hhk7734/commit

Commit

Create focused git commits from the current working tree.

Workflow

1. Inspect the repository state before staging anything:

   • git status --short
   • git diff --stat HEAD
   • git diff HEAD
   • git log --oneline -10

2. Verify changed code complies with applicable agent instruction files before staging:

   • List every changed path that will be included, including modified, staged, deleted, renamed, and untracked files.
   • For each changed path, check for AGENTS.md and CLAUDE.md at the repository root and in every ancestor directory from the path's top-level directory down to the changed file's parent directory.
   • Read every applicable instruction file found along that path and verify the changed code follows those instructions.
   • If an instruction conflict or compliance issue exists, fix it before continuing, or report the blocker instead of committing.

3. Decide whether the changes are one logical commit or multiple independent commits. Split unrelated features, fixes, refactors, docs, config, and generated artifacts when they can stand alone.

4. Do not commit files that likely contain secrets, credentials, private keys, tokens, or local-only environment values.

5. Stage files explicitly by path. Do not use git add . or git add -A.

6. Commit each logical group with a Conventional Commit message and a heredoc:

   git commit -F - <<'EOF'
   type(scope): concise imperative summary
   
   Optional body explaining why the change exists.
   EOF
   

7. After committing, report the commit hash and final git status --short.

Commit Message Rules

• Use Conventional Commits 1.0.0.
• Allowed types: feat, fix, docs, style, refactor, test, chore.
• Use a single optional scope, not comma-separated scopes.
• Keep the subject imperative, lowercase after the type prefix, and without a trailing period.
• For breaking changes, put ! after the type or scope, for example feat(api)!: remove deprecated endpoint.
• Prefer the subject to explain the user-facing or maintenance reason, not just the file operation.
• Add a body only when the reason, tradeoff, or migration detail is not obvious.
• Use footers for BREAKING CHANGE, Refs, or Closes when applicable.

Guardrails

• Never amend an existing commit unless the user explicitly asks.
• Never skip hooks with --no-verify unless the user explicitly asks.
• Never push or create a pull request; use commit-push to push or commit-push-pr to publish a PR.
• If there are no changes to commit, say so and do not create an empty commit.