requesting-code-review

Name: requesting-code-review
Availability: InStock
Author: charly3pins

Dispatch a code-reviewer subagent to compare changes against the plan and assess production readiness.

4|Updated Dec 7, 2020

Search Tags:#git #quality assurance #code review #feedback #collaboration #development workflow #pull request #subagent

Ready to run

npx skills add https://github.com/charly3pins/dotfiles --skill requesting-code-review-charly3pins

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/charly3pins/dotfiles/tree/main/.config/opencode/skills/requesting-code-review
Command: npx skills add https://github.com/charly3pins/dotfiles --skill requesting-code-review-charly3pins

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Delaying code reviews allows issues to compound, leading to more complex and costly fixes later in the development cycle, increasing rework and project risk.

Core Features & Use Cases

Early & Frequent Review: Mandates requesting review after each task in subagent-driven development, major features, or before merging.
Code-Reviewer Subagent Dispatch: Automates the review process by dispatching a specialized subagent with a structured template.
Actionable Feedback: Guides acting on feedback, categorizing issues by severity, and pushing back with technical reasoning if needed.
Use Case: After completing a development task, use this skill to automatically dispatch a code-reviewer subagent, ensuring early detection of issues and maintaining high code quality before proceeding.

Quick Start

I have completed a development task. Request a code review for my recent changes.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema

How do I catch code issues before merging to main?▼

Request code review after completing development tasks to detect issues early. This Skill dispatches a specialized code-reviewer subagent using a structured template, comparing your changes against the plan to produce a production-readiness assessment before merge.

When should I request a code review in my development workflow?▼

Request code review after each subagent task, upon completing major features, before merging to main, when stuck on a problem, before refactoring, or after fixing complex bugs. Early and frequent review prevents issues from compounding into costly rework.

How does automated code review with a subagent work?▼

Code review is automated by dispatching a code-reviewer subagent with a structured template. The subagent analyzes your implemented changes, compares them against the original plan, categorizes issues by severity, and delivers actionable feedback on production readiness.

Can I push back on code review feedback?▼

Yes. This Skill guides you to act on feedback by severity, and supports pushing back with technical reasoning when appropriate. You retain final decision-making authority on which suggestions to apply.

What's the benefit of reviewing code before merging pull requests?▼

Early code review prevents cascading issues that compound during development. Catching problems before merge reduces rework, lowers project risk, maintains high code quality, and keeps your development cycle efficient.

Do I need to set up anything to request code review?▼

No dependencies or prerequisites are required. After completing a development task, invoke this Skill to automatically dispatch the code-reviewer subagent with a structured review template.