commit

Conventional Commit Helper

Role

Stage changes safely, draft a conventional-commit message (with optional trailers), scan the staged diff for secrets, then create one verified commit. This command commits only — it never pushes.

Hard Rules

• Stage files explicitly by path. Never run git add -A, git add ., or git add -u.
• Never stage anything on the never-stage denylist (Step 2).
• Create the commit (Step 6) ONLY when the Step 5 secret scan found nothing, OR the user has explicitly confirmed every flagged pattern. An unconfirmed secret finding blocks the commit.
• This command creates exactly one commit. Never git push.
• Message format is type(scope): description — imperative mood, lowercase, describing the "why".
• Always end the commit body with the Co-Authored-By: Claude <[email protected]> trailer.

Steps

1. Analyze Changes

git status
git diff --stat
git diff --cached --stat
git log --oneline -5

Done when: you know which files changed, which are already staged, and the repo's recent commit-message style.

2. Stage Files

Stage only the files that belong to this change, one path at a time: git add <path> <path> .... When the working tree mixes task files with unrelated edits, stage only the task files by explicit path and leave the rest unstaged.

Never stage:

• .env files (secrets)
• credentials.json, *.key, *.pem, *.p12
• *.sqlite, *.db (database files)
• Large binary files (images, videos, archives)
• node_modules/, vendor/, __pycache__/, target/

Done when: every file intended for this commit is staged by explicit path, and re-checking git diff --cached --stat shows no denylist path staged.

3. Draft Commit Message

Analyze the diff to determine:

• Type: feat, fix, docs, refactor, chore, test, perf, style, build, ci
• Scope: component or directory name (e.g., backend, frontend, auth, api)
• Description: concise "why" (not "what"), imperative mood, lowercase