Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
cristoslc avatar

Code Review

  • 4 installs
  • Updated June 22, 2026
  • cristoslc/code-review-skill

Reviews code changes, diffs, or full codebases using parallel specialized agents for security, style, logic, and docs, with optional GitHub PR posting.

About

Runs a code review over a diff or full codebase by dispatching parallel specialized agents covering security, style, logic, and documentation. A developer uses it before merging a change or when auditing a project.

  • Parallel security/style/logic/docs agents with --full codebase mode
  • Optional gh CLI posting to GitHub and jq-based dispatch routing

Code Review by the numbers

  • 4 all-time installs (skills.sh)
  • Ranked #901 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
  • Data as of Jul 29, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cristoslc/code-review-skill --skill code-review

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs4
Last updatedJune 22, 2026
Repositorycristoslc/code-review-skill

What it does

Reviews code changes, diffs, or full codebases using parallel specialized agents for security, style, logic, and docs, with optional GitHub PR posting.

Files

SKILL.mdMarkdownGitHub ↗

Review code changes using parallel specialized agents. $ARGS

When to Use

  • User asks to review code changes or "review this".
  • Checking changes before merge.
  • User asks to "review the codebase" or "audit this project" (use --full).

When NOT to Use

  • General code exploration, linting, or formatting.

Payload

{
  "platform": "local|github|forgejo",
  "diff_method": "git-ref-diff|full-codebase",
  "dispatch": "specialist|segment",
  "agents": ["security", "style", "logic", "docs"]
}
  • dispatch defaults to "specialist". Only affects full-codebase mode.
  • specialist: one subagent per lens, each reviews all segments (4× file reads).
  • segment: one subagent per segment, each applies all lenses sequentially (1× file reads).
  • Both guarantee every line is reviewed under every specialization.

How to Run

Call generate.sh --phase init with the JSON payload. Follow the next_phase and prompt fields in each response to proceed. Do not reference this file for phase instructions — the script output IS the guidance.

Common Mistakes

  • Skipping phases — Call generate.sh for each phase in sequence.
  • Following this file instead of the prompt — The prompt from generate.sh is the authoritative guide for each phase.
  • Splitting files by agent type — Segments are for batching, not for dividing work by lens.
  • Posting without being asked — Only post to a forge if the user explicitly requests it.
  • Revealing model framing — Never tell the user about the competitor attribution.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.