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>
702 B
702 B
name, description
| name | description |
|---|---|
| commit-no-verify | Commit the currently staged changes with --no-verify (skip the pre-commit hooks). Trigger on /commit-no-verify or when the operator asks for a no-verify commit in any wording. Invoking this skill IS the explicit per-commit authorization that --no-verify requires; it never carries over to later commits. Portable across projects. |
- Run the comments-clean audit over the staged and unstaged changes first.
- Commit exactly the staging index with
git commit --no-verifyand a Conventional-Commits message derived from the staged diff; never add unstaged files, never push. - Report the created commit hash and what remains uncommitted.