skills.rest
lagz0ne
lagz0neCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Automate code review for subagent-driven development tasks.

2|1|Updated Jan 5, 2026
Search Tags:#merge#subagent#quality-assurance#code-review#task-driven
One-click install
npx skills add https://github.com/lagz0ne/prev-cli --skill requesting-code-review-lagz0ne
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/lagz0ne/prev-cli/tree/main/.opencode/skill/requesting-code-review
Command: npx skills add https://github.com/lagz0ne/prev-cli --skill requesting-code-review-lagz0ne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the code review step in subagent-driven development to catch issues early and ensure quality before merging.

Core Features & Use Cases

  • Code review orchestration: Utilizes a standardized template to evaluate what was implemented, the plan, and base/head changes.
  • Pre-merge quality gate: Identifies critical, important, and minor issues before integration.
  • Workflow integration: Fits into task-based, ad-hoc development, and batch-review workflows.

Quick Start

After you finish a development task, run the requesting-code-review skill to trigger a review and prepare feedback for the reviewer.

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 for subagent-driven development before merging to main?▼

Automating code review for subagent-driven development involves evaluating implemented changes against the original plan, classifying issues by severity, and logging actionable feedback before merging to main to catch integration issues early.

What is a pre-merge quality gate and when should I run a code review?▼

A pre-merge quality gate identifies critical, important, and minor issues before merging to main. You should run a code review after each completed task, after major features, and before merging to main to surface issues early.

How do I trigger a code review after finishing a development task?▼

To trigger a code review after finishing a development task, run the review skill to evaluate what was implemented, compare the plan against base and head changes, and prepare structured feedback for the reviewer.

Does this code review workflow support batch reviews and ad-hoc task-based development?▼

Yes, this code review workflow supports task-based development, ad-hoc reviews, and batch-review workflows, fitting into various development processes to evaluate changes and prepare feedback for the reviewer.

What's the best way to classify code review issues by severity before integration?▼

The best way to classify code review issues by severity before integration is to use a standardized template that evaluates implemented changes against the plan, categorizing issues into critical, important, and minor levels to log actionable feedback.

Related Skills

Explore More Software Engineering Skills→
WesleyMFrederickWesleyMFrederick

requesting-code-review

Dispatch a code-reviewer subagent to review Git changes between BASE_SHA and HEAD_SHA.

Community
Basic
miguelarcjrmiguelarcjr

requesting-code-review

Dispatch a code-review subagent to evaluate completed work against requirements.

Community
Intermediate
mortenbroesbymortenbroesby
1

requesting-code-review

Dispatch a code-reviewer subagent to evaluate code quality, architecture, testing, and production readiness.

Community
Intermediate
shawnpangshawnpang
285

security-review

Identify vulnerabilities across code, infrastructure, and workflows with risk classification.

Community
Advanced