pr-reviewer

Review finished work against definition of done and release gates.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/supermalang/ai-augmented-coding --skill pr-reviewer-supermalang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-reviewer
Source: https://github.com/supermalang/ai-augmented-coding/tree/main/.claude/skills/pr-reviewer
Command: npx skills add https://github.com/supermalang/ai-augmented-coding --skill pr-reviewer-supermalang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual burden of final pull request review by checking completion status, enforcing project conventions, validating tests, and coordinating the delivery steps needed to ship a task safely.

Core Features & Use Cases

  • Gate mode shipping: Verifies the definition of done, runs lint and tests, audits the diff, updates the roadmap, pushes the branch, and opens the pull request.
  • Audit mode review: Performs a read-only convention audit on a branch and reports blockers, fixes, nits, and confirmed good practices without changing files.
  • Use case: A developer has finished a task and wants a final automated quality gate before merge, or wants a pre-push review of changes against repository rules and release requirements.

Quick Start

Ask the skill to review a finished task for shipping or to audit your current branch against project conventions.

Frequently Asked Questions about pr-reviewer

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

FAQPage Schema
How do I automate code review and definition of done checks before opening a pull request?

Automated code review before a pull request verifies completion against the definition of done, enforces repository conventions, runs lint and tests, and coordinates the delivery steps needed to ship safely.

Can I run a read-only git diff audit on my branch without modifying files?

Yes, you can run a read-only branch audit to review a git diff against repository conventions, reporting blockers, fixes, nits, and confirmed good practices without changing files.

What is the best way to enforce release gates and update a roadmap before pushing a branch?

Enforcing release gates and updating a roadmap before pushing a branch involves validating finished work against project context, recording the delivery state, and publishing the branch safely via forge commands.

Does the pull request review process require access to project context and tests?

Yes, the pull request review process requires access to git diff, roadmap state, project context, tests, and forge commands to validate completion status and record the delivery safely.

How do I validate repository conventions and run final ship checks for a finished development task?

Validating repository conventions and running final ship checks involves auditing the diff, verifying the definition of done, running tests, and coordinating controlled pull request creation for the finished task.