aboutsummaryrefslogtreecommitdiff
path: root/.claude/commands/review-code.md
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-06 06:38:24 -0500
committerCraig Jennings <c@cjennings.net>2026-05-06 06:38:24 -0500
commitd4ff742e42832e889a4a3b10f6e8820f0a738010 (patch)
tree42b4be08aaf479df7a29cf7e94db374356af56c3 /.claude/commands/review-code.md
parentaa6924591127970d3241ab6b1a50f4bab457da27 (diff)
downloadrulesets-d4ff742e42832e889a4a3b10f6e8820f0a738010.tar.gz
rulesets-d4ff742e42832e889a4a3b10f6e8820f0a738010.zip
fix(commands): drop leftover name: frontmatter from converted commands
The conversion commit ran sed -i to strip the name: line, but the staged version from git mv was captured before the sed ran. Result: the commit shipped the original frontmatter, and the sed cleanup was sitting in the working tree. This commit lands the cleanup that should have been in aa69245.
Diffstat (limited to '.claude/commands/review-code.md')
-rw-r--r--.claude/commands/review-code.md1
1 files changed, 0 insertions, 1 deletions
diff --git a/.claude/commands/review-code.md b/.claude/commands/review-code.md
index 1bb2bde..e7f4e18 100644
--- a/.claude/commands/review-code.md
+++ b/.claude/commands/review-code.md
@@ -1,5 +1,4 @@
---
-name: review-code
description: Review code changes against engineering standards. Accepts a PR number, a SHA range (BASE..HEAD), the current branch's diff against main, staged changes, or a described scope ("the last 3 commits"). Audits CLAUDE.md adherence (reads root + per-directory CLAUDE.md), intent-vs-delivery (when given a plan/ADR/ticket), security, testing (TDD evidence + three-category coverage), conventions (conventional commits + no AI attribution), root-cause discipline, architecture (layering + scope), API contracts. Produces a structured report — Strengths, per-criterion PASS/WARN/FAIL, per-issue Critical/Important/Minor severity — ending with an explicit verdict (Approve / Request Changes / Needs Discussion) plus 1-2 sentence reasoning. Self-filters low-confidence findings; never flags pre-existing issues, lint/typecheck issues (CI handles those), or changes on unmodified lines. Use before merging a PR, before pushing a branch, or when reviewing a teammate's work. Do NOT use for proposing features (use brainstorm or arch-design), drafting implementation (use start-work or add-tests), standalone security audits (use security-check), or narrow style-only checks (a linter handles those).
---