claude/skills/commit/SKILL.md
Stage and commit changes to git following conventional commits format. Use when asked to commit, create a commit, or save changes. Drafts meaningful commit messages by understanding the why, not just the what. Never amends published commits, never skips hooks, never uses git add -A. Stages specific files by name. Does not push — that is the gh skill's job.
npx skillsauth add paulnsorensen/dotfiles commitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Stage and commit. Conventional commits. No push.
Run in parallel first:
git status
git diff HEAD
git log --oneline -5
Then sequentially:
git add -A or git add .git statustype(scope): short description (≤72 chars)
Optional body if nuance is lost without it.
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Types: feat, fix, refactor, chore, docs, test, style
Focus on the why, not the what. The diff already shows what changed.
Use a heredoc to preserve formatting:
git commit -m "$(cat <<'EOF'
type(scope): short description
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
EOF
)"
.env, credentials, or large binaries — warn the user$ need single-quoted delimiter (<<'EOF' not <<EOF)git diff HEAD after staging means nothing new was added — check git diff --cached insteadtools
Reconstruct what a past coding-agent session was doing so you can resume it — goal, files touched, last verified state, and the next step — by querying the session logs. Use when the user says "what was I working on", "recover that session", "reconstruct where I left off", "resume my last session", "what did that session change", "rebuild context from logs", or invokes /work-recovery. Report-only — it never scores or judges. Do NOT use for usage scoring (that is /skill-improver, /tool-efficiency, /prompt-analytics) or one-off interactive log queries (that is /session-analytics).
development
Curate this repo's hallouminate wiki (.hallouminate/wiki/, the repo:dotfiles:wiki corpus) — add or update architecture pages, per-harness docs, and gotchas. Use when the user says "update the wiki", "document this in the wiki", "refresh the harness docs", "add a wiki page", "curate the wiki", "the wiki is stale", or invokes /wiki-curator. Also use at session end to write back a non-obvious decision or gotcha worth preserving. Grounds the existing wiki first, follows one-topic-per-file conventions, verifies every external doc URL before writing, and reindexes. Do NOT use for general code search (that is cheez-search) or for editing AGENTS.md command reference.
tools
Audit how a tool, command, or MCP server is actually used across coding-agent sessions and produce calibrated recommendations — tool-vs-task fit, error forensics, fix recommendations, permission friction, MCP health, and token economics. Use when the user says "tool efficiency", "am I using X efficiently", "audit tool usage", "why does X keep failing", "how do I fix this error", "what should I change", "permission friction", "is this MCP worth it", "tool error rate", "fix recommendations", or invokes /tool-efficiency. Do NOT use for auditing a skill or agent definition (that is /skill-improver) or for one-off interactive log queries (that is /session-analytics).
tools
Analyze how prompts and skill routing behave across coding-agent sessions and produce calibrated recommendations — prompt-pattern analysis, routing accuracy, and knowledge gaps. Use when the user says "analyze my prompts", "prompt patterns", "is routing working", "which skill should have fired", "knowledge gaps", "what do I keep asking", or invokes /prompt-analytics. Do NOT use for auditing a single skill/agent definition (that is /skill-improver), tool/MCP efficiency (that is /tool-efficiency), or one-off interactive log queries (that is /session-analytics).