// Create well-structured git commits with conventional commit messages. Use when asked to commit changes, prepare a commit, or stage and push code.
| name | git-commit |
| description | Create well-structured git commits with conventional commit messages. Use when asked to commit changes, prepare a commit, or stage and push code. |
| license | MIT |
| compatibility | Requires git |
| allowed-tools | Bash(git:*) |
git status to see all changed files. Read the output carefully.git diff --stat to understand the scope of the change.git add <specific-files>, never git add . unless every changed file belongs in the same logical commit.<type>(<scope>): <description>
<body — explain WHY, not WHAT>
<footer — references, breaking changes>
feat, fix, refactor, docs, test, chore, perf, cigit diff --cached to review exactly what will be committed. Read the staged diff.git commit -m "..." with the message.| Excuse | Rebuttal |
|---|---|
"I'll just use git add . to save time" | Staging everything blindly leads to committing debug files, env vars, and unrelated changes. Stage intentionally. |
| "The message 'fix stuff' is fine for now" | Every commit message is permanent history. Write it properly the first time. |
| "I'll squash these later" | You won't. Write clean commits now. |
git diff --cached output was reviewed before committing.env, __pycache__, or build artifacts were stagedDesign or review REST and GraphQL API interfaces. Use when asked to design an API, review endpoint structure, define request/response schemas, or improve API ergonomics.
Perform a structured security and quality audit on source code. Use when asked to review code, audit a pull request, check for vulnerabilities, or assess code quality.
Design, build, or debug data processing pipelines. Use when asked to process a dataset, transform data, build an ETL pipeline, schedule batch jobs, or fix data quality issues.
Safely run database schema migrations. Use when asked to update database schema, add columns, create tables, run alembic, or apply Django migrations.
Audit project dependencies for vulnerabilities, license issues, and bloat. Use when asked to check dependencies, audit packages, find vulnerable libraries, or reduce bundle size.
Execute a structured deployment to staging or production. Use when asked to deploy, ship, release, push to production, or promote to staging.
