← ClaudeAtlas

cmp-commitlisted

Use when the owner explicitly asks to commit work in this project — reading the diff, proposing atomic commits, running the finish gates, staging specific files and writing a Conventional Commits message. Commits only; never pushes unless separately asked.
whinstudio/skills · ★ 0 · Code & Development · score 69
Install: claude install-skill whinstudio/skills
# Commit The owner starts this skill with `/cmp-commit`, optionally with a scope or wording hint. When the owner asks for a commit in plain words, follow the same steps. ## 1. Trigger - Commit only when the owner asks for it in this conversation. A negation ("do not commit yet") wins over any earlier request. - A headless code step never commits: `git` is not an allowed command there. - Work on the branch that is checked out. If the owner uses branches, follow their naming. Never stash, reset or check out over the owner's uncommitted work to switch branches, and do not insist on a branch when the owner says none is needed. ## 2. Read the state ``` git status --short git diff --stat git diff git diff --staged ``` - Compass normally creates the repository and makes the first commits itself (template, design and assets, implementation; the owner can turn this off in Compass settings). Build outputs, `release/` and the run report are kept out through `.git/info/exclude` — leave them unstaged. - Not a git repository yet (Compass's git setting was off or git was missing): ask the owner before running `git init -b develop`. The first commit then holds the project as it stands: stage its folders and root files by name, as in step 5. - Files that are already staged but do not belong to this change: stop and ask the owner before going on. - Understand every change you are about to commit. A file you did not touch and cannot explain is asked about, not swept in.