requesting-code-review

Initiate code reviews by comparing SHA hashes from previous and current commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you to efficiently request and manage code reviews, ensuring that issues are caught early in the development process.

Core Features & Use Cases

  • Task-based Code Reviews: Automatically request reviews after each task in subagent-driven development.
  • Major Feature Reviews: Conduct code reviews for major features and before merging.
  • Optional Reviews: Request reviews when stuck, before refactoring, or after fixing complex bugs.
  • Feedback Handling: Offers structured feedback and assessment for issues identified by the reviewer.

Quick Start

After completing your task, run the following command to dispatch a code reviewer subagent: use 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 review requests after completing a development task?

To automate code review requests, run the `use code-reviewer.md` command after completing your task to dispatch a reviewer subagent, ensuring issues are caught early before integration.

When should I request a code review during the git integration process?

You should request a code review during the final stages of code integration, specifically for major features, before merging, or optionally when stuck, refactoring, or fixing complex bugs.

How does initiating a code review process handle commit history?

Initiating a code review requires comparing SHA hashes from the previous commit and the current commit to evaluate code quality and compliance with development standards.

What is the best way to handle structured feedback for issues identified by a code reviewer?

The best way to handle structured feedback is to use a task-based code review process that offers assessment and feedback handling for issues identified by the reviewer subagent.

Can I use this code review process for subagent-driven development workflows?

Yes, this code review process is designed for subagent-driven development, automatically requesting task-based reviews to ensure code quality and compliance throughout the workflow.