commit-helper

Conventional Commit Helper

Create a well-formatted commit following conventional commit conventions.

Parse the user's request for commit scope and message. A request to create a commit authorizes that scoped local commit; a request only to draft a message does not. Read applicable AGENTS.md instructions, discover available command tools, and honor required project checks. This workflow does not authorize pushing, amending, bypassing hooks or changing Git configuration.

Steps

1. Analyze Changes

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

2. Stage Files (if needed)

Inspect the actual staged and unstaged diffs, not only their statistics. Identify the selected files/hunks and any pre-existing staged changes. Stage only authorized scope with explicit paths/hunks; never use git add . or git add -A by default. If unrelated changes are already staged, preserve the index and resolve commit scope before committing; do not silently include or unstage someone else's work. Re-read the final staged diff before commit. 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/

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

Format: type(scope): description

Examples:

• feat(auth): add JWT refresh token rotation
• fix(feed): prevent duplicate swipes on same candidate
• refactor(api): extract validation into middleware
• docs(readme): update setup instructions for Docker
• test(users): add edge cases for concurrent access

If the user provides a specific commit message, use it instead of auto-generating.