91b9845c1b
comments-clean purges explanatory comments before every operator-requested stage or commit and penalizes own violations into persistent memory; commit-no-verify commits the exact staging index with hooks skipped, the invocation itself being the per-commit authorization; commit-next chains both and stages the next logical bundle with an explain and confidence briefing; explain walks code and its collaborators in execution order and offers a Mermaid schema in the affected README; help-skills lists every project, global and plugin skill with triggers and composition. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
988 B
988 B
name, description
| name | description |
|---|---|
| commit-next | Commit the staged bundle with --no-verify, then stage the next logical bundle and brief the operator on it. Trigger on /commit-next or when the operator asks to commit and stage the next bundle in one step. Portable across projects. |
- Run the commit-no-verify skill on the currently staged changes
(comments-clean audit first, then
git commit --no-verify, exact staging index only). - Group the remaining uncommitted changes into logical bundles (one concern per bundle: same failure class, same mechanism, or same role) and stage the next one; never mix concerns to save a commit.
- For the newly staged bundle run the explain skill (what the changes do and how the pieces interact, file:line-anchored) followed by the confidence skill (fix confidence, break risk, evidence, residuals).
- Close with what remains unstaged and wait for the operator's commit decision; never auto-commit the newly staged bundle.