New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Review

by 0xku in 0xku/kon

Review code changes and return prioritized, actionable findings

MITAuto-check passedDevelopment

Install Review

skills CLI
$ npx skills add 0xku/kon --skill review -a claude-code

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

GitHub CLI
$ gh skill install 0xku/kon 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/0xku/kon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/kon/builtin_skills/review .claude/skills/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
review
GitHub stars
354
Token cost
~958 tokens
SKILL.md length
556 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Review code changes and return prioritized, actionable findings

  • Tasks that involve Code review
  • SKILL.md covers Target selection, Review rubric, Investigation guidance and Priority rubric, plus 1 more section
  • Calls gh and git

What it does

Review is an agent skill from 0xku/kon. Review code changes and return prioritized, actionable findings

Its SKILL.md is about 960 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: Kon is a minimal coding agent (and also a highly opinionated one). The licence is MIT.

When your agent uses it

  • Tasks that involve Code review

Example prompts

  • “/review”

What it can do on your machine

Read from SKILL.md and the folder at commit f5862a0. 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:

    • gh
    • git

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

  • Network

    No URLs in SKILL.md. Its commands use gh and 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

Review loads about 958 tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 556 words of instructions outside code blocks.

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

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 0xku/kon at commit f5862a0, republished under its MIT licence (© 0xku). 556 words, ~958 tokens.

Download SKILL.mdSave it as .claude/skills/review/SKILL.md (or your agent's skills folder).
name
review
description
Review code changes and return prioritized, actionable findings
register_cmd
true
cmd_info
review code changes

Review the requested code changes as if you are reviewing another engineer's PR.

User-provided target or constraints (honor these): $ARGUMENTS

Target selection

  • If no target is provided, review the current code changes: staged, unstaged, and untracked files.
  • If the user provides a base branch, review the changes that would merge into that branch. Find the merge base and inspect the diff from that commit.
  • If the user provides a commit SHA, review only the changes introduced by that commit.
  • If the user provides a PR number, PR URL, or text like PR#68 feat/headless-mode "feat: add non-interactive prompt mode", assume the GitHub CLI is available. Use gh pr view to inspect PR metadata, resolve the base/head branches, fetch as needed, compute the merge base, and review the PR diff. Do not checkout a different branch unless the user explicitly asks or confirms.
  • For PRs, do not assume the head branch exists on origin; it may live on a contributor fork. Prefer gh pr checkout --detach <number> only if checkout is acceptable, or fetch the head repository/ref reported by gh pr view --json headRepository,headRefName into a temporary remote/ref before diffing.
  • For a PR scenario such as /review PR#68 feat/headless-mode "feat: add non-interactive prompt mode", use the PR number/title/branch as hints, verify them with gh pr view 68, then review the code changes relative to the PR base branch.

Review rubric

Only report issues the original author would likely fix if they knew about them.

Flag a finding only when:

  • it meaningfully affects correctness, security, performance, reliability, or maintainability;
  • it is discrete and actionable;
  • it appears introduced by the reviewed change;
  • you can identify the affected code path or user scenario;
  • it is not merely a style preference, nit, or intentional behavior change.

Do not stop at the first issue. Return all qualifying findings. If there are no findings worth fixing, say so clearly.

Show full SKILL.md (245 more words)Show less

Investigation guidance

Use repository tools to inspect the actual diff and surrounding code. Prefer precise commands such as:

  • git status --short
  • git diff --staged
  • git diff
  • git diff <merge-base>...HEAD
  • git show <sha>
  • gh pr view <number> --json number,title,body,baseRefName,headRefName,url,author

Read nearby implementation and tests when needed to prove whether a suspected issue is real. Avoid speculative findings.

Priority rubric

Use these severity levels for finding titles:

  • [P0] — Drop everything to fix. Blocking release, operations, or major usage. Only use for universal issues that do not depend on assumptions about inputs.
  • [P1] — Urgent. Should be addressed in the next cycle.
  • [P2] — Normal. Should be fixed eventually.
  • [P3] — Low. Nice to have.

Finding format

For each finding, include:

  • priority tag in the title: [P0], [P1], [P2], or [P3];
  • concise title;
  • file path and line range;
  • one short paragraph explaining why this is a bug and when it matters;
  • confidence score if useful.

Keep line ranges as short as possible and make sure they overlap the reviewed diff when possible.

End with an overall verdict:

  • patch is correct if existing code/tests should not break and no blocking issues were found;
  • patch is incorrect if the patch has blocking correctness, security, reliability, or maintainability issues that should prevent merging.

Do not mark a patch incorrect for non-blocking issues such as style, formatting, typos, documentation nits, or ordinary [P2]/[P3] follow-ups unless they still indicate the patch should not merge.

Do not fix the code unless the user asks after the review.

© 0xku, 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 src/kon/builtin_skills/review of 0xku/kon.

Open the folder on GitHubat commit f5862a0

Compare with similar skills

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.

Review compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review this skill0xku/kon354—~958Automated safety check: PassMIT
PR ReviewNVIDIA/Megatron-LM18k—~839Automated safety check: PassApache-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 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

Similar skills

  • PR Review

    NVIDIA/Megatron-LM

    Official

    Review rubric for the /review pull-request command. An agent skill from NVIDIA/Megatron-LM.

    18k GitHub stars~839 tokensUpdated today
    DevelopmentAuto-check passed

  • 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 5 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

  • Mole Bug Patterns

    tw93/Mole

    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 yesterday
    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

More from 0xku/kon

  • Kon Tmux Test

    0xku/kon

    E2E testing of kon using tmux sessions; IMPORTANT: only trigger this skill when user asks for e2e testing of kon

    354 GitHub stars~2.8k tokensUpdated 6 days ago
    Auto-check passed

  • Init

    0xku/kon

    Create or update AGENTS.md for this repository. An agent skill from 0xku/kon.

    354 GitHub stars~900 tokensUpdated 6 days ago
    Auto-check passed

  • Kon Release Publish

    0xku/kon

    Tag, publish to PyPI, and create GitHub release for Kon with validation and rollback-safe steps

    354 GitHub stars~899 tokensUpdated 6 days ago
    Auto-check passed

Categories

Questions about Review

What does Review do?

Review code changes and return prioritized, actionable findings. Review is an agent skill from 0xku/kon.

When should I use Review?

Review fits situations like: tasks that involve Code review.

How do I install Review in Claude Code?

Run `npx skills add 0xku/kon --skill review -a claude-code`. Or copy the skill folder (src/kon/builtin_skills/review in 0xku/kon) into .claude/skills/review in your project. Claude Code loads it when a task matches its description.

How do I install Review in Codex?

Run `npx skills add 0xku/kon --skill review -a codex`. Or copy the skill folder (src/kon/builtin_skills/review in 0xku/kon) into .agents/skills/review in your project. Codex loads it when a task matches its description.

Can I use 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 0xku/kon --skill 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/review, .gemini/skills/review, .github/skills/review and .opencode/skills/review in your project.

What does Review need to run?

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

Does Review access the network?

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

Is 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 Review use?

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 Review use?

About 958 tokens (SKILL.md is roughly 3.8k 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 Review?

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

Who maintains Review?

0xku (a GitHub user) maintains it in 0xku/kon, which has 354 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 3, 2026.

Source: 0xku/kon on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.