requesting-code-review

Dispatch a subagent to analyze code changes against defined plans and requirements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the code review process, ensuring that code changes are thoroughly checked for quality, adherence to requirements, and production readiness before being merged.

Core Features & Use Cases

  • Automated Code Analysis: Leverages a subagent to perform detailed code reviews.
  • Structured Feedback: Provides categorized feedback (Critical, Important, Minor) on code quality, architecture, testing, and requirements.
  • Use Case: After implementing a new user authentication module, dispatch this Skill to get a comprehensive review, identify potential bugs, and ensure it meets security standards before merging into the main branch.

Quick Start

Use the requesting-code-review skill to get a code review for your latest changes.

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 git commits before merging?

Automating code review for git commits involves dispatching a specialized subagent to analyze changes against requirements. It identifies issues in development workflows by using git commands to define commit ranges and applying a structured template for feedback.

What is the best way to verify feature implementation against requirements before a merge?

Verifying feature implementation against requirements before a merge is best achieved by dispatching a subagent for detailed code analysis. It provides categorized feedback on code quality, architecture, and testing to ensure production readiness.

How does subagent code analysis work for pre-merge verification?

Subagent code analysis for pre-merge verification works by evaluating code changes against structured plans and requirements. It categorizes feedback into Critical, Important, and Minor issues regarding code quality and architecture to facilitate early bug detection.

Do I need specific git commands to identify commit ranges for code review?

Yes, specific git commands are required to identify commit ranges for code review. The automated analysis process uses these commit ranges to determine the exact code changes evaluated against your defined plans and requirements.

What categories of feedback does automated code review provide?

Automated code review provides structured feedback categorized into Critical, Important, and Minor issues. These categories cover code quality, architecture, testing, and requirements adherence to ensure thorough pre-merge verification.