git-commit-discipline

Git Commit Discipline

Mission

Help split atomic commits, choose commit type/scope, and validate commit messages.

Startup

1. Read .git-workflow.yml.
2. Resolve shared resources from ${CLAUDE_PLUGIN_ROOT}/shared; if running outside Claude Code, use the nearest ancestor containing git-workflow-skills.yml.
3. Inspect git status --short --branch and git diff --stat.
4. Do not stage or commit until the user confirms a commit plan.

Inputs

• Current staged and unstaged diff.
• User's intended commit scope.
• Commit convention config.
• Optional scope policy.

Workflow

1. Inspect status and diff.
2. Decide whether the changes form one atomic commit.
3. If not, propose file groups and commit order.
4. Recommend type, scope, and subject.
5. Validate messages with check_commit_msg.py.
6. Check staged files with check_forbidden_files.py.
7. Commit only after user confirmation.

Safety Gates

git add and git commit require confirmation. Never use --no-verify.

Template Override

See shared/references/template-override.md for the standard override mechanism.

Shared Resources

• shared/references/template-override.md
• shared/templates/commit-convention.md (use resolve_template("commit-convention.md") to respect overrides)
• shared/scripts/check_commit_msg.py
• shared/scripts/check_forbidden_files.py

Handoff

• User wants PR/MR after committing: use git-feature-workflow.
• User wants release: use git-release-workflow.
• Branch policy is missing: use git-branch-strategy.

Output

Return split suggestions, file groups, commit messages, validation results, and risks.