| name | commit-discipline |
| description | Use when preparing commits, splitting work into commit boundaries, writing commit messages, or reviewing whether a branch is ready for GitHub PRs in this repository. |
Commit Discipline
Use this skill when the task involves commit planning, commit message writing, or GitHub readiness.
Read first
docs/engineering/commit-and-github-workflow.md
docs/memory/active-context.md
AGENTS.md
Workflow
- Identify the current change set.
- Decide whether it is one atomic concern or several.
- Split by concern if schema, auth, tenancy, frontend, docs, or tooling are mixed without a single delivery reason.
- Draft the commit message using
type(scope): summary.
- Add body sections only when they increase review clarity:
- Confirm the validation that was run and what remains unverified.
- If the branch is PR-ready, suggest the PR title and note migration, tenancy, auth, or rollout risk.
Rules
- prefer atomic commits over timeline commits
- do not accept
wip, changes, or generic messages
- do not group unrelated refactors into feature commits
- keep schema and risky auth changes especially easy to review
- if a commit cannot be reverted cleanly, it is probably too broad