When is a code review considered mandatory?

Reviews are mandatory after completing each task in subagent-driven development, after implementing major features, and immediately before merging to the main branch.

How should I handle feedback from the code-reviewer subagent?

Fix Critical and Important issues immediately before proceeding. Minor issues can be noted for later, and you can push back with technical reasoning if you believe the reviewer is incorrect.

How does this skill identify which code to review?

It utilizes Git SHAs to define a range between a starting commit (BASE_SHA) and an ending commit (HEAD_SHA), allowing the subagent to focus precisely on recent changes.

What is the core principle of this skill?

The core principle is 'Review early, review often,' designed to catch technical issues before they cascade into more complex problems later in the development cycle.

Automated Code Review

Name: Automated Code Review
Author: orbtyapp

byorbtyapp

Collaboration Tools

Dispatches specialized subagents to perform comprehensive code reviews and identify technical issues before they reach production.

About

The Requesting Code Review skill automates the peer-review process within Claude Code by leveraging the orbty-eazy:code-reviewer subagent. It allows developers to define specific git commit ranges (BASE_SHA to HEAD_SHA) and provides a structured framework for auditing implementation against original requirements. By categorizing feedback into Critical, Important, and Minor tiers, it ensures that high-priority bugs are addressed immediately while maintaining a clear audit trail for subagent-driven development workflows.

Key Features

Integration with subagent-driven development and planning workflows
0 GitHub stars
Git-based diff analysis using specific commit SHAs
Categorized feedback loop for Critical and Important issues
Automated subagent dispatch for technical code audits
Template-driven review process for consistent reporting

Use Cases

Performing a final technical audit before merging feature branches to main
Getting an automated second opinion when stuck on complex refactoring tasks
Verifying individual task completion in subagent-driven development

About

Key Features

Integration with subagent-driven development and planning workflows
0 GitHub stars
Git-based diff analysis using specific commit SHAs
Categorized feedback loop for Critical and Important issues
Automated subagent dispatch for technical code audits
Template-driven review process for consistent reporting

Use Cases

Performing a final technical audit before merging feature branches to main
Getting an automated second opinion when stuck on complex refactoring tasks
Verifying individual task completion in subagent-driven development