From git-discipline
Use when the user wants to commit ALL uncommitted changes in the working tree, grouped into logical commits. Triggers on /git-discipline:commit-all-the-things, "commit everything", "clean up the working tree", and "commit what's left".
How this skill is triggered — by the user, by Claude, or both
Slash command
/git-discipline:commit-all-the-thingsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<post-update-broadcast>
if [ -n "${CLAUDE_PLUGIN_ROOT:-}" ]; then
node "${CLAUDE_PLUGIN_ROOT}/bin/check-broadcast"
fi
If the command produces output, the git-discipline plugin was updated since the last time you saw the broadcast on this machine. Show the output verbatim in a markdown block, prefixed with one short sentence ("git-discipline was updated; here is what changed."). Then continue with the rest of this skill.
If the command produces no output, say nothing about updates and proceed.
The helper writes the sentinel only when stdout was non-empty, so a silent run does not mark the version as seen.
Commit all uncommitted changes in the working tree, grouped into logical commits with descriptive messages.
commit-snipe (which only commits the current session)/git-discipline:commit-all-the-things IS the instruction. Do not present a plan, do not confirm per commit, do not ask intermediate questions. Keep working until the working tree is clean.
digraph commit_all {
"git status" [shape=box];
"Working tree clean?" [shape=diamond];
"Identify coherent story\nfrom remaining changes" [shape=box];
"Stage files for this story" [shape=box];
"Commit" [shape=box];
"Report" [shape=doublecircle];
"git status" -> "Working tree clean?";
"Working tree clean?" -> "Report" [label="yes"];
"Working tree clean?" -> "Identify coherent story\nfrom remaining changes" [label="no"];
"Identify coherent story\nfrom remaining changes" -> "Stage files for this story";
"Stage files for this story" -> "Commit";
"Commit" -> "git status";
}
Read the diffs, not just file names. Signals that changes belong to the same story:
Infra and cleanup first, features after:
Files are an implementation detail. The unit is the logical change, not the file. Use git add -p to stage only the hunks that belong to the current story. A file with changes for two stories is split across two commits.
# Example: two hunks in settings.json, stage only the second
printf 'n\ny\n' | git add -p settings.json
Verify every staging with git diff --cached --stat before you commit.
Follow the commit message conventions in project- and user-CLAUDE.md. This skill determines only WHAT is grouped per commit, not HOW the commit is made.
git add . or git add -A. Always explicit paths or hunks.When done: short table with each commit (hash plus message). No explanation per commit, the messages speak for themselves.
npx claudepluginhub epologee/laicluse-agent-fieldkit --plugin git-disciplineGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.