| name | phase-commit-workflow |
| description | Create high-quality phase commits for this repository. Use when work is executed in multiple phases or when preparing any git commit, so each commit is atomic, validated, clearly messaged, and easy to review or rollback. |
Phase Commit Workflow
Apply this workflow whenever a phase is complete and a commit is needed.
Workflow
- Define commit scope for the completed phase.
- Inspect working tree and exclude unrelated changes.
- Validate the phase (run relevant checks or report what cannot run).
- Craft a commit message with explicit intent and evidence.
- Commit only phase files.
- Verify commit content and leave a short handoff summary.
Commit Scope Rules
- One commit per completed phase.
- Keep commit atomic and reviewable.
- Do not bundle unrelated refactors.
- Do not stage generated noise unless required by the phase.
- Never include secrets, credentials, or local environment artifacts.
Message Standard
Use this subject format:
type(scope): short outcome [phase X/N]
Recommended type values:
feat for new behaviorfix for bug fixesrefactor for structural cleanup without behavior changedocs for documentation-only updatestest for test additions/updateschore for maintenance tasks
Body template:
Why:
- reason for this phase
What:
- key files/changes
Validation:
- commands run and outcomes
Staging Checklist
Before commit:
git status --shortgit diff --statgit add <phase-files-only>git diff --cached
If unrelated files are staged, unstage them before committing.
Phase Handoff Note
After commit, report:
- commit hash
- phase objective completed
- validations executed
- next phase to run
