requesting-code-review

Analyze Git commit ranges for bugs and architectural flaws.

21|9|Updated May 27, 2026

Search Tags:#git #best-practices #quality-assurance #code-review #software-engineering

Ready to run

npx skills add https://github.com/cq112233/unibestX --skill requesting-code-review-cq112233

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/cq112233/unibestX/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/cq112233/unibestX --skill requesting-code-review-cq112233

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of code quality degradation and logic errors by enforcing a structured, agent-driven review process before merging changes or proceeding to complex tasks.

Core Features & Use Cases

Structured Evaluation: Uses a dedicated reviewer template to ensure consistent assessment of architecture, quality, and requirements.
Git-Aware Context: Leverages Git SHA ranges to provide reviewers with precise, isolated diffs for accurate analysis.
Use Case: After completing a complex feature implementation, use this skill to dispatch a code-reviewer agent to verify that the new code aligns with the original technical plan and meets production standards.

Quick Start

Use the requesting-code-review skill to initiate a formal code review for the current branch against the main 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 for specific Git commits?▼

To automate code review for specific Git commits, dispatch an AI reviewer agent to analyze isolated commit ranges against defined project requirements. This process evaluates architecture, quality, and logic to catch bugs before merging changes.

What is the best way to catch architectural flaws before merging a feature branch?▼

The best way to catch architectural flaws before merging is to use an agent-driven review process that compares your feature branch against the main branch. This ensures new code aligns with the original technical plan and meets production standards.

Can I use a dedicated AI reviewer to verify if new code aligns with an implementation plan?▼

Yes, you can dispatch a dedicated AI reviewer to verify if new code aligns with an implementation plan. The reviewer uses a structured template to assess architecture, quality, and requirements adherence within your specified Git SHA ranges.

How does agent-driven code analysis work with Git history?▼

Agent-driven code analysis works with Git history by leveraging Git SHA ranges to provide the reviewer with precise, isolated diffs. This allows the AI agent to perform comparative code analysis and identify critical bugs accurately.

Do I need general-purpose task tools to perform systematic code quality assurance?▼

Yes, you need general-purpose task tools to perform systematic code quality assurance. The review process requires access to Git history and the ability to execute these tools for accurate comparative code analysis.

When should I not use an automated code review agent?▼

You should avoid using an automated code review agent for changes outside a defined Git commit range or when project requirements are undefined, as the analysis relies on comparing specific diffs against established technical plans.