Requesting Code Review
Use when completing tasks or major features. Know when and how to request reviews. Provides git commit range to code-reviewer agent.
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 requesting-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/requesting-code-review ~/.claude/skills/requesting-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
# Requesting Code Review ## Core Principle **Request reviews at logical completion points with clear context.** ## Overview Code review is most effective when requested at appropriate times with sufficient context. This skill defines when to request reviews and how to provide reviewers with what they need. ## When to Request Review ### Always Request Review: - ✅ After completing individual planned tasks - ✅ Upon finishing major features before merging - ✅ Before merging to main/master branch - ✅ When PR/MR is ready for human review ### Consider Requesting Review: - ⚠️ After significant refactoring - ⚠️ When implementing complex algorithms - ⚠️ After fixing critical bugs - ⚠️ When uncertain about approach ### Don't Request Review: - ❌ Mid-task (wait until task complete) - ❌ Work in progress (unless seeking early feedback) - ❌ Trivial changes (typos, formatting) - ❌ Before self-review complete ## Review Request Protocol ### Step 1: Complete Self-Review First **MANDATORY:** Use `code-review` skill before requesting external review ``` I'm completing self-review using the code-review skill before requesting external review. [Perform comprehensive self-review] Self-review complete ✅ - All tests pass - No obvious issues found - Code quality verified Now ready for external review. ``` ### Step 2: Identify Commit Range
Details
- Skill name
requesting-code-review- Repository
- Freddy-CHEN-ux/00_claude_skills
- Path
skills/requesting-code-review/SKILL.md- Repo updated
- 10 January 2026
FAQ
What does the Requesting Code Review skill do?
Use when completing tasks or major features. Know when and how to request reviews. Provides git commit range to code-reviewer agent.
How do I install the Requesting 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 Requesting 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.
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
Receiving Code Review
8Freddy-CHEN-ux/00_claude_skills
Use when processing code review feedback. Technical evaluation of feedback, verify before implementing. No performative agreement or gratitude.
Sharing Skills
8Freddy-CHEN-ux/00_claude_skills
Use when contributing skills back to the community. Follow git workflow: sync upstream → create branch → develop skill → test with writing-skills → commit → push → PR. One skill per PR.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.