reviewer

Review pull requests and staged diffs for correctness, security, performance, and conventions.

5|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/garethrhughes/fragile --skill reviewer-garethrhughes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer
Source: https://github.com/garethrhughes/fragile/tree/main/.opencode/skills/reviewer
Command: npx skills add https://github.com/garethrhughes/fragile --skill reviewer-garethrhughes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers quickly evaluate proposed changes for correctness, security, performance, and alignment with project conventions, reducing the risk of shipping flawed or unsafe work.

Core Features & Use Cases

  • Feature and proposal review: Checks whether the requested change matches the feature document and proposal, including scope, acceptance criteria, and unresolved questions.
  • Code and infrastructure review: Assesses implementation quality across application code, tests, APIs, Terraform, and MCP updates, with special attention to safety and consistency.
  • Actionable verdicts: Produces severity-labelled findings with traceable references so teams can decide whether a change can pass, needs comments, or must be blocked.

Quick Start

Use the reviewer skill to assess the provided change set and return a final verdict with specific findings and file references.

Frequently Asked Questions about reviewer

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

FAQPage Schema
How do I review pull requests for security risks and convention violations?

Review Terraform changes by assessing infrastructure code for safety, consistency, and convention violations. The review process checks Terraform updates alongside application code and tests, producing severity-labelled findings with a final ship verdict.

Can I verify acceptance criteria automatically during code review?

Verify acceptance criteria during code review by checking whether the proposed change matches the feature document and proposal scope. This includes validating that unresolved questions are addressed and returning specific findings if criteria are unmet.

Does this code review process work with MCP updates and API contracts?

Code review handles MCP updates and API contracts by assessing implementation quality and safety across these specific change types. It evaluates infrastructure changes including API contracts, tests, and MCP updates within the repository.

What is the best way to block risky changes before they ship?

Block risky changes before shipping by reviewing staged diffs for correctness and security flaws, then issuing a BLOCK verdict. This verdict includes severity-labelled findings with traceable file references so teams can prevent unsafe work from merging.

How do I review feature documents and proposals against implementation scope?

Review feature documents and proposals against implementation scope by checking whether the requested change matches the documented scope, acceptance criteria, and unresolved questions. The review outputs specific findings and a final verdict on alignment.