commit

Commit the current repository changes.

Follow this exact workflow:

1. Inspect the repository state:
   • Run git status --short.
   • Run git diff and git diff --staged.
   • Run git log --oneline -5 to match the repository's commit style.
2. Decide what belongs in this commit:
   • Stage only relevant files by explicit path.
   • Do not use git add -A or git add . unless the user explicitly asked for an all-files commit.
   • Do not stage secrets, credentials, .env*, private keys, or unrelated local files.
3. Verify before committing:
   • Run the relevant available checks for this repository, such as tests, lint, typecheck, or build.
   • If no check command exists, say that explicitly.
4. Create one atomic commit:

   • Use the repository's existing commit message style when clear.

   • Prefer <type>: <short description> when no local convention exists.

   • Explain why in the body when useful.

   • Do not amend unless the user explicitly asked for amend.

   • Do not bypass hooks with --no-verify.

   • Include this trailer:

     Co-Authored-By: Claude Opus 4.7 <[email protected]>

5. If a hook or verification fails:
   • Fix the root cause if it is in scope.
   • Re-stage the relevant files.
   • Create a new commit after the fix.
   • Do not bypass the failing hook.
6. Finish by reporting:
   • Commit hash and message.
   • Verification commands run.
   • Any files intentionally left uncommitted.

Arguments from the user, if any, are additional guidance for what to include or how to phrase the commit:

$ARGUMENTS