skills.rest
KYRIE66nb
KYRIE66nbCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

requesting-code-review

Route code changes to a code-review subagent for structured feedback.

Updated Apr 8, 2026
Search Tags:#workflow#subagent#quality-assurance#code-review#merge-request#review-feedback#dev-process
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill requesting-code-review-kyrie66nb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.codex/skills/requesting-code-review
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill requesting-code-review-kyrie66nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This task-oriented skill routes code changes to a dedicated code-review subagent to catch issues early and prevent cascading defects.

Core Features & Use Cases

  • Structured review prompts: generates a consistent code-review brief including what was implemented, plan, base and head SHAs, and a succinct description.
  • Task-aware reviews: used after completing a task in subagent-driven development or before merging major features to main.
  • Actionable feedback workflow: categorizes issues by severity and provides a path to resolution, reducing cycle time and improving quality.

Quick Start

Invoke the code-reviewer subagent after completing a task to generate and act on a formal 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 code review before a merge request?▼

Automate code review before a merge request by routing code changes to a dedicated subagent that generates a consistent review brief and provides actionable feedback categorized by issue severity.

What is a subagent-driven code review workflow?▼

A subagent-driven code review workflow routes completed task changes to a dedicated subagent to catch issues early, generating a formal brief with base and head SHAs, plan alignment, and a production-readiness assessment.

How do I structure feedback for a pre-merge code review?▼

Structure pre-merge code review feedback by categorizing issues into critical, important, and minor severities, while also documenting strengths, plan alignment, and a clear assessment of production readiness.

Can I use an automated code review for task-based development?▼

Yes, automated code review fits task-based development by invoking a code-reviewer subagent immediately after completing a task, ensuring issues are caught early before they cascade into larger defects.

When should I request a formal code review in the dev process?▼

Request a formal code review in the dev process after completing a task in subagent-driven development or before merging major features to main, ensuring early detection of cascading defects.

What is the best way to catch cascading defects during feature implementation?▼

The best way to catch cascading defects during feature implementation is routing changes to a code-review subagent that provides structured, severity-categorized feedback and a production-readiness assessment before merging.

Related Skills

Explore More Software Engineering Skills→
hetsheth-droidhetsheth-droid

requesting-code-review

Route git changes to a code-reviewer subagent for structured pre-merge reviews.

Community
Intermediate
mshaheerzmshaheerz
1

review-merge-readiness

Review git diffs against project plans and requirements for merge readiness.

Community
Intermediate
pascallammerspascallammers
1

requesting-code-review

Dispatch a code-reviewer subagent to verify implementations against project plans.

Community
Intermediate
tense-itense-i
1

requesting-code-review

Dispatch a code-reviewer subagent after each task before merging to main.

Community
Intermediate