Skip to main content
ZICQ

Skills ZICQ category:Agent Workflows review

Review

Centralizes persona-driven code reviews (Fowler, Torvalds, Carmack, React core, etc.) so Claude can pick or combine expert viewpoints when the user asks for a code review or perspective-specific critique.

37 installs

Official URL:skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Centralizes persona-driven code reviews (Fowler, Torvalds, Carmack, React core, etc.) so Claude can pick or combine expert viewpoints when the user asks for a code review or perspective-specific critique.

When to use it

The official description does not include a separate “Use when”. Per the spec, agents activate this skill when the task matches keywords in that description.

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: Review Skill; Critical Workflow; General Checklist; Multi-Perspective Reviews; Persona References (load on demand). It includes spec-recommended sections: step-by-step instructions.

File analysis

File analysis: besides SKILL.md, the body references references/ai-reviewer.md, references/anders-reviewer.md, references/beck-reviewer.md, references/bjarne-reviewer.md, references/brendan-reviewer.md, references/carmack-reviewer.md. Those resources load on demand.

Review SkillCritical WorkflowGeneral ChecklistMulti-Perspective ReviewsPersona References (load on demand)

· allowed-tools:Read, Grep, Glob, Bash

Source category:skills.sh agent-skill

SKILL.md & Agent activation

Official spec ↗
name
review
description
Centralizes persona-driven code reviews (Fowler, Torvalds, Carmack, React core, etc.) so Claude can pick or combine expert viewpoints when the user asks for a code review or perspective-specific critique.
allowed-tools
Read, Grep, Glob, BashExperimental field; support depends on the client and does not grant permissions by itself.
  1. DiscoverThe client exposes names and descriptions to the agent.
  2. ActivateYour request or the task context selects the skill and loads its instructions.
  3. Load resourcesReferenced scripts, documentation and assets are used when needed.
Files referenced by the instructions · 12
  • references/ai-reviewer.md
  • references/anders-reviewer.md
  • references/beck-reviewer.md
  • references/bjarne-reviewer.md
  • references/brendan-reviewer.md
  • references/carmack-reviewer.md
  • references/dean-reviewer.md
  • references/dhh-reviewer.md
  • references/fowler-reviewer.md
  • references/github-reviewer.md
  • references/grace-reviewer.md
  • references/guido-reviewer.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "review" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-f7db3d7908f3efdd-Review.html
Save it as .cursor/skills/review/SKILL.md or .claude/skills/review/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/johnlindquist/claude instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/johnlindquist/claude' --list

npx skills add 'https://github.com/johnlindquist/claude' --skill 'review'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

Readable layout

name: review description: Centralizes persona-driven code reviews (Fowler, Torvalds, Carmack, React core, etc.) so Claude can pick or combine expert viewpoints when the user asks for a code review or perspective-specific critique. allowed-tools: Read, Grep, Glob, Bash

Review Skill

Unifies every reviewer persona into one Skill. Claude activates this Skill whenever code should be reviewed and then "lazy loads" the exact perspective by opening the reference docs linked below or by spawning persona-specific subagents.

Critical Workflow

REQUIRED: Before conducting ANY code review, you MUST load the relevant persona reference file(s) using the Read tool. These references contain the specific review priorities, perspective, and evaluation criteria for each reviewer persona.

  1. Collect the code/diff context plus the user's goals (bugs, architecture, performance, etc.).
  2. MANDATORY: Parse reviewer hints (e.g., "perf, react, typescript") and READ the matching reference file(s) directly using the Read tool BEFORE reviewing:
    • AI/ML concerns → Read references/ai-reviewer.md FIRST
    • Type system concerns → Read references/anders-reviewer.md FIRST
    • Testing/TDD concerns → Read references/beck-reviewer.md FIRST
    • Performance/abstraction → Read references/bjarne-reviewer.md FIRST
    • Innovation/pragmatism → Read references/brendan-reviewer.md FIRST
    • Low-level performance → Read references/carmack-reviewer.md FIRST
    • Distributed systems → Read references/dean-reviewer.md FIRST
    • Convention/simplicity → Read references/dhh-reviewer.md FIRST
    • Refactoring/architecture → Read references/fowler-reviewer.md FIRST
    • Collaboration/CI/CD → Read references/github-reviewer.md FIRST
    • Abstraction/modularity → Read references/grace-reviewer.md FIRST
    • Readability/Python → Read references/guido-reviewer.md FIRST
    • Portability/Java → Read references/james-reviewer.md FIRST
    • Compiler/tooling → Read references/lattner-reviewer.md FIRST
    • Systems/rigor → Read references/linus-reviewer.md FIRST
    • Developer joy/Ruby → Read references/matz-reviewer.md FIRST
    • Observability/tracing → Read references/perf-reviewer.md FIRST
    • React patterns → Read references/react-reviewer.md FIRST
    • Go/concurrency → Read references/rob-reviewer.md FIRST
    • Unix philosophy → Read references/unix-reviewer.md FIRST
  3. Apply the reviewer persona's perspective by following their specific guidance and priorities from the loaded reference.
  4. Cite specific files/lines, flag issues, and provide concrete recommendations.

DO NOT attempt to conduct a code review without first loading the appropriate persona reference file(s).

General Checklist

  • Understand inputs/outputs, dependencies, and expected behavior before judging the change.
  • Use the allowed tools (Read, Grep, Glob, Bash) to inspect implementation, history, and tests.
  • Evaluate correctness, safety, performance, maintainability, and user impact.
  • Flag missing tests, weak docs, regressions, or architectural drift; propose concrete fixes.
  • Summarize findings in severity order, then note risks, questions, and verification steps.

Multi-Perspective Reviews

When multiple personas are requested (e.g., "review this with Anders and React perspectives"):

  • Read each relevant reference file from the list below
  • Apply each perspective's priorities and concerns to the code
  • Synthesize findings: highlight where perspectives agree or conflict
  • Prioritize issues by severity across all perspectives

Persona References (load on demand)

  • AI Visionaries - adaptive systems, emergent behavior, data-driven design. Open instructions
  • Anders Hejlsberg - strong typing, language/tooling ergonomics, structured APIs. Open instructions
  • Kent Beck - TDD discipline, rapid feedback loops, adaptive design. Open instructions
  • Bjarne Stroustrup - performance via abstraction, type safety, disciplined engineering. Open instructions
  • Brendan Eich - rapid innovation, creative problem-solving, pragmatic experimentation. Open instructions
  • John Carmack - low-level excellence, graphics/perf tuning, precision thinking. Open instructions
  • Jeff Dean - planet-scale systems, efficiency, distributed reliability. Open instructions
  • DHH - opinionated conventions, developer autonomy, simplicity over ceremony. Open instructions
  • Martin Fowler - refactoring readiness, evolutionary architecture, intentional design. Open instructions
  • GitHub Generation - collaboration hygiene, docs, CI/CD automation. Open instructions
  • Grace Hopper & Barbara Liskov - abstraction integrity, substitutability, modular design. Open instructions
  • Guido van Rossum - readability, Pythonic simplicity, pragmatic clarity. Open instructions
  • James Gosling - JVM portability, API stability, backward compatibility. Open instructions
  • Chris Lattner - compiler/toolchain innovation, language interoperability, performance. Open instructions
  • Linus Torvalds - kernel-level rigor, patch discipline, brutally honest feedback. Open instructions
  • Yukihiro "Matz" Matsumoto - Ruby aesthetics, human-centric design, joy in code. Open instructions
  • Brendan Gregg & Liz Rice - observability, tracing, data-first performance analysis. Open instructions
  • React Core Maintainer - hooks, concurrent rendering, DX-focused component patterns. Open instructions
  • Rob Pike - Go/Unix minimalism, concurrency primitives, composable tooling. Open instructions
  • Unix Traditionalist - small sharp tools, composability, text-first automation. Open instructions

Each reference stays out of context until explicitly opened, keeping Claude's context lean while still giving fast access to the original, detailed reviewer guidance.

Related skills

Agent Workflows

Skill Creator

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that exte…

Agent Workflows

Clawdhub

Use the ClawdHub CLI to search, install, update, and publish agent skills from clawdhub.com. Use when you need to fetch new skills on the fl…

Agent Workflows

Agent Team Orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team …

Agent Workflows

Superpowers

Spec-first, TDD, subagent-driven software development workflow. Use when: (1) building any new feature or app — triggers brainstorm → plan →…