Agent skill

Code Review

by damianvtran in damianvtran/local-operator

Reviewing code for defects: diff-first reading, severity classification, evidence over inference, finding caps, and terminal verdicts.

MITAuto-check passedDevelopment

Install Code Review

skills CLI
$ npx skills add damianvtran/local-operator --skill code-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install damianvtran/local-operator code-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/damianvtran/local-operator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/local_operator/skills/builtin/code-review .claude/skills/code-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
code-review
GitHub stars
217
Token cost
~672 tokens
SKILL.md length
390 words
Files
1
Repo updated
First seen
Licence
MIT

At a glance

Reviewing code for defects: diff-first reading, severity classification, evidence over inference, finding caps, and terminal verdicts.

  • Reviewing a diff
  • SKILL.md covers Read the diff first, Classify every finding, Evidence over inference and Remediation rounds (round 2…, plus 2 more sections
  • Calls git
  • Auditing someone elses work

What it does

Code Review is an agent skill from damianvtran/local-operator. Reviewing code for defects: diff-first reading, severity classification, evidence over inference, finding caps, and terminal verdicts. Use when reviewing a diff, PR, or patch, or auditing someone else's work.

Its SKILL.md is about 670 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Code review. The repository describes itself as: An open-source AI agent hub for your own machine: build organizations of collaborating agents that message each other, run in the background around the clock, and share your… The licence is MIT.

When your agent uses it

  • Reviewing a diff
  • Auditing someone elses work

Example prompts

  • “/code-review”

What it can do on your machine

Read from SKILL.md and the folder at commit 05e4c97. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Code Review loads about 672 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 390 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~672

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from damianvtran/local-operator at commit 05e4c97, republished under its MIT licence (© damianvtran). 390 words, ~672 tokens.

Download SKILL.mdSave it as .claude/skills/code-review/SKILL.md (or your agent's skills folder).
name
code-review
description
Reviewing code for defects: diff-first reading, severity classification, evidence over inference, finding caps, and terminal verdicts. Use when reviewing a diff, PR, or patch, or auditing someone else's work.

Code review

The same practice for any agent: reviewing a diff, a patch, or another agent's work.

Read the diff first

  • git diff <base>..<head> (or the PR's diff) IS the review. Read the tree only where the diff raises a question you can state.
  • Open a file when you can name the question it answers; re-reading files you already read is waste.
  • Review what changed plus what it touches: callers, shared state, and the tests near the change.

Classify every finding

SeverityMeans
BLOCKERWrong, unsafe, or loses data. Ship it and something breaks.
MAJORA real defect or missing case that will bite, but not stop-ship.
MINORCorrectness-preserving improvement.
NITStyle, naming, wording.
  • Caps: at most 5 MINOR and 5 NIT per round, the highest-value ones. A long tail of nits buries the blockers and costs a remediation round to answer.
  • Severity is about consequence, not effort to fix. Do not inflate; do not deflate to avoid an awkward round.

Evidence over inference

  • Every finding carries a location: file, line, and the code path. Without one it is a lead, not a finding.
  • Reproduce cheaply where possible: the targeted test, the query, a tiny probe. A finding you reproduced outranks one you reasoned to.
  • Where you cite a number or status, derive it or name its source. A value read from a summary is a lead.
  • Say plainly when nothing blocks. Padding a report to look thorough is a failure mode; so is agreeing to be agreeable.
Show full SKILL.md (142 more words)Show less

Remediation rounds (round 2 and later)

  • Scope to the delta: git diff <previous_reviewed_head>..<current_head>. Verify the fixes; do not re-audit unchanged, previously approved files.
  • No new out-of-scope findings; note them as follow-ups instead.
  • A fix that unexpectedly touches more is in scope again: check its blast radius.

Verdict

  • End with a terminal verdict: with no BLOCKER and no MAJOR left, the verdict is clean and you state the round is terminal; remaining minors and nits are follow-ups, not a reason for another round.
  • Language is precise: "blocked on X", "clean with follow-ups". Never "LGTM" with no checks behind it.

Red flags

  • Reviewing the tree instead of the diff.
  • Speculative findings ("there might be a race") with no code path named.
  • Silent scope creep into unrelated code.
  • Style preferences dressed as defects.
  • A finding the author cannot act on because it names no change.

© damianvtran, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in local_operator/skills/builtin/code-review of damianvtran/local-operator.

Open the folder on GitHubat commit 05e4c97

Compare with similar skills

Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Code Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Review this skilldamianvtran/local-operator217—~672Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k4 repos~1.1kAutomated safety check: PassMIT
Backend Code Reviewlangflow-ai/langflow155k—~3.5kAutomated safety check: NotesMIT
Mole Bug Patternstw93/Mole70k—~2kAutomated safety check: PassGPL-3.0
Backend Code Reviewlanggenius/dify158k—~676Automated safety check: PassCustom licence

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 4 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Backend Code Review

    langflow-ai/langflow

    Review backend code for quality, security, maintainability, and best practices based on established checklist rules.

    155k GitHub stars~3.5k tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.

    70k GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed
  • Backend Code Review

    langgenius/dify

    Reviews backend code under api/ for concrete, reproducible defects, routes to rule packs for architecture, schema, repositories and SQLAlchemy, and ranks findings from P0 to P3.

    158k GitHub stars~676 tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed

More from damianvtran/local-operator

All 8 skills in this repo
  • Design QA

    damianvtran/local-operator

    Deterministic design review for UI/UX on web and terminal screens: measure contrast, spacing, overlap, clipping and copy defects, then judge the rest.

    217 GitHub stars~729 tokensUpdated today
    Auto-check passed
  • Skill Authoring

    damianvtran/local-operator

    Writing and improving agent skills: description as routing signal, progressive disclosure, token budgets, testing before shipping, and improving from repeated mistakes.

    217 GitHub stars~748 tokensUpdated today
    Auto-check passed
  • Data Analysis

    damianvtran/local-operator

    Analysing data rigorously: profile before trust (keys, missingness), reproducible queries, provenance per number, units and sanity checks.

    217 GitHub stars~709 tokensUpdated today
    Auto-check passed
  • Financial Analysis

    damianvtran/local-operator

    Financial figures done carefully: periods and fiscal calendars, units and currencies, reconciliation, magnitude sanity checks, sourced assumptions.

    217 GitHub stars~657 tokensUpdated today
    Auto-check passed
  • Frontend Design

    damianvtran/local-operator

    Designing interfaces with a deliberate point of view: plan before pixels, avoid the generic-default look, typography and colour discipline, a quality floor that is not negotiable.

    217 GitHub stars~773 tokensUpdated today
    Auto-check passed
  • Responding To Review

    damianvtran/local-operator

    Answering review findings: verify each claim before implementing, no performative agreement, per-item fix/reject/defer with evidence, one batched remediation round.

    217 GitHub stars~616 tokensUpdated today
    Auto-check passed

Categories

Questions about Code Review

What does Code Review do?

Reviewing code for defects: diff-first reading, severity classification, evidence over inference, finding caps, and terminal verdicts. Code Review is an agent skill from damianvtran/local-operator. Reviewing code for defects: diff-first reading, severity classification, evidence over inference, finding caps, and terminal verdicts.

When should I use Code Review?

Code Review fits situations like: reviewing a diff; auditing someone elses work.

How do I install Code Review in Claude Code?

Run `npx skills add damianvtran/local-operator --skill code-review -a claude-code`. Or copy the skill folder (local_operator/skills/builtin/code-review in damianvtran/local-operator) into .claude/skills/code-review in your project. Claude Code loads it when a task matches its description.

How do I install Code Review in Codex?

Run `npx skills add damianvtran/local-operator --skill code-review -a codex`. Or copy the skill folder (local_operator/skills/builtin/code-review in damianvtran/local-operator) into .agents/skills/code-review in your project. Codex loads it when a task matches its description.

Can I use Code Review in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add damianvtran/local-operator --skill code-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-review, .gemini/skills/code-review, .github/skills/code-review and .opencode/skills/code-review in your project.

What does Code Review need to run?

Going by SKILL.md and its folder, Code Review needs the command-line tools its instructions call (git).

Does Code Review access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Code Review safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Code Review use?

Code Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Review use?

About 672 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Code Review?

Skills that share tags, products or a category with Code Review: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Backend Code Review (langflow-ai/langflow, 155k stars) and Mole Bug Patterns (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Review?

damianvtran (a GitHub user) maintains it in damianvtran/local-operator, which has 217 GitHub stars. The repository was last updated on October 11, 2026.

Source: damianvtran/local-operator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.