Clean Commit
Run the quality-reviewer skill on the current diff, then commit with a message that explains business impact.
Workflow
- Inspect changes —
git status, git diff, git log --oneline -10
- Run quality gates — load
quality-reviewer and follow its full procedure (one independent reviewer, integrated checks, diff hygiene, lint, tests, caller check). Its Verdict line tells you whether you may proceed.
- Fix anything that fails. Do NOT commit on failed gates unless the user explicitly says "skip " or "just commit".
- Stage only intended files — never
git add . blindly. Inspect each path.
- Compose the commit message (see rules below).
- Commit —
git commit -m "<message>".
- Show the result —
git log -1 --stat.
Commit Message Rules
| Rule |
Detail |
| Scope prefix |
<scope>: <subject> (e.g., api:, docs:, ci:, fix:, test:) |
| Subject mood |
Imperative, lowercase after colon |
| Subject length |
≤ 72 characters |
| Body (optional) |
Wrap at 72 cols, explain WHY, not WHAT |
| Reference issues |
Refs #123 or Closes #123 in the body |
Good:
api: reduce listing endpoint p99 from 3s to 400msdocs: split AGENTS.md into per-component codemaps
Bad:
Update files (vague)fixed bug (no scope, no impact)refactor: improved code quality (says nothing)- A 200-char subject line
Skip Flags
User can skip gates explicitly. These map to the quality-reviewer gate names:
skip review → skip code-review analysis, including the independent reviewerskip lint → skip the linterskip tests → skip the test gatejust commit → stage + commit, no gates
If the user says "just commit", still inspect the diff for secrets / debug prints before committing.
Hard Rules
- Never commit secrets, API keys,
.env files, or generated debug logs
- Never use
git commit --amend or git push --force unless the user asks
- Never bypass hooks (
--no-verify) without explicit permission
- If a commit hook rejects: fix the issue and make a new commit, don't amend
1---2name: clean-commit3description: Review, stage, and commit local changes. Use only when the user explicitly asks to create a commit.4---56# Clean Commit78Run the `quality-reviewer` skill on the current diff, then commit with a message that explains business impact.910## Workflow11121. **Inspect changes** — `git status`, `git diff`, `git log --oneline -10`132. **Run quality gates** — load `quality-reviewer` and follow its full procedure (one independent reviewer, integrated checks, diff hygiene, lint, tests, caller check). Its `Verdict` line tells you whether you may proceed.143. **Fix anything that fails.** Do NOT commit on failed gates unless the user explicitly says "skip <gate>" or "just commit".154. **Stage only intended files** — never `git add .` blindly. Inspect each path.165. **Compose the commit message** (see rules below).176. **Commit** — `git commit -m "<message>"`.187. **Show the result** — `git log -1 --stat`.1920## Commit Message Rules2122| Rule | Detail |23|------|--------|24| Scope prefix | `<scope>: <subject>` (e.g., `api:`, `docs:`, `ci:`, `fix:`, `test:`) |25| Subject mood | Imperative, lowercase after colon |26| Subject length | ≤ 72 characters |27| Body (optional) | Wrap at 72 cols, explain WHY, not WHAT |28| Reference issues | `Refs #123` or `Closes #123` in the body |2930**Good:**31- `api: reduce listing endpoint p99 from 3s to 400ms`32- `docs: split AGENTS.md into per-component codemaps`3334**Bad:**35- `Update files` (vague)36- `fixed bug` (no scope, no impact)37- `refactor: improved code quality` (says nothing)38- A 200-char subject line3940## Skip Flags4142User can skip gates explicitly. These map to the `quality-reviewer` gate names:43- `skip review` → skip code-review analysis, including the independent reviewer44- `skip lint` → skip the linter45- `skip tests` → skip the test gate46- `just commit` → stage + commit, no gates4748If the user says "just commit", still inspect the diff for secrets / debug prints before committing.4950## Hard Rules5152- Never commit secrets, API keys, `.env` files, or generated debug logs53- Never use `git commit --amend` or `git push --force` unless the user asks54- Never bypass hooks (`--no-verify`) without explicit permission55- If a commit hook rejects: fix the issue and make a new commit, don't amend
gzb1128