requesting-code-review

Dispatch a subagent to evaluate git-based changes against project requirements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill mitigates the risk of deploying buggy or architecturally unsound code by enforcing a structured, subagent-driven review process before any major feature or merge.

Core Features & Use Cases

  • Automated Review Dispatch: Triggers a specialized code-reviewer subagent to analyze git diffs against defined requirements.
  • Severity Categorization: Automatically classifies feedback into Critical, Important, and Minor issues to prioritize developer effort.
  • Use Case: Before merging a new feature branch into main, use this skill to verify that your implementation meets the original technical plan and adheres to quality standards.

Quick Start

Use the requesting code review skill to analyze the changes between the current branch and the main branch based on the deployment 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 automate code review before merging a git branch?

To automate code review before merging, this Skill dispatches a specialized subagent to evaluate git diffs against project requirements and categorizes feedback by severity. It systematically checks production readiness, testing coverage, and design patterns before code integration.

What is subagent-driven code quality assurance?

Subagent-driven code quality assurance is a process where a specialized subagent systematically evaluates git-based changes against technical plans. It enforces rigorous peer review, architectural validation, and production readiness checks to mitigate deploying unsound code.

How do I categorize code review feedback by severity?

To categorize code review feedback by severity, the subagent automatically classifies issues into Critical, Important, and Minor tiers. This prioritization helps developers focus on architectural validation and critical production readiness problems before merging.

Can I use this code review process for any software development lifecycle?

You can use this code review process for software development lifecycles requiring rigorous peer review and production readiness checks. It applies specifically to git-based workflows that need consistent, objective feedback on code quality and testing coverage before merging.

How does automated code review validate architectural design patterns?

Automated code review validates architectural design patterns by dispatching a subagent to analyze git diffs against defined project requirements. It provides objective feedback on whether the implementation adheres to established quality standards before deployment.