requesting-code-review

Dispatch a code-reviewer subagent to analyze changes against requirements.

Updated Nov 3, 2025

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

Ready to run

npx skills add https://github.com/ayourtch/kimichat --skill requesting-code-review-ayourtch

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures code quality and adherence to requirements by dispatching a dedicated code-reviewer subagent to scrutinize changes before they cascade into larger problems.

Core Features & Use Cases

Automated Code Review: Dispatches a code-reviewer subagent to analyze code changes against a plan or requirements.
Structured Feedback: Provides a template for the reviewer to categorize issues by severity (Critical, Important, Minor) and offer recommendations.
Quality Gate: Mandatory after each task in subagent-driven development, after major features, and before merging.
Use Case: After implementing a new verification function, use this skill to request a code review, providing the Git SHAs and a description of the changes for the subagent to analyze.

Quick Start

I'm using the requesting-code-review skill to review the changes for Task 3: Implement user roles.

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 code review before merging changes to main?▼

Code review ensures quality by dispatching a dedicated reviewer subagent to analyze your changes. Provide the base and head Git SHAs, describe what you implemented, and reference your plan or requirements. The subagent categorizes issues by severity and offers recommendations before merge.

What should I include when requesting a code review?▼

Include the base and head Git commit SHAs, a description of what was implemented, and your original plan or requirements. This gives the code-reviewer subagent the context needed to assess whether changes align with intent and catch issues early.

When should I use code review in my development workflow?▼

Request code review after completing each task in subagent-driven development, after implementing major features, before merging to main, when stuck, before refactoring, or after fixing complex bugs. It acts as a quality gate to prevent issues from cascading.

How does the code review feedback get organized?▼

The code-reviewer subagent structures feedback by severity level—Critical, Important, and Minor—with specific recommendations for each. This prioritization lets you address the most impactful issues first and act on feedback systematically.

Can I use code review for work outside of Git-based workflows?▼

This skill requires Git SHAs to identify changes between commits. If your workflow doesn't use Git or version control that provides commit identifiers, you'll need to adapt the input format or use an alternative approach for capturing code deltas.

What's the difference between code review and automated testing?▼

Code review focuses on adherence to requirements, design patterns, and potential logic issues through human reasoning via a subagent. Automated testing catches bugs through execution. Both are complementary—review catches design problems early; tests verify correctness at runtime.