skills.rest
lidge-jun
lidge-junCOMMUNITY
Explore all skills by this author →
𝕏@claudeebumGitHub

requesting-code-review

Dispatch a code-reviewer subagent to analyze code changes against requirements and quality standards.

5|Updated Feb 26, 2026
Search Tags:#git#quality assurance#code review#development workflow#merge#subagent
One-click install
npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill requesting-code-review-lidge-jun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/lidge-jun/cli-jaw-skills/tree/main/requesting-code-review
Command: npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill requesting-code-review-lidge-jun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the code review process, ensuring that code meets quality standards, requirements, and is production-ready before being merged.

Core Features & Use Cases

  • Automated Code Analysis: Leverages a subagent to perform detailed code reviews.
  • Structured Feedback: Provides categorized feedback on strengths, critical, important, and minor issues.
  • Use Case: After completing a new feature, you can use this skill to get an automated review that identifies potential bugs, architectural flaws, or areas for improvement before a human reviewer even looks at it.

Quick Start

Use the requesting-code-review skill to dispatch the code-reviewer subagent for the current branch.

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 branch?▼

Automated code review dispatches a subagent to analyze branch changes against quality standards and requirements. It identifies bugs and architectural flaws, categorizing issues by severity to provide actionable feedback for developers.

What is the best way to ensure production readiness before a git merge?▼

Production readiness is assessed by dispatching a subagent to review code changes. It evaluates your branch against specified requirements and quality standards, providing structured feedback on critical issues before merging.

Can I get structured feedback on potential bugs in my development workflow?▼

Structured feedback is generated by a code-reviewer subagent that categorizes issues by severity. It identifies strengths alongside critical, important, and minor issues to improve your development workflow.

Do I need git commands to define the review range for code analysis?▼

Git commands are required to define the review range for code analysis. The subagent uses this specified range of changes to evaluate production readiness and categorize issues by severity.

How does a subagent analyze code changes against specified requirements?▼

A subagent analyzes code changes by evaluating them against specified requirements and quality standards. It categorizes identified issues by severity and assesses production readiness to provide actionable developer feedback.

Related Skills

Explore More Software Engineering Skills→
FacuMFacuM

requesting-code-review

Dispatch a subagent to analyze code changes against requirements and quality standards.

Community
Intermediate
a-tabijia-tabiji

merge

Merge reviewed pull requests into main with squash merge and branch cleanup.

Community
Intermediate
conejoRojoconejoRojo

requesting-code-review

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

Community
Advanced
cbgbtcbgbt
5

review-scope

Evaluate code changes against requirements and constraints to produce ACCEPT or VIOLATIONS reports.

Community
Basic