requesting-code-review

Coordinate a subagent to capture and route code-review feedback.

58|6|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/Matt-Aurora-Ventures/Jarvis --skill requesting-code-review-matt-aurora-ventures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Matt-Aurora-Ventures/Jarvis/tree/main/.windsurf/skills/requesting-code-review
Command: npx skills add https://github.com/Matt-Aurora-Ventures/Jarvis --skill requesting-code-review-matt-aurora-ventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and accelerates software code-review by routing feedback through a dedicated subagent, reducing miscommunication and rework.

Core Features & Use Cases

  • Structured review prompts that capture WHAT_WAS_IMPLEMENTED, PLAN_OR_REQUIREMENTS, BASE_SHA, HEAD_SHA, and DESCRIPTION for precise feedback.
  • Guidance on severity levels and actionability to speed up decision-making during task-driven development, major feature work, and pre-merge checks.
  • Templates and workflows that integrate with common git workflows to ensure reproducible reviews across teams.

Quick Start

Draft a code-review request by filling in the template with what was implemented, the plan, and the base/head SHAs, then dispatch the code-reviewer subagent.

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 feedback for git workflows?

Automate code review feedback by dispatching a subagent with a structured template capturing implementation details, plan requirements, and git diff SHAs to route structured feedback.

What is the best way to structure a pre-merge code review request?

The best way to structure a pre-merge code review is by providing what was implemented, the plan or requirements, base SHA, head SHA, and a description to guide the reviewer.

How does a subagent coordinate code review severity levels?

A subagent coordinates code review severity levels by applying structured guidance on severity and actionability to speed up decision-making during task-driven development cycles.

Can I use this code review workflow for major feature implementations?

You can use this code review workflow for major feature implementations, task-driven development cycles, and pre-merge reviews across software projects to ensure reproducible feedback.

Do I need specific git diff references to get precise code review feedback?

You need specific git diff references like BASE_SHA and HEAD_SHA to capture precise code changes and route accurate feedback through the dedicated reviewer subagent.

Why should I standardize code review templates across teams?

Standardize code review templates across teams to reduce miscommunication and rework by ensuring all reviews capture consistent implementation details, requirements, and diff references.