requesting-code-review

Dispatch focused code reviews comparing Git commits against explicit requirements.

15|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/mahoushoujyo-eee/eshell --skill requesting-code-review-mahoushoujyo-eee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/mahoushoujyo-eee/eshell/tree/main/.codex/skills/requesting-code-review
Command: npx skills add https://github.com/mahoushoujyo-eee/eshell --skill requesting-code-review-mahoushoujyo-eee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers catch bugs, architectural problems, missing requirements, and production-readiness issues before changes are merged or become harder to fix.

Core Features & Use Cases

  • Focused Reviewer Dispatch: Provides a structured prompt for sending implementation context to a code reviewer subagent without exposing the current session history.
  • Git-Based Comparison: Uses base and head commit SHAs to review the precise range of completed changes.
  • Actionable Feedback: Organizes findings into Critical, Important, and Minor issues with file references, impact explanations, and suggested fixes.
  • Use Case: After implementing a major feature, use this Skill to dispatch a reviewer, evaluate the resulting feedback, and resolve important issues before merging.

Quick Start

Use the requesting-code-review skill to review the changes between the previous commit and the current commit against the feature requirements.

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 using git diff before merging a major feature?▼

To request a code review, you provide the base and head Git commit SHAs, a concise implementation summary, and explicit requirements to dispatch a focused reviewer that evaluates the git diff for defects and requirement gaps.

What is severity-calibrated feedback in a pre-merge code review?▼

Severity-calibrated feedback organizes code review findings into Critical, Important, and Minor issues, providing file references, impact explanations, and suggested fixes to help developers prioritize pre-merge validation tasks.

Can I use a subagent to review code quality without exposing my session history?▼

Yes, this skill dispatches a focused reviewer subagent using a structured prompt that sends implementation context without exposing the current session history, ensuring an isolated and objective code review.

Does automated bug detection evaluate production readiness and security?▼

Yes, the code review evaluates production readiness and security alongside code quality, architecture, and testing, identifying implementation defects and requirement gaps before changes are merged.

When do I need to run a code review checkpoint during refactoring?▼

You need a refactoring checkpoint when completing major features, subagent-driven development, or pre-merge validation, using base and head commit SHAs to catch architectural problems before they cascade.