reviewer

Review code diffs and pull requests for correctness, security, and regressions.

22|2|Updated Mar 24, 2026

Search Tags:#debugging #security #quality-assurance #risk-management #code-review #pull-request

Ready to run

npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill reviewer-jshsakura

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reviewer
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/reviewer
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill reviewer-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, evidence-driven PR-style review that assesses correctness, security, potential behavior regressions, and missing tests to reduce risk before changes are merged.

Core Features & Use Cases

Evidence-based review of code changes focusing on correctness, security implications, and test coverage.
Prioritizes small, high-impact fixes with clear rationale and mapping to files or diff hunks.
Validates normal execution paths, failure modes, and edge cases, with actionable mitigations.

Quick Start

Provide the PR changes you want reviewed, and I will return prioritized findings, mitigations, and validation steps.

Frequently Asked Questions about reviewer

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

FAQPage Schema

How do I automate code review for pull requests to check correctness and security?▼

Automated code review for pull requests assesses diffs for correctness, security, and test coverage. It maps scoped findings to specific files or lines, returning prioritized fixes and validation steps to reduce risk before merging.

How does evidence-based code review reduce merge risk?▼

Evidence-based code review reduces merge risk by validating normal execution paths, failure modes, and edge cases. It provides actionable mitigations and prioritizes small, high-impact fixes with clear rationale mapped to diff hunks.

How do I review a diff for missing test coverage and potential behavior regressions?▼

Reviewing a diff for missing test coverage and regressions involves analyzing changes against expected behavior. The process validates failure modes and edge cases, outputting prioritized findings with validation steps and residual risk mapping.

Can I use automated PR review for any software project diff?▼

Automated PR review applies to diffs and pull requests across software projects without platform restrictions. It assesses correctness, security implications, and test coverage, returning scoped findings regardless of the specific codebase.

What is the best way to prioritize code fixes identified during a pull request review?▼

Prioritizing code fixes during a pull request review focuses on small, high-impact changes with clear rationale. The process returns scoped findings mapped to specific files, validating execution paths to ensure actionable mitigations.