commit-discipline

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

1. docs/engineering/commit-and-github-workflow.md
2. docs/memory/active-context.md
3. AGENTS.md

Workflow

1. Identify the current change set.
2. Decide whether it is one atomic concern or several.
3. Split by concern if schema, auth, tenancy, frontend, docs, or tooling are mixed without a single delivery reason.
4. Draft the commit message using type(scope): summary.
5. Add body sections only when they increase review clarity:
   • Why
   • What
   • Validation
   • Refs
6. Confirm the validation that was run and what remains unverified.
7. 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

Output format

When asked to help with a commit, respond with:

1. proposed commit boundary
2. proposed commit message
3. validation status
4. risks or follow-up notes