From kernel
Performs code review on GitHub PRs or staged git changes, reports >80% confidence issues in logic/security/performance, outputs verdict: APPROVE, REQUEST CHANGES, or COMMENT.
How this command is triggered — by the user, by Claude, or both
Slash command
/kernel:reviewThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
<command id="review"> <purpose> Review code changes for quality, correctness, security. Only report issues with >80% confidence. Load: skills/testing/SKILL.md, skills/security/SKILL.md Reference: _meta/research/ai-code-anti-patterns.md </purpose> <context> ai_code_stats: buggier: 1.7x more issues than human code security: 40-62% contain vulnerabilities findings: 10.83 per AI PR vs 6.45 human priority: check Big 5 first (what AI actually breaks) </context> <on_start> <identify_scope> </identify_scope> </on_start> <confidence_threshold> | Confidence | Category | Report? | |----...
Load: skills/testing/SKILL.md, skills/security/SKILL.md Reference: _meta/research/ai-code-anti-patterns.md
ai_code_stats: buggier: 1.7x more issues than human code security: 40-62% contain vulnerabilities findings: 10.83 per AI PR vs 6.45 humanpriority: check Big 5 first (what AI actually breaks)
<on_start>
agentdb read-start
<identify_scope>
gh pr diff {number} # For PRs
git diff --staged # For staged
git diff HEAD~1 # For recent
</identify_scope> </on_start>
<confidence_threshold>
| Confidence | Category | Report? |
|---|---|---|
| 95%+ | Definite bug | YES |
| 85-95% | Likely issue | YES |
| 70-85% | Possible issue | MAYBE |
| <70% | Style preference | NO |
| </confidence_threshold> |
Files: X changed Findings: Y (Z critical)
[file:line] Issue (confidence: XX%) → Fix: suggestion
[file:line] Issue (confidence: XX%) → Fix: suggestion
Summary: APPROVE | REQUEST CHANGES | COMMENT </output_format>
<ask_user> Use AskUserQuestion when: a finding is between 70-85% confidence (ambiguous) Ask: "Found {issue} at {file:line} (confidence {X}%). Intentional, or should I flag it?" Options: intentional — skip, flag it, investigate deeper </ask_user>
<verdict_rules>
<on_complete>
agentdb write-end '{"command":"review","verdict":"X","critical":N,"high":N,"big5_violations":N}'
</on_complete>
npx claudepluginhub ariaxhan/kernel-claude --plugin kernel/code-reviewReviews local uncommitted changes or GitHub pull requests for security, code quality, and best practices. Also supports PR review mode with full file context.
/code-reviewReviews local uncommitted changes or GitHub PRs for security, code quality, and correctness issues, producing a severity-graded report.
/reviewPerforms structured code review on a file, recent unstaged changes, or changes since last commit. Categorizes issues by severity and outputs markdown table with verdict.
/reviewReviews staged changes or recent commits across five axes—correctness, readability, architecture, security, performance—producing categorized findings with file:line references and fixes.
/reviewRuns Codex code review on local git state (working tree or vs base branch). Supports --wait/--background, --base <ref>, --scope auto|working-tree|branch.
/reviewInvokes multiple external AI CLIs (Gemini, Claude, Codex, etc.) to independently review a phase plan and produces a structured REVIEWS.md with per-reviewer feedback.