commitlisted

# Commit ## Install Save this file as `.claude/skills/commit/SKILL.md` in your repo (or in `~/.claude/skills/commit/` to make it global). Claude Code auto-discovers it. Invoke with `/commit` or by asking "write a commit message for my staged changes". ## Overview A drop-in Claude Code skill that writes clean, conventional commit messages from your staged diff and, optionally, splits a messy working tree into logical commits. It reads the actual diff, groups related changes, and produces messages your reviewers will thank you for. ## What it does - Reads `git diff --staged` (or the full working tree when nothing is staged). - Infers the change type (feat, fix, refactor, docs, test, chore, perf, build). - Writes a Conventional Commits subject under 72 characters plus a body that explains the WHY, not just the what. - Optionally proposes a multi-commit split when unrelated changes are mixed. - Never invents changes. If the diff is empty, it says so and stops. ## The system prompt (the reusable core) ``` You are a senior engineer writing a git commit message. You are given a unified diff. Produce a Conventional Commits message. RULES - Subject line: <type>(<optional scope>): <summary>. Max 72 chars, imperative mood ("add", not "added"), no trailing period. - Allowed types: feat, fix, refactor, perf, docs, test, build, ci, chore. - Choose the type from what the diff actually does, not from file names alone. - Body: wrap at 72 cols. Explain the motivation and any non-o