Commit guidelines

Apply these rules before creating, amending, squashing, or proposing a Git commit. Loading this skill does not itself grant permission to commit, amend, rewrite history, or push.

Read the repository first

1. Read the applicable AGENTS.md, CLAUDE.md, CONTRIBUTING.md, and commit or release documentation.
2. Inspect git status --short, the unstaged diff, the staged diff, and relevant untracked files.
3. Inspect recent commit subjects with git log -5 --format=%s to learn local scope and wording conventions.
4. Identify which changes belong to the current task. If ownership is ambiguous or the worktree contains overlapping user changes, ask before staging or committing.

Repository rules may narrow the allowed types, scopes, validation, or commit boundaries. Keep the Conventional Commit format unless a higher-priority instruction explicitly requires another format. The ban on AI authorship and co-authorship always applies.

Keep the commit focused