← ClaudeAtlas

commitlisted

Stage and commit changes with native git, after showing the user exactly what will be committed. Triggers on /commit.
dagonet/claude-code-toolkit · ★ 3 · Code & Development · score 72
Install: claude install-skill dagonet/claude-code-toolkit
# Commit Execute a proper commit workflow using native git (PR1 removed the MCP-git mandate — the guard hooks gate git rather than ban it). ## Workflow 1. **Check status** - `git status --short` - If there are no changes, tell the user and stop 2. **Review changes** - `git diff --stat` for unstaged changes - `git diff --cached --stat` for already-staged changes 3. **Check recent commit style** (optional) - `git log --oneline -5` - Match the existing commit message style 4. **Stage files** - `git add <path> [<path> ...]` with explicit paths — never `.` or `*` 5. **Summarize what will be committed** - `git diff --cached --stat` again, and list the files in a short bullet list - Explain the purpose of the changes 6. **Template drift check** (requires template-sync-tools MCP) - If `.claude/template-manifest.json` exists in the repo root: 1. Call `template_compute_status(project_path=".")` 2. If any files have status `PROJECT_CUSTOM` or `CONFLICT`, append after the commit: **"Template drift detected: X file(s) modified locally. Run `/contribute-upstream` to push generalizable changes back, or `/sync-template` to pull latest template updates."** 3. If any files have status `AUTO_UPDATE`, append after the commit: **"Template updates available for X file(s). Run `/sync-template` to apply."** - If no manifest exists or template-sync-tools MCP is unavailable: skip silently 7. **Commit** - `git commit -m "<message>"` — clear, c