Skip to content

BUZZARDGTA/Session-Sniffer / .agents/skills/commit

commit

Verified

Organize 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:

  1. Inspect the Git working tree and full diff.
  2. Identify the files and individual diff hunks belonging to the requested change.
  3. Do not stage unrelated files or hunks.
  4. If the requested change cannot be separated safely from unrelated changes, explain the overlap and ask how the user wants to proceed.
  5. Propose one commit message describing only that change.
  6. 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.

  1. Inspect the Git working tree and full diff.
  2. Group changes into logical, independently meaningful changes.
  3. Separate unrelated features, fixes, refactors, tests, documentation, configuration, and other changes into different commits where practical.
  4. Use file-level and hunk-level staging when necessary.
  5. Do not force a separation when changes are tightly coupled and belong in the same commit (for example, resources/translations/*.json catalog updates belong in the same commit as the user-facing code or settings changes they translate).
  6. Propose one commit message for each logical change.
  7. Show the proposed groups, affected files, and commit messages.
  8. Create the proposed commits in logical order.

Commit Messages

Use concise Conventional Commit-style messages when appropriate:

  • feat: for new functionality
  • fix: for bug fixes
  • refactor: for code restructuring without behavior change
  • perf: for performance improvements
  • test: for test-only changes
  • docs: for documentation
  • build: for build/dependency/package changes
  • chore: 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:

  1. Review the staged diff.
  2. Verify that any commit adding, modifying, renaming, or removing user-facing strings (tr(), tr_plural(), SettingMeta, ThemeColorTokenMeta, or get_web_panel_i18n()) also includes the corresponding updates across all 32 resources/translations/*.json catalogs (see .agents/rules/i18n.md). If translations are missing from the working tree, stop and report or complete them before committing.
  3. Follow the validation workflow in .agents/rules/testing.md for the staged changes (running targeted checks, the full quality script when appropriate, or release-specific validation for version-only bumps).
  4. 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.

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 implementationStars: 318kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 318kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 318kUpdated Claude CodeCodexVerifiedInstall