commit
Create micro-commits (minimal incision) with at least one validation signal per commit.
When & Why to Use This Skill
This Claude skill automates the creation of micro-commits, ensuring every code change is surgical, isolated, and verified. By enforcing a 'minimal incision' principle and requiring at least one validation signal per commit, it enhances repository health, simplifies code reviews, and prevents the accumulation of unrelated changes. It is an essential tool for maintaining a clean, professional Git history and improving overall software delivery quality.
Use Cases
- Refactoring Complex Codebases: Systematically breaking down large-scale refactors into small, atomic commits that are easier to test, understand, and revert if necessary.
- Streamlining Code Reviews: Providing reviewers with a clear, logical progression of changes, which significantly reduces the cognitive load required to approve Pull Requests.
- Maintaining CI/CD Stability: Ensuring that every single commit passes local validation signals before being recorded, preventing broken builds and reducing friction in continuous integration pipelines.
- Precision Debugging and Rollbacks: Creating a granular commit history that allows developers to use tools like 'git bisect' more effectively to pinpoint the exact origin of a regression.
| name | commit |
|---|---|
| description | Create micro-commits (minimal incision) with at least one validation signal per commit. |
Commit
Intent
Carve changes into surgical commits: one coherent change, minimal blast radius, and at least one feedback signal before committing.
When to use
- “Split this into micro commits.”
- “Stage only the minimal change and commit it.”
- “Keep the commits tiny, keep checks passing.”
Workflow (Surgeon’s principle)
1) Scope the incision
- Identify the smallest change that can stand alone.
- Isolate unrelated edits; avoid drive-by refactors/formatting unless required for correctness.
2) Stage surgically (non-interactive-first)
Inspect:
git status -sbgit diff
Stage what you intend (prefer file-level staging in non-interactive harnesses):
git add <paths...>git restore --staged <paths...>
Verify:
git diff --cachedmatches the intended incision.
If you truly need hunk-level staging but your environment can’t do interactive staging, ask the user to stage hunks locally or provide a patch you can apply.
3) Validate the micro scope
- Optional helper:
scripts/micro_scope.py(staged vs unstaged size). - If the staged diff is multi-concern, split it before running checks.
4) Close the loop (required)
- Select the tightest available signal and run it.
- If the repo’s test/check command is not discoverable, ask for the preferred command.
- Reference:
references/loop-detection.md.
5) Commit
- Use a terse message; optimize for clarity, not poetry.
- Commit only after at least one signal passes.
6) Repeat
Repeat until the working tree is clean or the remaining changes are intentionally deferred.
Guardrails
- Don’t widen scope without asking.
- Prefer the smallest check that meaningfully exercises the change.
- Don’t claim completion without a passing signal.
Resources
scripts/micro_scope.pyreferences/loop-detection.md