requesting-code-review

Automate peer review of code changes with structured prompts for subagent-driven development.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/cill-i-am/task-tracker --skill requesting-code-review-cill-i-am
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/cill-i-am/task-tracker/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/cill-i-am/task-tracker --skill requesting-code-review-cill-i-am

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables rapid, validated peer review by dispatching a dedicated code-reviewer subagent with targeted context to ensure quality before progress.

Core Features & Use Cases

  • Dispatches a dedicated code-reviewer subagent to evaluate the latest changes.
  • Integrates with subagent-driven development workflows to catch issues early.
  • Provides an auditable, repeatable review process that can be reused across tasks.

Quick Start

Request a code review by dispatching the reviewer with the latest task context.

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 pull request merge?

Automated code review before a merge is handled by dispatching a dedicated code-reviewer subagent with structured context like WHAT_WAS_IMPLEMENTED, BASE_SHA, and HEAD_SHA to evaluate changes. This ensures rapid, validated peer review and catches issues early in subagent-driven development workflows.

What context do I need to provide for an automated code reviewer?

An automated code reviewer requires structured prompts containing WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION. Providing this targeted context guides the subagent to accurately evaluate task implementations, feature upgrades, and bug fixes.

Can I use subagent-driven development to verify task implementations?

Subagent-driven development verifies task implementations by dispatching a dedicated code-reviewer subagent to evaluate the latest changes. This provides an auditable, repeatable review process that can be reused across tasks to ensure quality before progress.

Does automated code review work for bug fixes and feature upgrades?

Automated code review works for bug fixes and feature upgrades by dispatching a reviewer subagent with targeted context. It evaluates the latest changes against provided requirements and SHAs to ensure validated peer review before merging.

What is the best way to streamline peer review in subagent workflows?

Streamlining peer review in subagent workflows is best achieved by automating the dispatch of a code-reviewer subagent. This approach provides an auditable, repeatable review process that validates task implementations and catches issues early before merging.