requesting-code-review

Dispatch a code-review subagent to categorize issues by severity before merging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline pre-merge quality checks by dispatching a code-review subagent to catch issues early and ensure changes meet standards.

Core Features & Use Cases

  • Automated orchestration: Dispatch the code-review subagent to evaluate changes before merging.
  • Structured feedback: categorize issues by severity (Critical, Important, Minor) and present actionable guidance.
  • Workflow integration: supports task-driven development, major feature reviews, and merge readiness checks.

Quick Start

Dispatch the code-reviewer subagent for your current task context to begin the 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 pre-merge code reviews for task-driven development?

Automate pre-merge code reviews by dispatching a code-review subagent to evaluate changes, which routes task-driven development updates to surface issues early before merging.

What is the best way to structure code review feedback by severity?

Structure code review feedback by categorizing identified issues into Critical, Important, and Minor severity levels, presenting actionable guidance to resolve problems early.

How does a code-review subagent integrate with plan-driven workflows?

A code-review subagent integrates with plan-driven workflows by dispatching automated quality checks during feature completion and merge preparation to ensure changes meet standards.

When do I need an automated subagent for merge readiness checks?

You need an automated subagent for merge readiness checks when completing major features, ensuring pre-merge quality assurance catches issues early and changes meet required standards.

Can I use an automated subagent to catch early code issues without manual review?

Yes, you can dispatch an automated subagent to evaluate changes and catch early code issues without manual review, providing structured feedback for merge preparation.

What are the limitations of using subagents for pre-merge quality assurance?

Using subagents for pre-merge quality assurance relies on routing changes for automated evaluation, which surfaces issues early but requires integration with task-driven development workflows to function effectively.