requesting-code-review

Automate code-review requests comparing implemented changes against the plan.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/luxunxiansheng/skills2026 --skill requesting-code-review-luxunxiansheng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/luxunxiansheng/skills2026/tree/main/requesting-code-review
Command: npx skills add https://github.com/luxunxiansheng/skills2026 --skill requesting-code-review-luxunxiansheng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates and institutionalizes early issue detection by initiating formal code reviews after each task, after completing major features, and before merging to main to ensure work meets requirements and prevent cascading defects.

Core Features & Use Cases

  • Mandatory review triggers after each task, after major features, and before merge to main.
  • Structured review workflow including placeholders and templates for consistent feedback.
  • Ad-hoc guidance for when stuck or before refactoring to ensure baseline checks and quality.

Quick Start

Dispatch the code-reviewer subagent after completing a task to capture changes, compare them against the plan, and begin the formal review.

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 a git pull request merge?

To automate code review requests before a merge, dispatch a code-reviewer subagent with the required git SHAs to evaluate code quality, architecture, and testing readiness against the original plan.

What is a structured code review workflow for subagent-driven development?

A structured code review workflow dispatches a subagent after completing tasks or major features to capture git changes, compare them against the implementation plan, and enforce formal quality checks.

When should I trigger a mandatory code review during the development cycle?

Trigger mandatory code reviews after completing each task, finishing major features, and before merging to main to catch issues early and prevent cascading defects in the codebase.

Can I use this code review process for batch tasks and pre-merge gates?

Yes, the code review process applies to subagent-driven development cycles, batch tasks, and pre-merge gates by requiring git SHAs to evaluate readiness and guide actions based on the review outcome.

Does a formal code review evaluate architecture and testing readiness?

Yes, a formal code review evaluates code quality, architecture, testing, and overall readiness by comparing implemented changes against the structured plan to guide subsequent development actions.

What is the best way to ensure work meets requirements before a git merge?

The best way to ensure work meets requirements is initiating formal code reviews before merging to main, using a structured workflow with templates to compare changes against the plan and prevent defects.