requesting-code-review

Request code reviews from a designated subagent within a git workflow.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/elysiaerica/ai_context_vault --skill requesting-code-review-elysiaerica
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/elysiaerica/ai_context_vault/tree/main/.codex/AGENT%20SKILLS/superpowers-main/skills/requesting-code-review
Command: npx skills add https://github.com/elysiaerica/ai_context_vault --skill requesting-code-review-elysiaerica

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires code-reviewer, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill facilitates the process of requesting and conducting code reviews, ensuring that code is of high quality and ready for integration.

Core Features & Use Cases

  • Task-Based Reviews: Request reviews after completing tasks or major features.
  • Early Feedback: Encourages early and frequent reviews to catch issues early.
  • Review Workflow: Integrates with git and subagent-driven development for streamlined code review process.
  • Use Case: Before merging your code into the main branch, use this Skill to request a code review, providing necessary context and instructions.

Quick Start

To request a code review, use the requesting-code-review Skill with the following template: Request code review for the 'Task X' commit range from {BASE_SHA} to {HEAD_SHA}.

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 a code review for a specific git commit range?

To request a code review, trigger the skill using the template: Request code review for the commit range from {BASE_SHA} to {HEAD_SHA}. This initiates the review process by passing git context and instructions to the designated subagent.

When should I request a code review in a task-based development workflow?

You should request a code review after completing specific tasks or major features, and before merging code into the main branch. Early and frequent reviews help catch issues early and ensure software quality and integration readiness.

Do I need a specific subagent to execute code review tasks?

Yes, executing code review tasks requires the designated 'code-reviewer' subagent. The skill operates within a subagent-driven development workflow by providing this specific dependency with the necessary context and instructions to perform the review.

Can I integrate automated code reviews into my git development workflow?

Yes, this skill integrates automated code reviews directly into a git-based development workflow. It streamlines the review process by delegating task-based reviews to a subagent, ensuring code quality before integration.

What context should I provide for a subagent-driven code review?

You should provide the specific task name, the base and head commit SHAs, and any relevant instructions. This context allows the code-reviewer subagent to accurately assess software quality and readiness for the targeted changes.

Why use a subagent-driven approach for software quality checks?

Using a subagent-driven approach for software quality checks isolates the review process within a designated agent. This ensures structured, task-based feedback on your git commits before merging code into the main branch.