requesting-code-review

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

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/tense-i/stock-market-simulator --skill requesting-code-review-tense-i
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/tense-i/stock-market-simulator/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/tense-i/stock-market-simulator --skill requesting-code-review-tense-i

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guidance helps teams ensure code quality and catch issues early by coordinating a dedicated code-review reviewer subagent after tasks and before merges.

Core Features & Use Cases

  • Automated kickoff: dispatches a code-reviewer subagent after each task to surface issues early.
  • Structured feedback: uses a standard template to organize what was implemented, plan, and impact.
  • Governance and compliance: enforces review steps before merging to main in subagent-driven workflows.

Quick Start

Invite the code-reviewer subagent after each task and complete the template with what was implemented.

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 for pull requests in a subagent workflow?

Automated code review dispatches a code-reviewer subagent after each task to catch issues early. It coordinates peer review by enforcing plan-to-implementation alignment and applying structured templates before merging to main.

What is a code-reviewer subagent and how does it assess pull requests?

A code-reviewer subagent is an automated reviewer dispatched to evaluate pull requests. It uses structured review templates to assess code quality, architecture, testing, and readiness, ensuring plan-to-implementation alignment before merges.

How do I enforce code reviews before merging to main?

To enforce code reviews before merging to main, dispatch a code-reviewer subagent after each task completion. This governance step applies structured templates to verify quality and readiness, preventing unreviewed code from reaching the main branch.

Does automated peer review work for subagent-driven development processes?

Automated peer review is designed specifically for subagent-driven development processes. It dispatches a reviewer subagent after each task, using structured templates to verify implementation alignment and code quality before merging.

What is the best way to structure code review feedback for quality assurance?

The best way to structure code review feedback is using a standard template that organizes what was implemented, the plan, and the impact. This ensures consistent quality assurance assessments across architecture, testing, and readiness.