requesting-code-review

Deploys a code-review subagent to evaluate git diffs against project requirements.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/arthrod/conejo-skills --skill requesting-code-review-arthrod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/arthrod/conejo-skills/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/arthrod/conejo-skills --skill requesting-code-review-arthrod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent or superficial code reviews by deploying a specialized subagent to perform a structured, objective analysis of your changes before they are merged.

Core Features & Use Cases

  • Structured Review: Evaluates code against specific requirements, architecture, and testing standards.
  • Severity Categorization: Automatically classifies feedback into Critical, Important, and Minor issues to prioritize your workflow.
  • Use Case: Use this before merging a major feature to ensure your implementation meets the testing doctrine and architectural requirements defined in your project plan.

Quick Start

Invoke the requesting-code-review skill by providing the base and head git commit hashes along with your task description to trigger the code reviewer subagent.

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 for a git pull request?

Automating code review for a git pull request is done by deploying a subagent to evaluate code diffs against architectural and testing standards. You trigger this autonomous review by providing base and head commit hashes alongside your task description.

What is autonomous code review and how does it categorize issues?

Autonomous code review is a structured analysis where a subagent evaluates changes objectively before merging. It automatically categorizes feedback into Critical, Important, and Minor issues to prioritize your workflow and ensure quality gates are met.

Can I use a subagent to enforce TDD and quality assurance before merging?

You can use a subagent to enforce TDD and quality assurance before merging by comparing git diffs against specific project plans. This ensures your implementation meets the testing doctrine and architectural requirements defined in your documentation.

What's the best way to perform an adversarial code review on git diffs?

The best way to perform an adversarial code review on git diffs is to deploy a specialized subagent. It provides context-aware feedback by comparing your changes against predefined architectural and testing requirements for rigorous quality gates.

Do I need to provide commit hashes to trigger an automated code review?

You need to provide base and head git commit hashes along with your task description to trigger the code reviewer subagent. This allows the autonomous agent to accurately identify and evaluate the specific code changes.