review-code

Name: review-code
Availability: InStock
Author: PacificStudio

Review code changes for risks with prioritized findings and file references.

264|27|Updated Mar 19, 2026

Search Tags:#performance #security #maintainability #quality #code-review

Ready to run

npx skills add https://github.com/PacificStudio/openase --skill review-code-pacificstudio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/PacificStudio/openase/tree/main/internal/builtin/skills/review-code
Command: npx skills add https://github.com/PacificStudio/openase --skill review-code-pacificstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps software teams perform consistent, thorough code reviews focused on risk, security, performance, and maintainability, reducing post-merge defects and design debt.

Core Features & Use Cases

Structured findings: severity-rated issues with file and line references.
Scope coverage: evaluates security, performance, maintainability, and test coverage across changes.
Use Case: before merging a PR, request a comprehensive review of the changed files to surface critical issues and suggested fixes.

Quick Start

Ask the AI to perform a comprehensive code review on the latest changes and return a prioritized list of findings with file and line references.

Frequently Asked Questions about review-code

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

FAQPage Schema

How do I perform a code review on a pull request to catch security and performance issues?▼

Perform a code review by analyzing pull request diffs to evaluate security, performance, maintainability, and test coverage. This process returns prioritized findings with severity ratings and specific file and line references for actionable feedback.

What is the best way to automate code reviews for feature branches before merging?▼

Automating code reviews for feature branches evaluates changed files to surface critical risks and design debt. It provides structured, actionable feedback with severity-rated issues and file references, reducing post-merge defects before integration.

Can I get actionable feedback with file and line references from a diff code review?▼

Yes, reviewing a diff can generate actionable feedback with exact file and line references. The evaluation surfaces prioritized findings across security, performance, and reliability, ensuring developers can quickly locate and resolve identified risks.

Does automated code review evaluate test coverage and maintainability risks?▼

Automated code review evaluates test coverage and maintainability alongside security, performance, and reliability. It analyzes code changes to identify maintainability risks and coverage gaps, returning severity-rated issues to guide targeted improvements.

How do code reviews reduce post-merge defects and design debt in software engineering?▼

Code reviews reduce post-merge defects and design debt by thoroughly evaluating code changes for risks before integration. This consistent process identifies security vulnerabilities, performance bottlenecks, and maintainability issues early, ensuring design quality.

What are the limitations of using automated code review for risk assessment?▼

Automated code review for risk assessment relies on analyzing provided code changes and diffs. It may not capture broader system architecture context or complex business logic flaws outside the immediate diff, requiring human oversight for comprehensive evaluation.