requesting-code-review

Dispatch the code-reviewer subagent to initiate structured code-review workflows.

1|1|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/orbtyapp/orbty-eazy --skill requesting-code-review-orbtyapp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/orbtyapp/orbty-eazy/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/orbtyapp/orbty-eazy --skill requesting-code-review-orbtyapp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the initiation of a code-review workflow by dispatching the code-reviewer subagent to catch issues before they cascade.

Core Features & Use Cases

  • Automatic code-review dispatch after each task, after major features, and before merges.
  • Enforces a structured feedback loop with a standardized review template.
  • Supports rapid feedback across development stages using orbty-eazy:code-reviewer.

Quick Start

Use the orbty-eazy:code-reviewer subagent by populating the required placeholders in the code-reviewer template and sending a review request after each task. Fill WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION. Then act on feedback as instructed.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I automate code review requests before merging a pull request?

Automating code review requests before merging involves dispatching a subagent after major features or before pulling to main. This skill triggers that workflow automatically to catch issues early and enable rapid feedback.

What is a structured code review template and how does it improve feedback?

A structured code review template enforces a standardized feedback loop by requiring specific fields like BASE_SHA, HEAD_SHA, and DESCRIPTION. This structure drives focused improvements by ensuring reviewers receive consistent context about what was implemented.

How do I integrate automated code review into a subagent-driven development workflow?

Integrating automated code review into subagent-driven development requires dispatching a review after each completed task. This skill automates that dispatch process, applying reviews at key development stages to enable rapid feedback.

When do I need to trigger an automated code review during development?

You need to trigger an automated code review after each task in subagent-driven development, after completing major features, and before merging to main. This timing catches issues before they cascade into larger problems.

What information do I need to provide for a subagent code review request?

For a subagent code review request, you must populate a structured template with WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION fields to drive focused improvements and provide necessary context.