review

Review Git branches or pull requests and generate QA reports.

51|2|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/g2i-ai/agents --skill review-g2i-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/g2i-ai/agents/tree/main/skills/review
Command: npx skills add https://github.com/g2i-ai/agents --skill review-g2i-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review a branch or PR for merge readiness and produce a QA report, helping teams catch regressions and gaps before merging.

Core Features & Use Cases

  • Automated review of changes against QA criteria and checks.
  • Generate and save a standardized QA report to docs/qa/reports/{yyyy-mm-dd}-{branch-or-pr-slug}.md.
  • Delegate execution to a QA subagent when not already running in the QA persona to ensure consistent results.

Quick Start

Ask your AI agent to review a PR URL or branch name to generate and save the QA report.

Frequently Asked Questions about review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate QA checks for a pull request before merging?

Automating QA checks for a pull request involves reviewing the branch against established criteria to generate a merge readiness report. This Skill evaluates code changes across Git workflows to catch regressions and document findings.

What is a QA report for merge readiness and when do I need one?

A QA report for merge readiness is a standardized document evaluating code changes against quality criteria. You need one when validating feature branches or pull requests to catch regressions and gaps before merging.

How do I generate a QA report for a specific feature branch?

To generate a QA report for a feature branch, ask your AI agent to review the branch name or PR URL. The Skill applies QA checks, coordinates findings via a subagent, and saves the report to docs/qa/reports/.

Can I use this code review automation without setting up any dependencies?

Yes, you can use this code review automation without external dependencies. The Skill operates natively and delegates execution to an internal QA subagent when not already running in the QA persona to ensure consistent results.

What is the best way to document pull request reviews for QA validation?

The best way to document pull request reviews for QA validation is to generate a standardized markdown file. This Skill saves reports to docs/qa/reports/{yyyy-mm-dd}-{branch-or-pr-slug}.md, ensuring consistent tracking of checks.

Why does my code review workflow need a QA subagent?

Your code review workflow needs a QA subagent to ensure consistent evaluation of merge readiness. The Skill delegates execution to the QA persona to apply checks and document findings systematically across branches.