Verified:GitHub

requesting-code-review

Name: requesting-code-review
Availability: InStock
Author: Raybird

Automates code review by dispatching a subagent to evaluate git diffs against defined requirements and architectural standards.

1|Updated Jan 28, 2026

Search Tags:#automation #git #software engineering #quality assurance #code review #subagent

Ready to run

npx skills add https://github.com/raybird/telenexus --skill requesting-code-review-raybird

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/raybird/telenexus/tree/main/skills/tao-of-opencode/references/superpowers/requesting-code-review
Command: npx skills add https://github.com/raybird/telenexus --skill requesting-code-review-raybird

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of human oversight in code quality by automating the code review process, ensuring that issues are caught early before they cascade into larger architectural problems.

Core Features & Use Cases

Automated Review Dispatch: Triggers a specialized code reviewer subagent to analyze git diffs against specific requirements.
Severity Categorization: Automatically classifies feedback into Critical, Important, and Minor issues to prioritize developer focus.
Use Case: After implementing a new feature, use this skill to verify that your code matches the original plan and adheres to best practices before merging into the main branch.

Quick Start

Request a code review for the changes between the current commit and the previous one by providing the description and plan to 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 git diffs before merging?▼

Automated code review dispatches a subagent to evaluate git diffs against defined requirements and architectural standards. It provides structured feedback on code quality, plan alignment, and production readiness before merging features.

What is the best way to ensure code matches original development plans?▼

To ensure code matches original plans, a code reviewer subagent evaluates git diffs against specific requirements and architectural standards. This automated process verifies plan alignment and catches issues early before merging into the main branch.

How does automated code review categorize feedback severity?▼

Automated code review categorizes feedback severity by classifying identified issues into Critical, Important, and Minor levels. This severity categorization helps prioritize developer focus on the most crucial architectural problems before merging features.

Can I use this code review automation for quality assurance after feature implementation?▼

You can use code review automation for quality assurance after implementing a new feature. It triggers a specialized subagent to analyze git diffs, verifying that your code matches the original plan and adheres to best practices before merging.

Do I need to provide a plan and description to trigger an automated git diff review?▼

You need to provide the description and plan to the code reviewer subagent to trigger an automated git diff review. This input allows the subagent to evaluate changes between the current commit and the previous one against your requirements.

What limitations exist when automating software engineering quality assurance with subagents?▼

Automating software engineering quality assurance with subagents relies on evaluating git diffs against defined requirements. It is designed for objective feedback on code quality and production readiness, but does not replace human oversight for complex architectural decisions.