requesting-code-review

Creates feature branches and submits PRs to trigger code-review templates for designated approvers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes how to request code reviews to catch issues before they cascade.

Core Features & Use Cases

  • Structured review workflow: create a feature branch, submit a PR to development, and dispatch a review to the Archiect / Lead Developer subagent.
  • Template guidance: provides a clear code-review template with placeholders for WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, PR ID, and DESCRIPTION.
  • Broad applicability: useful after completing tasks, delivering major features, or before merging to development.

Quick Start

Create a feature branch for your change, push it to the repository, then open a PR to the development branch. Dispatch Archiect / Lead Developer subagent or User for review using the code-reviewer.md template and fill in the placeholders.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I request a code review for a pull request?

Standardize code review requests by creating a feature branch, opening a pull request to the development branch, and dispatching a code-review template to the Lead Developer subagent to catch issues before they cascade.

When should I initiate a structured code review in my workflow?

Initiate a structured code review after completing a task, delivering a major feature, or performing pre-merge checks to ensure code quality is evaluated and issues are caught before changes cascade into the development branch.

What is included in a standard code review template?

A standard code review template includes placeholders for what was implemented, the plan or requirements, the pull request ID, and a description to provide the Lead Developer subagent with necessary evaluation context.

Does this code review workflow require a specific branching strategy?

Yes, this code review workflow requires creating a feature branch and submitting a pull request specifically to the development branch to isolate changes for structured evaluation before integration.

How do I dispatch a code review to the Lead Developer subagent?

Dispatch a code review to the Lead Developer subagent by invoking the code-reviewer template and filling in the required placeholders with your implementation details, requirements, pull request ID, and description for evaluation.

What is the best way to catch code quality issues before they cascade?

The best way to catch code quality issues is to standardize review requests using a structured template that ensures a Lead Developer evaluates the pull request against requirements before merging to the development branch.