Menu
Use when making git commits. Conventional commit format and rules.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | commit-conventions |
| description | Use when making git commits. Conventional commit format and rules. |
∀ git commits.
<type>(<scope>): <summary>| Type | When |
|---|---|
feat | New feature ∨ capability |
fix | Bug fix |
refactor | Code restructuring without behavior change |
test | Adding ∨ updating tests |
docs | Documentation changes |
chore | Tooling, config, dependencies |
Scope: feature work → auth/login | module → api/users | general → omit scope
feat(auth/login): add user validation
fix(auth/login): handle null email in signup
test(auth/login): add failing spec for email validation
docs(api): update API documentation
revert(auth/login): undo broken migration
chore: update dependencies
PR titles become the squash-merge commit on main — same conventional-commit rules apply:
| Kind | Format | Example |
|---|---|---|
| Slice PR | <type>(S<NN>): <summary> | feat(S03): /pi-rules doctor diagnostic CLI |
| Milestone PR | <type>(M<NN>): <name> | feat(M01): rule discovery expansion |
Always squash-merge — never merge-commit. Merge-commit messages
(Merge pull request #N from …) are non-conventional and break release tooling.
git add . ¬git add -A)Enforced by lefthook commit-msg hook. ¬bypass with --¬-verify.
Use when running security review on a diff/PR/file. Research-vs-Reporting discipline, three-tier confidence gate, attacker-controllable taxonomy.
Use when invoking plannotator for approval review of generated .tff-cc milestone artifacts (plan, verification, spec).
Use when starting design or discovery work. MUST use before any creative work.
Use when the user wants to report a bug, file an issue, or send feedback about tff-cc. Triggers on phrases like 'report issue', 'file a bug', 'tff-cc broke', 'something is wrong with tff-cc', 'open an issue', '/report-issue'.
Use when creating, refining, or composing skills. Evidence-driven pattern analysis.
Use when verifying acceptance criteria. Binary verdict per criterion. Evidence-based.