Git commit message format and guidelines. Use when making commits or creating agents that make commits.
Git commit message format and guidelines. Use when making commits or creating agents that make commits.
npx skills add https://github.com/dzackgarza/lattice_interface --skill git-commit-guidelinesこのコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール
Agent behavior auditing and structural debugging. Use when diagnosing why agents fail, produce trivial work, or don't complete assigned tasks.
Documentation coverage work for lattice theory methods. Use when doing documentation-only assignments - adding/updating method documentation, checklists, or reference docs.
Interface and type-surface design work. Use when assignments define or change API contracts, type signatures, or behavioral guarantees.
Test coverage work for lattice methods. Use when assignments involve code, tests, or runtime behavior - writing or updating tests.
Debug autonomous agent workers, cron jobs, timeouts, and connectivity issues. Use when agent runs are failing, not running, or producing unexpected behavior.
| name | git-commit-guidelines |
| description | Git commit message format and guidelines. Use when making commits or creating agents that make commits. |
All commits must follow this format:
<area>: <what>
Root cause: <why this was needed>
Behavior enabled: <what agents can now do correctly>
Guidelines:
Never claim completion: Tasks have no terminal state. Don't write "all N methods now documented" or similar. This poisons future runs by signaling no work remains.
Never use provenance files: Files like *_provenance_*.md are closure mechanisms. Git history is the authoritative record.
Example:
doc_coverage: Documented 47 Oscar methods across genus, lattice, quadratic_form
Root cause: Oscar package bilinear-form lattice APIs undocumented
Behavior enabled: Users can now discover these methods with source citations to local upstream docs
Always use explicit file list: git commit file1 file2 -m "message"
git add ., git add -A, or bare git commit