Review Process
Step-by-step workflow for conducting thorough code reviews
Install
npx skills add 0xranx/agentbrief --skill review-processgit clone --depth 1 https://github.com/0xranx/agentbrief.git /tmp/agentbrief
mkdir -p ~/.claude/skills
cp -r /tmp/agentbrief/briefs/code-reviewer/skills/review-process ~/.claude/skills/review-processPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Code Review Process ## Step-by-Step Review Workflow ### 1. Understand Context - Read the PR description and linked issues - Understand what problem is being solved and why - Check if the approach was discussed beforehand (design doc, RFC, issue thread) ### 2. High-Level Pass - Look at the file list -- does the scope make sense for the stated goal? - Check for unrelated changes mixed in (should be separate PRs) - Review the overall architecture: does the approach fit the codebase patterns? ### 3. Detailed Review - Walk through the code in logical order (not file order) - Start from the entry point and follow the data flow - For each change, evaluate against the review dimensions (correctness, architecture, naming, tests, errors, security) - Note findings with severity, location, issue, and suggestion ### 4. Test Review - Are the right things being tested? - Do tests cover both happy path and error paths? - Are tests testing behavior (what), not implementation (how)? - Would the tests catch a regression if someone changed the implementation? ### 5. Synthesize Feedback - Group findings by severity - Lead with critical issues - Provide an overall summary: approve, request changes, or comment - If requesting changes, be clear about what is blocking vs. what is optional ### 6. Follow-Up - Re-review addressed feedback promptly - Verify fixes actually resolve the issue (not just superficially)
Details
- Skill name
review-process- Repository
- 0xranx/agentbrief
- Path
briefs/code-reviewer/skills/review-process/SKILL.md- License
- MIT
- Repo updated
- 28 March 2026
FAQ
What does the Review Process skill do?
Step-by-step workflow for conducting thorough code reviews
How do I install the Review Process skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add 0xranx/agentbrief --skill review-process. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Review Process popular?
It lives in 0xranx/agentbrief, which has 43 GitHub stars and 0 forks.
Related skills
Typescript Advanced Types
430xranx/agentbrief
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
Analytics Setup
430xranx/agentbrief
When the user needs to set up product analytics, event tracking, or says 'set up analytics,' 'add tracking,' 'GA4,' 'Mixpanel,' 'PostHog,' 'Amplitude,' 'what events should we track,' 'conversion tracking,' 'funnel tracking,' or is launching a product and needs to instrument it for data collection.
API Documentation
430xranx/agentbrief
Create comprehensive API documentation for developers. Use when documenting REST APIs, GraphQL schemas, or SDK methods. Handles OpenAPI/Swagger, interactive docs, examples, and API reference guides.
Todo Discipline
48frankxai/claude-skills-library
Use when starting any complex task (3+ steps) or before declaring work complete. Enforces todo/task state to match reality — merge updates + read verification. Prevents false completion.
Release Notes
430xranx/agentbrief
When the user needs to write release notes, changelogs, or document what changed in a release. Use when the user says 'write release notes,' 'changelog,' 'what changed,' 'document this release,' 'update the README after launch,' or after completing a significant feature or version bump.
Tool Advisor
12dragon1086/claude-skills
Discovers your full tool environment and amplifies prompts with capability awareness. Suggests optimal tool compositions as non-binding options. Use when the user asks "what tools should I use", "best approach for this task", "how should I tackle", or explicitly mentions tool-advisor / $tool-advisor / ta. Do NOT trigger for direct coding requests, explanations, or reviews without tool-selection intent.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.