requesting-code-review

Dispatch a code-reviewer subagent with Git SHAs and implementation details.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skipping code reviews or performing them late in the development cycle can lead to cascading issues and costly rework. This skill streamlines the process of requesting timely, structured code reviews.

Core Features & Use Cases

  • Timely Review Triggers: Mandates requesting reviews after each task, major feature, or before merging, catching issues before they compound.
  • Automated Review Dispatch: Dispatches a dedicated code-reviewer subagent with relevant Git SHAs, implementation details, and plan references.
  • Actionable Feedback Loop: Guides on how to act on feedback, prioritizing critical and important issues for immediate resolution.

Quick Start

Use the requesting-code-review skill to get a review for the 'user-profile-validation' feature, comparing it against 'Task 3' of the plan.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I catch code issues before merging to main?

Code review catches defects early by having a dedicated reviewer examine changes before merge. This skill automates requesting structured reviews by dispatching a code-reviewer agent with Git SHAs and implementation details, preventing issues from cascading into production.

When should I request a code review in my development workflow?

Request code review after completing each task, after major features, before merging to main, when stuck, before refactoring, or after fixing complex bugs. Timely reviews ensure issues are caught while context is fresh and rework costs remain low.

What information do I need to provide for an automated code review?

Provide BASE_SHA and HEAD_SHA from Git, a description of what was implemented, the plan or requirements being addressed, and the HEAD_SHA reference. The skill uses this data to dispatch the code-reviewer agent with full context for thorough analysis.

How do I act on code review feedback?

The skill guides prioritizing feedback by severity: address critical and important issues immediately, then resolve minor suggestions. This structured approach ensures high-impact problems are fixed first, reducing rework cycles.

Can code review automation work with Git-based development?

Yes. This skill is designed for Git workflows, extracting commit SHAs and comparing branches to identify changes. It integrates into subagent-driven development cycles where reviews trigger automatically after tasks or before merge.