Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From mindlas
Partitions a broad change set into smaller, coherent, reviewable bundles to reduce change blast radius. Writes bundle metadata to .mindlas/splits/ without modifying source files.
How this command is triggered — by the user, by Claude, or both
Slash command
/mindlas:mindlas-blast-splitThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
!`mindlas blast split --apply --session ${CLAUDE_SESSION_ID}`
The Patch Splitter planned a deterministic split of this session's diff and wrote a validated
split queue under `.mindlas/splits/` (see the manifest path above). The `before → planned` move
reflects the BLAST the split **would** achieve once the bundles are landed separately — it is a
*planned* reduction, never modeled and never evidence-based, so the gauge stays honest.
**No source files were touched.** The Splitter only reads the diff and writes bundle metadata —
it never modifies, stages, commits, or rewrites your code. Land...!mindlas blast split --apply --session ${CLAUDE_SESSION_ID}
The Patch Splitter planned a deterministic split of this session's diff and wrote a validated
split queue under .mindlas/splits/ (see the manifest path above). The before → planned move
reflects the BLAST the split would achieve once the bundles are landed separately — it is a
planned reduction, never modeled and never evidence-based, so the gauge stays honest.
No source files were touched. The Splitter only reads the diff and writes bundle metadata — it never modifies, stages, commits, or rewrites your code. Landing each bundle is a human step by design.
If it reported no split: the diff is already small and coherent (one bundle, or the dominant bundle already carries the whole BLAST), so no artifacts were written and no win was claimed — there is nothing to partition.
Next step: review the bundles in the manifest and land them one coherent group at a time.
After each bundle, run /mindlas-verify (mindlas verify gate --preview) so verification tracks
the narrower change set rather than the original broad patch.
npx claudepluginhub evolutionairy-ai/mindlas/semantic-commitAnalyzes staged changes and splits them into semantic commits grouped by functional boundary, with user approval per commit. Supports --dry-run, --lang, and --max-commits options.
/semantic-commitAnalyzes staged git changes and splits them into small, meaningful commits with semantic messages. Supports --dry-run, --lang, and --max-commits options.
/create-prCreates a new branch, formats modified files with Biome, splits changes into logical commits, and submits a pull request with a summary and test plan.
/tidy-commitsOrganizes uncommitted changes into logical, review-friendly commits to make code review easier.
/semantic-commitAnalyzes staged changes, splits them into logical semantic units, and commits each unit with a conventional commit message. Supports --dry-run, --lang, and --max-commits options.
/semantic-commitSplits large uncommitted changes into logical atomic commits with semantic messages. Analyzes file groupings and change types. Supports --dry-run, --lang, --max-commits.