Splits all git changes into atomic commits of related changes. Use when you have uncommitted work ready to commit.
npx claudepluginhub pipemind-com/pipemind-marketplace --plugin spec-driven-developmentThis skill is limited to using the following tools:
Split all uncommitted git changes into atomic, well-described commits grouped by logical relationship.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Split all uncommitted git changes into atomic, well-described commits grouped by logical relationship.
Co-Authored-By lines in commit messages — specifically, never write Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> or any variant1. Survey all changes
Run in parallel:
git status (staged, unstaged, untracked)git diff (unstaged changes)git diff --cached (staged changes)If the working tree is clean, say so and stop.
2. Understand the changes
Read changed files as needed. Group changes into atomic units by asking: "If I had to revert one thing without affecting anything else, what's the smallest coherent set?"
Grouping heuristics (in priority order):
3. Plan the commit sequence
Print a numbered plan before committing:
Plan:
1. [type] Short description — file1, file2
2. [type] Short description — file3
...
Present the plan above and wait up to 30 seconds for operator response. If the operator approves or does not respond within 30 seconds, proceed with the plan as shown.
4. Execute commits
For each planned commit:
git add <specific files> (use -p via Bash only if a file contains changes for multiple commits)git commit -m "<type>: <concise description>" using conventional commit types (feat, fix, refactor, chore, docs, test, style)5. Verify
Run git log --oneline -n <count> to show the new commits.