requesting-code-review

Review code changes with structured checklists before merging.

2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/anortham/razorback --skill requesting-code-review-anortham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/anortham/razorback/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/anortham/razorback --skill requesting-code-review-anortham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are essential but often inconsistent and time-consuming, leading to undetected defects and misaligned expectations. This Skill provides a structured, Julie-first review process that standardizes both inline and pre-merge reviews to ensure consistency and production readiness.

Core Features & Use Cases

  • Inline Review (Plan Execution): Lead performs inline reviews after each implementer reports DONE, ensuring spec compliance and quality.
  • Standalone Review (Ad-hoc / Pre-Merge): Dispatch a dedicated code-reviewer agent to validate complex changes before merging.
  • Tools and workflow integration: Uses get_symbols, deep_dive, and fast_refs to analyze changes and ensure safe, maintainable updates.
  • Use Case: Teams shipping features with multiple contributors can prevent regressions by enforcing the review loop before merge.

Quick Start

Orient your workflow by invoking the lead to perform inline reviews after each implementer reports DONE and run a standalone review before merging to main.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize code reviews for production readiness across multiple AI coding agents?

Standardize code reviews by applying a structured, Julie-first review process that enforces consistency and production readiness across Claude Code, Cursor, Codex, OpenCode, Copilot CLI, and Gemini CLI. It uses tools like get_symbols and fast_refs to analyze changes.

What is the best way to run an inline code review during plan execution?

Run an inline code review by having the lead perform a review immediately after each implementer reports DONE. This ensures spec compliance and quality during plan execution before proceeding to the next implementation phase.

Can I use this code review process to validate complex changes before merging?

Yes, you can dispatch a dedicated code-reviewer agent to perform a standalone review. This validates complex changes and checks for production readiness, architecture, testing, and risk mitigation before merging to main.

How does the Julie-first investigation workflow analyze code changes?

The Julie-first investigation workflow analyzes code changes by utilizing tools like get_symbols, deep_dive, and fast_refs. These tools examine modifications to ensure safe, maintainable updates and mitigate regression risks.

Does this code review skill work with Claude Code and Cursor CLI environments?

Yes, the code review skill works with Claude Code, Cursor, Codex, OpenCode, Copilot CLI, and Gemini CLI. It integrates into these environments to provide a structured reviewer checklist for production readiness.

When do I need a standalone pre-merge code review instead of an inline review?

You need a standalone pre-merge code review when validating complex changes before merging to main, preventing regressions in teams with multiple contributors. Inline reviews are used during plan execution after each implementer finishes.