skills.rest
RedWoodOG
RedWoodOGCOMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Dispatch a reviewer subagent to perform checklist-driven code reviews.

174|23|Updated Apr 3, 2026
Search Tags:#automation#feedback#subagent#quality-assurance#code-review#development-workflow#review-process
One-click install
npx skills add https://github.com/RedWoodOG/Hermes-Desktop --skill requesting-code-review-redwoodog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/RedWoodOG/Hermes-Desktop/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/RedWoodOG/Hermes-Desktop --skill requesting-code-review-redwoodog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic code reviews prevent defects from slipping through by ensuring changes are inspected before they merge.

Core Features & Use Cases

  • Dispatch a reviewer subagent to evaluate implementation for correctness and quality.
  • Provide a structured feedback loop with a checklist and clear outputs.
  • Use cases include post-task reviews in subagent-driven development, pre-merge checks, and reviews after major refactors.

Quick Start

Dispatch a reviewer subagent after completing a task or feature to validate requirements before merging.

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 reviews for feature implementations and bug fixes?▼

You can automate code reviews by dispatching a reviewer subagent to evaluate completed changes. This provides a structured feedback loop using a predefined checklist to validate correctness and quality before merging.

What is the best way to structure pre-merge code review feedback?▼

Structured code review feedback is generated by guiding a reviewer subagent with a predefined checklist and clear output format. This ensures traceable acceptance criteria and consistent evaluation across multi-repo projects.

When do I need a checklist-driven review process in a development workflow?▼

You need a checklist-driven review process when performing post-task reviews in subagent-driven development or after major refactors. It ensures systematic inspection of changes to prevent defects from slipping through before merges.

Can I use a subagent to review code across multi-repo projects?▼

Yes, you can dispatch a reviewer subagent to perform code reviews across multi-repo projects. It applies to development workflows involving feature implementations and bug fixes, providing clear feedback and traceable acceptance criteria.

How does a reviewer subagent evaluate code quality and correctness?▼

A reviewer subagent evaluates code quality by applying a predefined checklist to the completed changes. It assesses correctness and quality, generating structured feedback and traceable acceptance criteria for the development workflow.

What are the limitations of automating code reviews with a subagent?▼

Automating code reviews with a subagent focuses on checklist-driven validation and structured feedback, but it requires completed changes to evaluate. It serves as a pre-merge check rather than a continuous monitoring solution.

Related Skills

Explore More Software Engineering Skills→
greglambgreglamb
1

requesting-code-review

Dispatch a code-reviewer subagent to identify defects and readiness issues in completed code changes.

Community
Intermediate
ylxmf2005ylxmf2005
11

acceptance-review-lead

Review delivery evidence against acceptance criteria and issue a verdict.

Community
Advanced
brabos-aibrabos-ai
8

add-subagent-driven-development

Dispatch independent subagents for iterative development tasks with enforced code reviews.

Official
Advanced
az9713az9713

code-review

Automate structured code review quality assurance for pull requests.

Community
Advanced