requesting-code-review

Name: requesting-code-review
Availability: InStock
Author: dogekiki

Dispatch subagents to evaluate git diffs against project requirements.

1|Updated Jul 21, 2026

Search Tags:#git #quality assurance #code review #development workflow #subagent

Ready to run

npx skills add https://github.com/dogekiki/SP-test --skill requesting-code-review-dogekiki

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/dogekiki/SP-test/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/dogekiki/SP-test --skill requesting-code-review-dogekiki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents technical debt and bugs from cascading by enforcing a structured, subagent-driven code review process before merging or proceeding to the next development task.

Core Features & Use Cases

Standardized Review Workflow: Provides a consistent template for subagents to evaluate code against requirements, architecture, and quality standards.
Context-Aware Evaluation: Ensures reviewers focus on specific git ranges and requirements without being distracted by session history.
Use Case: After implementing a new feature, use this skill to dispatch a reviewer to verify that your code matches the deployment plan and adheres to best practices before you merge it into the main branch.

Quick Start

Request a code review by providing the description of your changes and the git commit range to the subagent using the provided template.

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 using git commit ranges?▼

Automated code review using git commit ranges works by dispatching subagents to evaluate git diffs between base and head commit SHAs against defined project requirements. This catches architectural flaws and bugs before code integration without needing manual inspection.

What is subagent-driven code review in a development workflow?▼

Subagent-driven code review is a process where subagents perform rigorous, context-specific evaluations of your git diffs. This enforces a standardized review workflow that checks code against architecture and quality standards before merging.

Do I need git access to compare commit SHAs for code quality assessments?▼

Yes, you need git access to compare base and head commit SHAs for code quality assessments. The subagent requires this precise git diff context to evaluate your changes accurately without being distracted by session history.

How to catch architectural flaws and plan deviations before merging code?▼

To catch architectural flaws and plan deviations before merging code, dispatch a reviewer subagent using a structured template. The subagent evaluates your git diff against your deployment plan to verify adherence to best practices.

Can I use automated code review to prevent technical debt from cascading?▼

Yes, you can use automated code review to prevent technical debt from cascading. By enforcing a subagent-driven review process before merging or proceeding to the next development task, deviations from project requirements are caught early.