requesting-code-review

Automate sequential code reviews with specialized subagents and structured markdown output.

205|26|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/LerianStudio/ring --skill requesting-code-review-lerianstudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/LerianStudio/ring/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/LerianStudio/ring --skill requesting-code-review-lerianstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, and includes references (resource) components.

What problem does it solve?

Inconsistent or parallel code reviews can miss critical issues, leading to cascading problems. This skill automates a sequential review process with specialized subagents to ensure thorough validation.

Core Features & Use Cases

  • Sequential Review Order: Dispatches code-reviewer, business-logic-reviewer, and security-reviewer subagents in a specific sequence, each building on the previous.
  • Specialized Focus: Each reviewer focuses on a distinct domain (architecture, business logic, security) to catch specific types of issues.
  • Gate-Based Progression: Requires fixing critical/high issues at each gate before proceeding to the next reviewer, preventing issues from accumulating.

Quick Start

I've completed a major feature. Use the requesting-code-review skill to get it reviewed.

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 reviews across multiple perspectives?

Automate code reviews by dispatching specialized reviewers—code-reviewer, business-logic-reviewer, and security-reviewer—sequentially to catch architecture, business logic, and security issues in one pass. Each reviewer builds on the previous analysis before proceeding to the next gate.

When should I run automated code reviews in my development workflow?

Run automated code reviews at Gate 4, after completing major features and before merging to main. The skill auto-detects git SHAs and changed files, then generates structured feedback with issue severity, reviewer verdicts, and handoff instructions.

Can automated code reviews catch security issues alongside architecture problems?

Yes. Specialized security-reviewer subagents run in parallel with code and business-logic reviewers, delivering comprehensive multi-perspective feedback that surfaces architecture flaws, business logic gaps, and security vulnerabilities in a single structured markdown report.

What happens if critical issues are found during automated review?

The sequential gate-based process requires fixing critical and high-severity issues at each review stage before proceeding to the next reviewer. This prevents issues from accumulating and ensures thorough validation before merge.

Do I need git configured to run code reviews?

Yes. The skill depends on git to auto-detect changed files and commit SHAs. Once git is available, the skill generates implementation summaries, infers requirements, and outputs structured markdown with review verdicts and severity categorization.