requesting-code-review

Dispatch a code-review subagent to inspect recent changes before merging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams catch issues early by dispatching a code-review subagent before tasks are merged, preventing defects from propagating.

Core Features & Use Cases

  • Auto-dispatch of the code-reviewer subagent for every task in subagent-driven development.
  • Provides early feedback on code quality, architecture, testing, and readiness for merge.
  • Ideal for major feature delivery and before merging to main to ensure compliance with requirements.

Quick Start

Invoke the requesting-code-review skill after completing a task to trigger the code-reviewer subagent.

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 pre-merge code reviews for feature branches?

Automating pre-merge code reviews involves dispatching a code-review subagent to inspect recent changes. It validates alignment with the plan, assesses code quality and testing, and documents feedback for remediation before merging to main.

What is a subagent-driven development workflow for code quality assurance?

Subagent-driven code quality assurance auto-dispatches a code-review subagent for every completed task. It provides early feedback on code quality, architecture, and testing to prevent defects from propagating during feature delivery.

When should I trigger an automated code review during task-based workflows?

Trigger automated code reviews immediately after completing a task and before merging to main. This timing ensures issues are caught early and validates readiness for merge across task-based, feature-driven workflows.

Can I use an automated code-review subagent for major feature delivery?

Yes, you can use an automated code-review subagent for major feature delivery. It ensures compliance with requirements by providing early feedback on architecture, testing, and code quality before merging to main.

What is the best way to catch defects early before merging code?

The best way to catch defects early is dispatching a code-review subagent to inspect recent changes before merging. This validates alignment with the plan and documents feedback for remediation to prevent defects from propagating.