skills.rest
roborew
roborewCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Review pull requests for bugs, security risks, and merge readiness.

Updated Jul 21, 2026
Search Tags:#testing#quality assurance#code review#security#merge readiness#gatekeeping
One-click install
npx skills add https://github.com/roborew/opencode --skill review-roborew
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/roborew/opencode/tree/main/skills/review
Command: npx skills add https://github.com/roborew/opencode --skill review-roborew

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill acts as a gatekeeper for code quality, identifying risks and ensuring that code meets standards before merging.

Core Features & Use Cases

  • Code Quality Assessment: Reviews code for bugs, security vulnerabilities, and correctness.
  • Merge Readiness Verification: Checks if code passes tests, meets coverage requirements, and addresses all identified issues.
  • Use Case: Before merging a new feature into the main branch, use this Skill to perform a thorough review, ensuring it's free of critical defects and adheres to project standards.

Quick Start

Use the review skill to assess the code changes in the current pull request.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check code quality and merge readiness before merging a pull request?▼

Code quality and merge readiness checks review your pull request for bugs, security vulnerabilities, correctness, and adherence to testing and coverage requirements. This process analyzes changes and outputs a structured artifact detailing required fixes and a final merge verdict.

What does a code review gate check evaluate in a software development project?▼

A code review gate check evaluates bugs, security risks, correctness, and testing coverage requirements. It analyzes pull requests to ensure code meets project standards, producing a structured artifact with required changes, acceptance checks, and a merge readiness verdict.

Can I use an automated reviewer to verify testing and coverage requirements before a merge?▼

Yes, an automated reviewer verifies testing and coverage requirements alongside bugs and security risks. It analyzes your pull request changes and generates a structured artifact that details required changes, acceptance checks, and a merge readiness verdict.

What is the best way to identify security vulnerabilities and correctness issues in new code?▼

The best way to identify security vulnerabilities and correctness issues is a dedicated code review assessment. It analyzes pull requests for defects and risks, requiring a structured artifact output that details required changes, acceptance checks, and a merge readiness verdict.

Does a merge readiness review output a structured list of required changes?▼

Yes, a merge readiness review outputs a structured artifact detailing required changes, acceptance checks, and a final merge verdict. This ensures all identified bugs, security risks, and coverage gaps are addressed before code integration.

Related Skills

Explore More Software Engineering Skills→
first-flukefirst-fluke
218

frontend-code-review

Review React, Next.js, and TypeScript code changes against a standardized checklist.

Official
Basic
infraspecdevinfraspecdev
3

review

Review code changes for correctness, security, cost, architecture, and acceptance criteria gaps.

Official
Advanced
thomfilgthomfilg

check

Automate code review, test execution, and requirements verification.

Community
Intermediate
icartshicartsh
4

code-analyze

Analyze .NET solutions for code quality, security, and dependency issues.

Community
Advanced