skills.rest
victorqnguyen
victorqnguyenCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Your requested JSON structure is invalid. Please review the developer's guide for formatting requirements. Alternatively, visit your local town office for a copy of the current edition of the guidelines.

Updated Aug 23, 2026
Search Tags:#git#workflow#subagent#quality-assurance#code-review#pull-request
One-click install
npx skills add https://github.com/victorqnguyen/victors-architecture --skill requesting-code-review-victorqnguyen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/victorqnguyen/victors-architecture/tree/main/packages/core/skills/requesting-code-review
Command: npx skills add https://github.com/victorqnguyen/victors-architecture --skill requesting-code-review-victorqnguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatching a reviewer subagent when completing tasks helps catch issues early, preventing defects from cascading and preserving momentum.

Core Features & Use Cases

  • Mandatory review triggers: automatically dispatch after each task in subagent-driven development to surface blockers early.
  • Structured review: provides a standardized template for evaluating code quality, architecture, and tests.
  • Pre-merge gate: ensures feedback is addressed before merging to main, reducing risk of regressions.

Quick Start

Dispatch the code-reviewer subagent after completing a task to obtain feedback before proceeding.

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 before merging a pull request?▼

Automate code review by dispatching a reviewer subagent before merging to main. This subagent evaluates code quality, architecture, and tests using a structured template, capturing base and head SHAs to generate an assessment with strengths and issues.

When should I run a code review in a subagent-driven development workflow?▼

Run a code review after completing each task in subagent-driven development, after finishing major features, and before merging to main. This structured review process acts as a quality gate to catch issues early and prevent defects from cascading.

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

The best way to catch code quality issues is dispatching a reviewer subagent after task completion. This enforces a structured review process by providing a standardized prompt template that evaluates architecture and tests, surfacing blockers early.

Does this code review subagent provide a structured assessment of my git changes?▼

Yes, the code review subagent provides a structured assessment by capturing the base and head SHAs of your git changes. It generates a detailed evaluation highlighting strengths and issues, ensuring feedback is addressed before merging.

Can I integrate a pre-merge quality gate into my git workflow?▼

Yes, you can integrate a pre-merge quality gate by dispatching a reviewer subagent before merging to main. This ensures all feedback from the structured code review is addressed, significantly reducing the risk of regressions.

Related Skills

Explore More Software Engineering Skills→
joshmandersjoshmanders
29

requesting-code-review

Dispatch a code-review subagent after tasks using base and head SHAs.

Community
Intermediate
jayhjenkinsjayhjenkins

requesting-code-review

Dispatch a code-reviewer subagent to validate code changes before merging.

Community
Basic
arcasilesgrouparcasilesgroup
54

ai-pr

Automate governed pull request workflows with pre-push gates and squash merge.

Official
Advanced
guma154-cmdguma154-cmd

coderabbit-review

Automate CodeRabbit CLI code reviews in WSL environments.

Community
Intermediate