requesting-code-review

Dispatch a dedicated reviewer to plan code reviews with structured feedback templates.

Updated Feb 11, 2016
One-click install
npx skills add https://github.com/Ehrax/dotfiles --skill requesting-code-review-ehrax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Ehrax/dotfiles/tree/main/configs/agents/skills/requesting-code-review
Command: npx skills add https://github.com/Ehrax/dotfiles --skill requesting-code-review-ehrax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, turn-key process to ensure code quality by triggering formal reviews at key milestones, preventing defects from propagating into production.

Core Features & Use Cases

  • Mandatory review after each task in subagent-driven development to maintain quality.
  • Templates and guidelines for reviewers to provide actionable feedback.
  • Works across feature implementation, bug fixes, and pre-merge validation to reduce risk before merging.

Quick Start

Request a code review by dispatching the code-reviewer subagent and filling the template at code-reviewer.md.

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 reviews for subagent-driven development tasks?

Automate code reviews for subagent-driven tasks by dispatching a dedicated reviewer subagent using a structured template. This enforces mandatory quality checks after each task completion, ensuring traceability with base and head SHAs.

What is the best way to structure feedback during a pull request review?

Structure pull request review feedback using a predefined template that requires clear context and actionable guidelines. This ensures reviewers provide targeted, traceable validation before merging codebases into production.

Does this code review workflow require specific git commit SHAs?

Yes, this code review workflow requires the use of base and head git commit SHAs. This provides strict traceability and ensures the reviewer validates the exact code changes made between the two references.

Can I use automated code review for pre-merge validation across different codebases?

Yes, you can use this automated code review for pre-merge validation across feature implementations and bug fixes in various codebases. It triggers formal reviews at key milestones to prevent defects from reaching production.

When are code reviews mandatory in this quality assurance workflow?

Code reviews are mandatory after each individual task and after major feature implementations within this workflow. Optional checks are also available for additional quality assurance during subagent-driven development.