Review code changes for security, performance, correctness, and maintainability. Use when: 'review code', 'PR review', 'check changes', 'review my diff', 'is this…
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add KevinZai/commander --skill ccc-code-review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ccc Code Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/kevinzai-ccc-code-review-commander)More formats (shields.io, HTML) on the badges page.
---
name: ccc-code-review
description: "Review code changes for security, performance, correctness, and maintainability. Use when: 'review code', 'PR review', 'check changes', 'review my diff', 'is this…"
allowed-tools:
- Read
- Write
- Edit
- Bash
- Glob
- Grep
- Agent
- AskUserQuestion
argument-hint: "<PR URL, file path, or diff>"
---
# /ccc-code-review — alias → /ccc-review
> **Deduplicated (v6.1).** This skill is now an alias for **/ccc-review** — the canonical review workflow — branch audit, security/perf/correctness, and specialist-agent dispatch (covers diff review).
>
> Invoke /ccc-review instead. This stub is kept so the `/ccc-code-review` command still resolves and prior references do not break.
---
> ⚙️ **Fable contract:** plan before build · verifier ≠ worker · prove before alarm · loops need gates · leave durable state — `rules/fable-method.md`
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
