diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-20 09:47:13 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-20 09:47:13 -0500 |
| commit | b9da9b5142f1d343378e8d4f5aa6780ee8728cd4 (patch) | |
| tree | 84d9674cb3974b9d74f980742a52139fb76e395b /claude-rules | |
| parent | 5737cc0ca1725c1ea08f28cf60048ab3a3adec7c (diff) | |
| download | rulesets-b9da9b5142f1d343378e8d4f5aa6780ee8728cd4.tar.gz rulesets-b9da9b5142f1d343378e8d4f5aa6780ee8728cd4.zip | |
refactor(skills): convert review-code from command to skill
review-code was a command with disable-model-invocation set, so the model could never reach for it on its own. Every time a review fit the moment, the agent had to hand back to me to type the slash command. Moving it to a skill makes it model-invocable while it stays slash-invocable as /review-code.
git mv keeps the file history (99% rename). The frontmatter drops disable-model-invocation and gains name: review-code; the body is unchanged. It also drops the discovery-check paragraph in commits.md, which only existed to find the command on disk when it was missing from the skills list, moot now that the skill shows up there.
Diffstat (limited to 'claude-rules')
| -rw-r--r-- | claude-rules/commits.md | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/claude-rules/commits.md b/claude-rules/commits.md index 41d17e7..9e1a8e0 100644 --- a/claude-rules/commits.md +++ b/claude-rules/commits.md @@ -272,8 +272,6 @@ Run the `review-code` skill against the change: - Before a PR: `/review-code` (branch diff against `main` merge-base) - Before commenting on someone else's PR: `/review-code <PR#>` -**Discovery check.** If `/review-code` doesn't appear in the session's available-skills list, check `~/.claude/commands/review-code.md` and `./.claude/commands/review-code.md` on disk before declaring it unavailable. The available-skills enumeration covers plugin-installed skills but can miss user commands under `~/.claude/commands/`, which are still routable as slash-commands. If either file exists, surface the discrepancy to the user before falling through to the trivial-one-liner exception in Step 2 — don't auto-skip. - Surface **all** findings to the user: Critical, Important, and Minor. **Default block:** any Critical or Important finding stops the flow. Fix the |