requesting-code-review

Automate structured code review via a reviewer subagent with delegate_task.

3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/ever-oli/io --skill requesting-code-review-ever-oli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/ever-oli/io/tree/main/skills/software-development/requesting-code-review
Command: npx skills add https://github.com/ever-oli/io --skill requesting-code-review-ever-oli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatch a reviewer subagent to catch issues before they cascade. Review early, review often.

Core Features & Use Cases

  • Standardized Review Checklist: Enforces a comprehensive, repeatable set of quality checks before merge.
  • Contextual Feedback Loop: Captures file changes, rationale, and tests to guide improvements efficiently.
  • Workflow Integration: Seamlessly integrates with delegate_task to assign reviewers and collect verdicts.

Quick Start

Dispatch a reviewer subagent to evaluate your recent changes using the built-in delegate_task tool.

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 a pre-merge code review using a subagent?

Automate post-bug-fix audits by dispatching a reviewer subagent to evaluate changes against a standardized checklist. The subagent propagates context and returns structured feedback with a verdict on critical, important, and minor issues.

How does a reviewer subagent enforce commit standards during a code review?

A reviewer subagent enforces commit standards by applying a standardized review checklist to your code changes. It evaluates the changes and generates structured feedback categorizing issues by severity before providing a final verdict.

Can I use delegate_task to assign code reviews and collect feedback?

Yes, you can integrate delegate_task to assign reviewer subagents and collect their verdicts. This workflow integration captures file changes, rationale, and tests to guide improvements efficiently through a contextual feedback loop.

What is the best way to structure feedback for a post-implementation review?

The best way to structure feedback for a post-implementation review is by categorizing issues into critical, important, and minor levels. This structured evaluation method ensures repeatable quality assurance checks and delivers a clear final verdict.

Does automated code review work without external dependencies?

Yes, automated code review works without external dependencies. The process relies entirely on internal subagent dispatch and context propagation to evaluate changes and enforce quality assurance standards.