Receiving Code Review
Use when processing code review feedback. Technical evaluation of feedback, verify before implementing. No performative agreement or gratitude.
Install
/plugin marketplace add Freddy-CHEN-ux/00_claude_skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Freddy-CHEN-ux/00_claude_skills --skill receiving-code-reviewgit clone --depth 1 https://github.com/Freddy-CHEN-ux/00_claude_skills.git /tmp/00_claude_skills
mkdir -p ~/.claude/skills
cp -r /tmp/00_claude_skills/skills/receiving-code-review ~/.claude/skills/receiving-code-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Receiving Code Review ## Core Principle **Verify before implementing. Ask before assuming. Technical correctness over social comfort.** ## Overview Code review feedback requires technical evaluation, not performative agreement. This skill teaches how to receive, evaluate, and implement feedback professionally. ## The Iron Laws ### Law 1: Technical Evaluation Required **Never blindly accept feedback.** Verify it's technically correct first. ### Law 2: No Performative Agreement **Forbidden phrases:** - ❌ "You're absolutely right!" - ❌ "Great point!" - ❌ "Good catch!" - ❌ "Thanks for the feedback!" - ❌ "I should have thought of that!" **Why forbidden:** These are social lubricants, not technical responses. They signal submission rather than evaluation. ### Law 3: Verify Against Codebase **Check actual code before responding.** Reviewer may be wrong or looking at old version. ## Response Pattern (The Six Steps) ### Step 1: READ Read feedback completely without reacting. ``` Reviewer feedback received: "This function does too much. Split into smaller functions." [Read completely, don't respond yet] ``` ### Step 2: UNDERSTAND Restate the requirement to confirm understanding.
Details
- Skill name
receiving-code-review- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/receiving-code-review/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Receiving Code Review skill do?
Use when processing code review feedback. Technical evaluation of feedback, verify before implementing. No performative agreement or gratitude.
How do I install the Receiving Code Review skill?
Claude Code plugin: /plugin marketplace add Freddy-CHEN-ux/00_claude_skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Receiving Code Review popular?
It lives in Freddy-CHEN-ux/00_claude_skills, which has 8 GitHub stars and 3 forks.
Related skills
Add Integration
8Freddy-CHEN-ux/00_claude_skills
Build a new API integration for Nexus. Load when user mentions "add integration", "new integration", "integrate with", "connect to [service]", or "build [service] integration". Interactive workflow that discovers API endpoints, plans the integration, and creates a project for implementation.
AI Agents
8Freddy-CHEN-ux/00_claude_skills
Production-grade AI agent patterns with MCP integration, agentic RAG, handoff orchestration, multi-layer guardrails, and observability (modern best practices)
AI LLM
8Freddy-CHEN-ux/00_claude_skills
Production LLM engineering skill. Covers strategy selection (prompting vs RAG vs fine-tuning), dataset design, PEFT/LoRA, evaluation workflows, deployment handoff to inference serving, and lifecycle operations with cost/safety controls.
Requesting Code Review
8Freddy-CHEN-ux/00_claude_skills
Use when completing tasks or major features. Know when and how to request reviews. Provides git commit range to code-reviewer agent.
PR Writer
5vnovakovits/claude-skills
Write, scope, size, and review pull requests that are fast and safe to review and merge. Grounded in Google's Engineering Practices, GitHub's PR guidance, the SmartBear/Cisco review study, Conventional Commits, LLVM's AI tool policy and agentic-PR research, plus delivery practice (expand/contract migrations, flags, observability gates). Covers splitting and sizing, Conventional-Commit titles, a stand-alone description (what/why, Mermaid diagrams of only what changed: Example Mapping for a policy, Event Storming for a process, sequence for an interaction, contracts crossed, confidence card, tes
Retro Points
5vnovakovits/claude-skills
Turn a discussion into retrospective points for a team's daily retro. Called on the current conversation, a pasted thread, a file, or a ticket or PR, it finds what slowed the team down, traces each item from event to pattern to the structure and belief behind it, names the system archetype, runs the systems-thinking iceberg on recurring points, proposes one structural experiment per pattern, scores it for impact, and recommends what the retro should open with. Built on Kerth's Prime Directive, Derby & Larsen's phases, Toyota Kata's daily improvement cycle, a multi-branch 5 Whys repaired with A
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.