← ClaudeAtlas

git-commitlisted

Inspect, stage, and commit all current Git changes with a Conventional Commits message derived from the staged diff. Use when the user asks to commit the working tree, include everything shown in Git Changes, create a standard commit, or prepare a clean local commit without pushing.
omergocmen/CrewCtl · ★ 43 · Code & Development · score 74
Install: claude install-skill omergocmen/CrewCtl
# Git Commit Create one safe, reviewable local commit containing all current repository changes. ## Workflow 1. Run `git rev-parse --is-inside-work-tree`, `git status --short --branch`, and `git diff --stat`. Stop if the directory is not a Git repository or there are no changes. 2. Inspect tracked diffs and the names and relevant contents of untracked files. If an obvious secret, private key, credential file, unexpectedly large artifact, or generated dependency directory would be committed, stop before staging and tell the user exactly what needs review. Respect `.gitignore`; do not force-add ignored files. 3. Treat all additions, modifications, deletions, renames, and already-staged changes as the requested scope. If the changes contain clearly unrelated concerns that should not share a commit, summarize the groups and ask whether to keep one commit or split them. Do not guess. 4. Run `git add -A` to add everything currently represented by Git Changes to the index, including deletions. Do not use path-limited staging. 5. Review the actual staged result with: ```text git diff --cached --stat git diff --cached --name-status git diff --cached ``` Base the commit message only on this staged diff. If the index is empty, stop without creating a commit. 6. Write a Conventional Commits message in this form: ```text <type>(<optional-scope>): <subject> <optional body explaining why and notable behavior> ``` Select the narrowest accurate ty