Agent skill

Receiving Code Review

How to handle code review feedback with technical rigor. An agent skill from TechDufus/oh-my-claude.

MITAuto-check passedDevelopment

Install Receiving Code Review

skills CLI

$ npx skills add TechDufus/oh-my-claude --skill receiving-code-review -a claude-code

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

GitHub CLI

$ gh skill install TechDufus/oh-my-claude receiving-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/TechDufus/oh-my-claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/oh-my-claude/skills/receiving-code-review .claude/skills/receiving-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/

Paste into Claude Code

Install the "receiving-code-review" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/receiving-code-review into .claude/skills/receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "receiving-code-review", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/receiving-code-review

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add TechDufus/oh-my-claude --skill receiving-code-review -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install TechDufus/oh-my-claude receiving-code-review --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/oh-my-claude/skills/receiving-code-review .agents/skills/receiving-code-review && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "receiving-code-review" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/receiving-code-review into .agents/skills/receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "receiving-code-review", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add TechDufus/oh-my-claude --skill receiving-code-review -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install TechDufus/oh-my-claude receiving-code-review --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/oh-my-claude/skills/receiving-code-review .cursor/skills/receiving-code-review && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "receiving-code-review" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/receiving-code-review into .cursor/skills/receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "receiving-code-review", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/TechDufus/oh-my-claude.git --path plugins/oh-my-claude/skills/receiving-code-review

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add TechDufus/oh-my-claude --skill receiving-code-review -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install TechDufus/oh-my-claude receiving-code-review --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/oh-my-claude/skills/receiving-code-review .gemini/skills/receiving-code-review && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "receiving-code-review" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/receiving-code-review into .gemini/skills/receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "receiving-code-review", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install TechDufus/oh-my-claude receiving-code-review

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add TechDufus/oh-my-claude --skill receiving-code-review -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/oh-my-claude/skills/receiving-code-review .github/skills/receiving-code-review && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "receiving-code-review" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/receiving-code-review into .github/skills/receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "receiving-code-review", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add TechDufus/oh-my-claude --skill receiving-code-review -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install TechDufus/oh-my-claude receiving-code-review --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/TechDufus/oh-my-claude.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/oh-my-claude/skills/receiving-code-review .opencode/skills/receiving-code-review && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "receiving-code-review" agent skill from https://github.com/TechDufus/oh-my-claude/tree/main/plugins/oh-my-claude/skills/receiving-code-review into .opencode/skills/receiving-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "receiving-code-review", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: receiving-code-review
GitHub stars: 174
Token cost: ~1.1k tokens
SKILL.md length: 536 words
Files: 1
Skills in repo: 12
Repo updated: Jul 13, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

How to handle code review feedback with technical rigor. An agent skill from TechDufus/oh-my-claude.

Works in 5 steps: Clarify unclear items first (don't build… → Blocking/critical issues (things that… → Simple fixes (typos, naming, formatting) → …
Receiving review comments from code-reviewer agent
SKILL.md covers When to Apply, Response Pattern, Forbidden Responses and Source-Specific Handling, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Receiving Code Review is an agent skill from TechDufus/oh-my-claude. How to handle code review feedback with technical rigor. Use when receiving review comments from code-reviewer agent, PR reviews, or external feedback. Triggers on: 'review feedback', 'address review', 'fix review comments', 'code review response'.

Its SKILL.md is about 1.1k 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. The repository describes itself as: Add ultrawork to any prompt for maximum parallel execution. The licence is MIT.

When your agent uses it

Receiving review comments from code-reviewer agent
External feedback
: review feedback
Fix review comments

Example prompts

“review feedback”
“address review”
“fix review comments”
“/receiving-code-review”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Clarify unclear items first (don't build on misunderstanding)
Blocking/critical issues (things that prevent the code from working)
Simple fixes (typos, naming, formatting)
Complex fixes (refactors, architectural changes)
Test each fix independently

What it can do on your machine

Read from SKILL.md and the folder at commit ede75db. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Receiving Code Review loads about 1.1k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 536 words of instructions outside code blocks.

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

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 TechDufus/oh-my-claude at commit ede75db, republished under its MIT licence (© TechDufus). 536 words, ~1,111 tokens.

Download SKILL.mdSave it as .claude/skills/receiving-code-review/SKILL.md (or your agent's skills folder).

name: receiving-code-review
description: How to handle code review feedback with technical rigor. Use when receiving review comments from code-reviewer agent, PR reviews, or external feedback. Triggers on: 'review feedback', 'address review', 'fix review comments', 'code review response'.

Receiving Code Review Skill

How to handle review feedback with technical rigor, not performative agreement.

When to Apply

After receiving code-reviewer agent output
PR review comments from teammates or external reviewers
External feedback on implementation decisions
When told to "address review comments" or "fix review feedback"

Response Pattern

READ -> UNDERSTAND -> VERIFY -> EVALUATE -> RESPOND -> IMPLEMENT

READ

Read the full review. Don't skim, don't react immediately. Take in every comment before acting on any of them. Later comments may contradict or contextualize earlier ones.

UNDERSTAND

For each issue, understand what's actually being flagged. Restate in your own words: "This comment is about X because Y." If you can't restate it, you don't understand it yet.

VERIFY

Check if the reviewer's claim is factually correct. Read the code they reference. Don't assume they're right or wrong -- look at the actual code at {file}:{line}.

EVALUATE

Is this a real issue? Does the suggested fix actually improve things? Is the effort justified given the impact? Not all feedback requires action.

RESPOND

Technical response only:

Agree with reasoning: "Correct. The null check is missing at line X. Fixing."
Disagree with evidence: "The review flags X, but {file}:{line} shows Y handles this case."
Ask for clarification: "The comment suggests X. Is the concern about safety or performance?"

IMPLEMENT

Fix in order: clarify unclear items -> blocking issues -> simple fixes -> complex fixes. Test each fix independently before moving to the next.

Forbidden Responses

These responses indicate you're people-pleasing, not engineering:

"You're absolutely right!" -- Performative agreement without understanding
"Great point!" -- Flattery is not technical discourse
"I'll fix that right away!" -- Understand before acting
"Of course, makes total sense!" -- Does it? Or are you people-pleasing?

Instead: "The review identifies X. Checking... [evidence]. This is correct because [reason]. Fixing."

Or: "The review suggests X, but [counter-evidence]. Keeping current approach because [reason]."

Source-Specific Handling

Source	Trust Level	Response Style
Human partner	High context	Clarify intent, implement thoughtfully
External reviewer	Medium context	Verify claims against code, ask about unknowns
code-reviewer agent	Systematic but no context	Cross-reference with requirements, verify specifics

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

When to Push Back

Technically incorrect -- "The review suggests X, but the code at {file}:{line} shows Y"
YAGNI -- "This adds complexity for a hypothetical scenario. Current implementation handles all existing cases"
Breaks existing functionality -- "This change would break {specific behavior} because {evidence}"
Missing context -- "The review assumes X, but the requirement specifies Y (see {reference})"

Pushing back is not adversarial. It's quality control. Reviewers benefit from knowing when their feedback misses context.

Implementation Order

Clarify unclear items first (don't build on misunderstanding)
Blocking/critical issues (things that prevent the code from working)
Simple fixes (typos, naming, formatting)
Complex fixes (refactors, architectural changes)
Test each fix independently

Common Mistakes

Mistake	Why It's Wrong	Do This Instead
Fix everything without reading all comments	Later comments may contradict earlier ones	Read ALL comments first
Performative agreement	Hides misunderstanding	Respond with technical reasoning
Batch all fixes in one commit	Can't isolate if something breaks	One logical change per commit
Skip re-testing after fixes	Fixes introduce new bugs	Test after every change
Ignore minor issues	They accumulate	Fix or explicitly defer with reason

The Bottom Line

Review feedback is data, not judgment. Evaluate it technically, respond with evidence, implement with discipline.

Files

Just SKILL.md in plugins/oh-my-claude/skills/receiving-code-review of TechDufus/oh-my-claude.

Open the folder on GitHubat commit ede75db

Compare with similar skills

Receiving 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.

Receiving Code Review compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Receiving Code Review this skillTechDufus/oh-my-claude	174	—	~1.1k	Automated safety check: Pass	MIT	2 mo ago
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	2 days ago
WooCommerce Code Reviewwoocommerce/woocommerce	11k	3 repos	~1.1k	Automated safety check: Pass	Custom licence	today
Open Code Review CLIalibaba/open-code-review	45k	—	~3.1k	Automated safety check: Pass	Apache-2.0	today
GitHub Review Iterationprisma/orm	48k	—	~2.2k	Automated safety check: Pass	Apache-2.0	today
Understand Diff AnalysisEgonex-AI/Understand-Anything	86k	—	~1.4k	Automated safety check: Pass	MIT	today

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
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
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
45k GitHub stars~3.1k tokensUpdated today
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
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
86k GitHub stars~1.4k tokensUpdated today
DevelopmentAuto-check passed
Code Review
flutter/flutter
Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback.
179k GitHub stars~1.4k tokensUpdated today
DevelopmentAuto-check passed

Questions about Receiving Code Review

What does Receiving Code Review do?

How to handle code review feedback with technical rigor. An agent skill from TechDufus/oh-my-claude. Receiving Code Review is an agent skill from TechDufus/oh-my-claude. How to handle code review feedback with technical rigor.

When should I use Receiving Code Review?

Receiving Code Review fits situations like: receiving review comments from code-reviewer agent; external feedback; : review feedback; fix review comments.

How do I install Receiving Code Review in Claude Code?

Run `npx skills add TechDufus/oh-my-claude --skill receiving-code-review -a claude-code`. Or copy the skill folder (plugins/oh-my-claude/skills/receiving-code-review in TechDufus/oh-my-claude) into .claude/skills/receiving-code-review in your project. Claude Code loads it when a task matches its description.

How do I install Receiving Code Review in Codex?

Run `npx skills add TechDufus/oh-my-claude --skill receiving-code-review -a codex`. Or copy the skill folder (plugins/oh-my-claude/skills/receiving-code-review in TechDufus/oh-my-claude) into .agents/skills/receiving-code-review in your project. Codex loads it when a task matches its description.

Can I use Receiving 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 TechDufus/oh-my-claude --skill receiving-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/receiving-code-review, .gemini/skills/receiving-code-review, .github/skills/receiving-code-review and .opencode/skills/receiving-code-review in your project.

What does Receiving Code Review need to run?

SKILL.md names no scripts, command-line tools or credentials: Receiving Code Review is instructions for the agent only.

Does Receiving Code Review access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

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

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

About 1.1k tokens (SKILL.md is roughly 4.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 Receiving Code Review?

Skills that share tags, products or a category with Receiving Code Review: PR Babysitter (openinterpreter/openinterpreter, 69k stars), WooCommerce Code Review (woocommerce/woocommerce, 11k stars), Open Code Review CLI (alibaba/open-code-review, 45k stars) and GitHub Review Iteration (prisma/orm, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Receiving Code Review?

TechDufus (a GitHub user) maintains it in TechDufus/oh-my-claude, which has 174 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on July 13, 2026.

Source: TechDufus/oh-my-claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Receiving Code Review

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Receiving Code Review Skill

When to Apply

Response Pattern

READ

UNDERSTAND

VERIFY

EVALUATE

RESPOND

IMPLEMENT

Forbidden Responses

Source-Specific Handling

When to Push Back

Implementation Order

Common Mistakes

The Bottom Line

Files

Compare with similar skills

Similar skills

More from TechDufus/oh-my-claude

Related

Questions about Receiving Code Review