BUZZARDGTA/Session-Sniffer / .agents/skills/commit
commit
VerifiedOrganize and commit current Git changes by committing a requested feature alone or splitting all unrelated changes into separate logical commits.
Session Sniffer Commit
Use this skill when the user wants to commit current Git changes.
Commit Modes
Determine the user's intent from the request.
Specific Change
If the user identifies a feature, fix, refactor, documentation change, or other specific change:
- Inspect the Git working tree and full diff.
- Identify the files and individual diff hunks belonging to the requested change.
- Do not stage unrelated files or hunks.
- If the requested change cannot be separated safely from unrelated changes, explain the overlap and ask how the user wants to proceed.
- Propose one commit message describing only that change.
- Stage only the intended changes and create exactly one commit.
All Changes
If the user asks to commit everything, do not automatically create one large commit.
- Inspect the Git working tree and full diff.
- Group changes into logical, independently meaningful changes.
- Separate unrelated features, fixes, refactors, tests, documentation, configuration, and other changes into different commits where practical.
- Use file-level and hunk-level staging when necessary.
- Do not force a separation when changes are tightly coupled and belong in the same commit (for example,
resources/translations/*.jsoncatalog updates belong in the same commit as the user-facing code or settings changes they translate). - Propose one commit message for each logical change.
- Show the proposed groups, affected files, and commit messages.
- Create the proposed commits in logical order.
Commit Messages
Use concise Conventional Commit-style messages when appropriate:
feat:for new functionalityfix:for bug fixesrefactor:for code restructuring without behavior changeperf:for performance improvementstest:for test-only changesdocs:for documentationbuild:for build/dependency/package changeschore:for maintenance
Write the message from the actual diff. Do not invent functionality or motivation that is not supported by the changes.
Safety
Follow the Git and Change Discipline rules in .agents/rules/core.md.
- Never modify files merely to make commits possible.
- Preserve unstaged and uncommitted changes that are outside the selected commit.
- Use partial/hunk staging when files contain changes belonging to multiple commits.
- Inspect the staged diff before every commit.
- Do not use
git add .or equivalent blanket staging when only part of the working tree belongs in a commit. - Do not push commits unless the user explicitly asks for a push as a separate action.
Validation
Before committing:
- Review the staged diff.
- Verify that any commit adding, modifying, renaming, or removing user-facing strings (
tr(),tr_plural(),SettingMeta,ThemeColorTokenMeta, orget_web_panel_i18n()) also includes the corresponding updates across all 32resources/translations/*.jsoncatalogs (see.agents/rules/i18n.md). If translations are missing from the working tree, stop and report or complete them before committing. - Follow the validation workflow in
.agents/rules/testing.mdfor the staged changes (running targeted checks, the full quality script when appropriate, or release-specific validation for version-only bumps). - If validation fails, stop before committing and report the failure.
For multiple commits, validate each staged change as appropriate before creating its commit.
Final Report
After committing, report:
- commit hash
- commit message
- files included
- validation performed
- any remaining unstaged or uncommitted changes
The goal is to produce clean, focused commits while leaving unrelated work untouched.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |