skills.rest
jr2804
jr2804COMMUNITY
Explore all skills by this author →
GitHub

requesting-code-review

Dispatch a code-reviewer subagent to review code changes and guide fixes.

Updated Dec 4, 2025
Search Tags:#workflow#subagent#quality-assurance#code-review#team-collaboration#pull-request
One-click install
npx skills add https://github.com/jr2804/prompts --skill requesting-code-review-jr2804
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/jr2804/prompts/tree/main/skills/development/requesting-code-review
Command: npx skills add https://github.com/jr2804/prompts --skill requesting-code-review-jr2804

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to systematically request code reviews to catch issues early before they cascade.

Core Features & Use Cases

  • Core principle: Review early, review often to catch issues before they cascade.
  • Trigger points: After each task in subagent-driven development, after completing major features, and before merging to main; optional use when stuck or before refactoring.
  • Structured workflow: Dispatches a code-reviewer subagent with predefined fields and ensures feedback leads to concrete fixes.

Quick Start

Use the code-review workflow to request a review after completing a task. Provide the change summary and the plan or requirements, then invoke the code-reviewer to obtain feedback and address issues before proceeding.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I request a code review after completing a task in subagent-driven development?▼

You can request a code review by dispatching the code-reviewer subagent with your change summary and plan. This standardizes the process and ensures feedback leads to concrete fixes.

When should I trigger a code review in my workflow?▼

Trigger code reviews after each subagent task, after major features, and before merging to main. You can also optionally request reviews when stuck or before refactoring.

What problem does systematic code review solve for team collaboration?▼

Systematic code review catches issues early before they cascade. By reviewing early and often, teams prevent problems from escalating throughout the development lifecycle.

What information do I need to provide to get useful code review feedback?▼

You need to provide a change summary and the plan or requirements. The code-reviewer subagent uses these predefined fields to deliver structured feedback for concrete fixes.

Can I use code review workflows before refactoring my codebase?▼

Yes, requesting a code review before refactoring is an optional trigger point. The code-reviewer subagent assesses your codebase and returns feedback to guide concrete fixes.

Related Skills

Explore More Software Engineering Skills→
miles990miles990

requesting-code-review

Dispatch a code-reviewer subagent to review changes before merging.

Community
Intermediate
alo-expalo-exp
6

requesting-code-review

Dispatch a code-reviewer subagent to evaluate recent work before merging.

Official
Intermediate
tobihagemanntobihagemann
399

finalize

Automate staging, testing, code simplification, AI review, and pull request generation.

Community
Advanced
cloudfieldczcloudfieldcz
7

requesting-code-review

Dispatch the cf-powers:code-reviewer subagent to review code changes and return structured feedback.

Official
Intermediate