commit
Commit
Create one clear Conventional Commit for the intended current changes.
Workflow
- Inspect
git status,git diff, andgit diff --cached. - Read recent commit messages for useful scopes and local phrasing.
- If there is nothing worth committing, stop.
- Stage only intended files. Never stage secrets.
- Use the user's message if provided. Otherwise write a Conventional Commit message:
type(scope): subject. - Create the commit and report the hash and message.
Rules
More from owainlewis/blueprint
tdd
Test-first variant of implement: understand the desired behavior, write a failing test, make it pass, then simplify.
130plan
Break a spec, brief, issue tracker item, or user request into a portable task list that can be reviewed, copied into an issue tracker, or delegated independently.
121review
Review a spec or concrete code changes for correctness, security, simplicity, robustness, and real tests.
120spec
Write an implementation spec to docs/<feature-slug>/spec.md and pause for human review. Use when the user says \"write a spec\", \"spec this out\", \"technical design\", \"design doc\", or when a task has decisions, invariants, or contracts that should be reviewed before code is written.
117refactor
Improve the shape of existing code without changing behavior.
104debug
Debug systematically: observe, hypothesize, test, fix, verify.
96