requesting-code-review

Automate code review requests with base and head SHAs.

141|20|Updated Dec 19, 2025
One-click install
npx skills add https://github.com/julianromli/opencode-template --skill requesting-code-review-julianromli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/julianromli/opencode-template/tree/main/skill/requesting-code-review
Command: npx skills add https://github.com/julianromli/opencode-template --skill requesting-code-review-julianromli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and standardizes requesting code reviews to catch issues early and ensure alignment with project goals.

Core Features & Use Cases

  • Structured, repeatable review requests driven by subagents to improve feedback quality.
  • Guides reviewers through key inputs (base/head SHAs, implemented changes, and planned requirements) to speed up the process.
  • Applicable after each task in subagent-driven development, after completing major features, or before merging to main to uphold quality.

Quick Start

Provide a concise code-review request by summarizing what changed and the intended review plan.

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 in a subagent workflow?▼

You can automate code review requests by dispatching a subagent to capture base and head SHAs, evaluate implemented changes, and assess feedback against a defined plan to ensure quality and alignment.

When should I request a code review in an automated git workflow?▼

You should request a code review after completing each task in subagent-driven development, finishing major features, or before merging to main. This ensures quality assurance checks catch issues early in the development cycle.

What inputs are needed for a structured code review subagent?▼

A structured code review subagent requires base and head SHAs, a summary of implemented changes, and the planned requirements. These inputs speed up the process and guide reviewers through the evaluation.

How do I standardize code review feedback against a development plan?▼

To standardize code review feedback against a plan, provide the reviewer with the intended requirements alongside the code changes. The subagent then evaluates the feedback to ensure alignment with project goals.

Does this code review automation work without external dependencies?▼

Yes, this code review automation works without external dependencies. It requires no additional components, relying entirely on the core subagent workflow to capture git SHAs and evaluate feedback.