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

Code Review

by yamcodes in yamcodes/arkenv

Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace.

MITAuto-check passedDevelopment

Install Code Review

skills CLI
$ npx skills add yamcodes/arkenv --skill code-review -a claude-code

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

GitHub CLI
$ gh skill install yamcodes/arkenv 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/yamcodes/arkenv.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/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
145
Token cost
~1.4k tokens
SKILL.md length
661 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace.

  • Works in 8 steps: Locate current PR and comments → Parse and analyze comments → Implement the fixes → …
  • The user mentions code reviews
  • SKILL.md covers Workflow Selection, Mode A: Address / Fix Review… and Mode B: Perform Code Review
  • Calls gh, git and pnpm

What it does

Code Review is an agent skill from yamcodes/arkenv. Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace. Make sure to use this skill whenever the user mentions code reviews, addressing PR reviews, fixing PR comments, resolving review feedback, performing a code review, or running '/code-review', even if they don't explicitly name GitHub or the PR number.

Its SKILL.md is about 1.4k 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 and Pull requests. It works with GitHub. The repository describes itself as: ⛯ Typesafe environment variables with ArkType, Zod, or Valibot. The licence is MIT.

When your agent uses it

  • The user mentions code reviews
  • Addressing PR reviews
  • Fixing PR comments
  • Resolving review feedback

Example prompts

  • “/code-review”
  • “/code-review”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Locate current PR and comments
  2. Parse and analyze comments
  3. Implement the fixes
  4. Verify changes
  5. Report results & comment back
  6. Retrieve changes
  7. Analyze the changes
  8. Report review findings

What it can do on your machine

Read from SKILL.md and the folder at commit 74b3732. 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
    • pnpm
    • npm
    • tsc

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

  • Network

    No URLs in SKILL.md. Its commands use gh, git, pnpm and npm, 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 1.4k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 661 words of instructions outside code blocks.

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

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 yamcodes/arkenv at commit 74b3732, republished under its MIT licence (© yamcodes). 661 words, ~1,357 tokens.

Download SKILL.mdSave it as .claude/skills/code-review/SKILL.md (or your agent's skills folder).
name
code-review
description
Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace. Make sure to use this skill whenever the user mentions code reviews, addressing PR reviews, fixing PR comments, resolving review feedback, performing a code review, or running '/code-review', even if they don't explicitly name GitHub or the PR number.
metadata.internal
true

Code Review

A dual-purpose skill to either (1) systematically retrieve and address pull request review comments on GitHub, or (2) perform a code review on changes in the workspace.

Workflow Selection

At the start of execution, identify the user's intent:

  • Mode A: Address / Fix Review Comments: Follow this mode if the user wants to address, fix, or resolve comments/feedback from a prior or active review (e.g., "fix PR comments", "address review notes", "resolve feedback", "address /code-review").
  • Mode B: Perform Code Review: Follow this mode if the user wants a review of their changes or the current workspace (e.g., "review my code", "check these changes", "do a code review", "/code-review").

Mode A: Address / Fix Review Comments

Systematically retrieve and fix comments from a PR review.

1. Locate current PR and comments
  • Run git status to find the current branch.
  • Run gh pr status to find the active pull request number and repository information.
  • Fetch Comments (Avoid Missing Inline Comments): Standard commands like gh pr view <PR_NUMBER> --comments only return high-level conversation summaries and completely omit inline code review comments made in the diff. To reliably retrieve the complete list of inline review comments, query the GitHub API directly:
    bash
    gh api repos/:owner/:repo/pulls/<PR_NUMBER>/comments --jq '.[] | {id, path, line, body}'
2. Parse and analyze comments
  • Extract the list of review comments. Focus on unresolved or actionable requests.
  • For each comment, identify the affected file path, line numbers, and expected outcome.
  • Check for Stale/Addressed Comments: Before making any code modifications, verify if the comment is already addressed or stale (e.g. if the target code has already been changed or deleted in a recent commit). Mark such comments as "Stale/Already Addressed" and skip them.
  • Handle Ambiguity / Ask for Clarification: If a comment is ambiguous, lacks context, or if you are unsure of the best implementation path, STOP and ask the user for clarification. Do not make risky assumptions.
3. Implement the fixes
  • View the surrounding code using the view_file tool to understand context.
  • Update the code using replace_file_content or multi_replace_file_content. Keep changes minimal and adhere strictly to the codebase's existing code style, imports, and naming patterns.
4. Verify changes
  • Compile/build the package (e.g., pnpm build, npm run build, or tsc --noEmit).
  • Run the test suite (e.g., pnpm test, npm test, or vitest) to ensure all tests pass.
  • Run size limit checks if applicable.
Show full SKILL.md (283 more words)Show less
5. Report results & comment back
  • Present a clear markdown table summarizing:
    • Review comment / concern.
    • File and lines changed.
    • Action taken (e.g., "Fixed", "Already Addressed", "Skipped").
    • Verification status.
  • Comment and Resolve on PR: Always reply to and resolve addressed threads on GitHub:
    • Reply: Post a reply to the thread using the REST API (with the database ID of the last comment):
      bash
      gh api -X POST /repos/:owner/:repo/pulls/<PR_NUMBER>/comments/<comment_id>/replies -f body="Addressed in latest commit."
    • Resolve Thread: Mark the thread as resolved using the GraphQL API (using the GraphQL thread ID PRRT_...):
      bash
      gh api graphql -F threadId="<thread_id>" -f query='
  mutation($threadId: ID!) {
    resolveReviewThread(input: { threadId: $threadId }) {
      thread { id isResolved }
    }
  }
'
    • General Comment: To add a general comment to the PR:
      bash
      gh pr comment <PR_NUMBER> --body "Addressed review comments: ..."

Mode B: Perform Code Review

Perform a high-quality, professional code review of the workspace changes.

1. Retrieve changes
  • Run git status to check modified files.
  • Run git diff (or compare branches) to retrieve the full diff of the changes under review.
2. Analyze the changes

Review the diff/code for:

  • Correctness & Bugs: Off-by-one errors, edge cases, incorrect conditional logic.
  • TypeScript & Types: Stale or weak types, unsafe casts, unused imports or variables.
  • Dead Code: Functions, imports, or files that are defined but never used.
  • Stale JSDoc & Docs: Stale doc comments that refer to renamed functions or old signatures.
  • Architectural Patterns: Consistency with the repository's architecture (e.g. modular structure, proper abstraction boundaries).
3. Report review findings

Output the code review structured by file:

  • For each file, list specific findings with line numbers and recommendations.
  • Categorize findings into:
    • ⚠️ Critical / Issues: Bugs, type/compilation errors, or logic issues.
    • ℹ️ Refactors / Cleanup: Dead code, unused imports, stale JSDoc.
    • 💡 Suggestions / Nits: Minor styling, readability improvements, or alternative approaches.

© yamcodes, 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 skills/code-review of yamcodes/arkenv.

Open the folder on GitHubat commit 74b3732

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 skillyamcodes/arkenv145—~1.4kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
GitHub Review Iterationprisma/orm48k—~2.2kAutomated safety check: PassApache-2.0
PR Review State Fetchprisma/orm48k—~767Automated safety check: PassApache-2.0
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
Fastlane Pull Request Reviewfastlane/fastlane42k—~550Automated safety check: PassMIT

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

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • PR Review State Fetch

    prisma/orm

    Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated today
    DevelopmentAuto-check passed

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Fastlane Pull Request Review

    fastlane/fastlane

    Reviews a fastlane pull request against its linked issue and the project guides, separating blocking from non-blocking findings and handling vulnerabilities privately.

    42k GitHub stars~550 tokensUpdated today
    DevelopmentAuto-check passed

  • Pull Request Reviewer for daisyUI

    saadeghi/daisyui

    Reviews open pull requests in the daisyUI repository using read-only GitHub data and isolated base-versus-PR checks, then writes a merge verdict report.

    43k GitHub stars~766 tokensUpdated 8 days ago
    DevelopmentAuto-check passed

More from yamcodes/arkenv

All 20 skills in this repo

  • Hallmark

    yamcodes/arkenv

    Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots.

    145 GitHub starsUsed in 4 repos~18k tokens
    Auto-check passed

  • Bulletproof React

    yamcodes/arkenv

    Bulletproof React architecture patterns for scalable, maintainable applications.

    145 GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Arkenv

    yamcodes/arkenv

    Answer questions about ArkEnv and help implement environment variable validation.

    145 GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Forward Port

    yamcodes/arkenv

    Manually forward-ports merged dev (v0) changes to the v1 branch, adapting code to v1's package layout and changeset names.

    145 GitHub stars~970 tokensUpdated today
    Auto-check passed

  • Groom Issue

    yamcodes/arkenv

    Groom a poorly written issue by grilling the user to clarify requirements, updating the issue on GitHub via the gh cli, and utilizing the triage skill to apply the correct label and add an agent…

    145 GitHub stars~1k tokensUpdated today
    Auto-check passed

  • Internalize Skill

    yamcodes/arkenv

    Move newly installed skills from '.agents/skills/' to the project's root 'skills/' directory, with options to rename and attribute them, and mark them as internal.

    145 GitHub stars~750 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Code Review

What does Code Review do?

Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace. Code Review is an agent skill from yamcodes/arkenv. Fetch, analyze, and address code reviews and comments on GitHub, or perform a code review on changes in the workspace.

When should I use Code Review?

Code Review fits situations like: the user mentions code reviews; addressing PR reviews; fixing PR comments; resolving review feedback.

How do I install Code Review in Claude Code?

Run `npx skills add yamcodes/arkenv --skill code-review -a claude-code`. Or copy the skill folder (skills/code-review in yamcodes/arkenv) 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 yamcodes/arkenv --skill code-review -a codex`. Or copy the skill folder (skills/code-review in yamcodes/arkenv) 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 yamcodes/arkenv --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 (gh, git, pnpm, npm and tsc).

Does Code Review access the network?

SKILL.md contains no URLs. Its commands use gh, git and npm, 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 1.4k tokens (SKILL.md is roughly 5.4k 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), GitHub Review Iteration (prisma/orm, 48k stars), PR Review State Fetch (prisma/orm, 48k stars) and PR Finalize Review (microsoft/garnet, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Review?

yamcodes (a GitHub user) maintains it in yamcodes/arkenv, which has 145 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 8, 2026.

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