git-commitlisted

# Git Commit Create commit messages that stay useful after the diff is closed. ## Purpose / Not For Use this skill when the task includes drafting or creating a git commit. In scope: - Turn staged or unstaged changes into an accurate Conventional Commit header. - Add a commit body that explains why the change was necessary and what was done. - Follow the repository's existing commit taxonomy when it already has a stable pattern. - Flag commits that should probably be split before creating misleading history. Out of scope: - Pull request writing, release notes, or changelog generation by themselves. - Rebases, history rewriting, or force-push workflows. - Generic git troubleshooting unrelated to the commit message itself. ## Archetype Recommend Lightweight with a small decision layer. Why: - The workflow is linear and repeatable. - Most quality checks are binary: correct type, correct scope, correct body structure, correct breaking-change signaling. - The only subjective part is choosing the most accurate framing, which is handled by the type and body references. ## Trigger Boundary Trigger this skill when the user asks for any of the following: - `commit this` - `make a commit` - `create a commit` - `write a commit message from this diff` - `draft a proper git commit` - any request whose next meaningful step is creating a real git commit Do not trigger when the user only wants: - a pull request - a changelog - release/version planning without a commit task - a gene