requesting-code-review

Automate formal code review requests with Git range context and structured prompts.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill requesting-code-review-leonardoteodoroo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/leonardoteodoroo/amino-advanced/tree/main/.agent/skills/requesting-code-review
Command: npx skills add https://github.com/leonardoteodoroo/amino-advanced --skill requesting-code-review-leonardoteodoroo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating code reviews is often manual, causing delays, missing context, and inconsistent feedback across tasks and major features. This Skill standardizes when and how to request reviews, captures essential context, and aligns reviewers with explicit expectations.

Core Features & Use Cases

  • Structured request templates that include what was implemented, the plan or requirements, and branch references.
  • Contextual prompts with BASE_SHA and HEAD_SHA to reproduce changes and assess impact.
  • Works with subagent-driven development, ad-hoc development, and pre-merge review scenarios to maintain quality before integration.

Quick Start

Provide the latest changes and trigger the code-reviewer subagent to generate a structured review using the template.

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 requests for pull requests?

Provide the BASE_SHA and HEAD_SHA Git range, an implementation description, and a plan reference. The skill requires this exact structured context to trigger the code-reviewer subagent and generate a standardized review prompt for your pull request.

What context do I need to provide for a structured code review?

You need a structured Git range context with BASE_SHA and HEAD_SHA, a concise implementation description, and a plan or requirements reference. This context aligns reviewers with expectations and allows them to reproduce changes accurately.

Can I use this code review workflow with ad-hoc development?

Yes, the skill applies to ad-hoc development, subagent-driven workflows, and pre-merge scenarios. It standardizes review requests across all development types to maintain quality assurance before code integration.

When should I trigger a formal code review in a subagent workflow?

Trigger a formal code review upon completing tasks or major feature work before merging. The skill ensures timely feedback by applying structured review prompts across subagent-driven development cycles.

Why do my code review requests lack context for reviewers?

Requests lack context when missing the structured Git range, implementation description, or plan reference. The skill solves this by enforcing a standardized template that captures essential context and aligns reviewer expectations.