ok-pr-deep-review

Analyze GitHub pull requests for design, testing, security, and performance issues.

1|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/akurinnoy/ok_plugins --skill ok-pr-deep-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ok-pr-deep-review
Source: https://github.com/akurinnoy/ok_plugins/tree/main/plugins/ok-pr-review/skills/ok-pr-deep-review
Command: npx skills add https://github.com/akurinnoy/ok_plugins --skill ok-pr-deep-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a deep, comprehensive analysis of pull requests, going beyond standard code review to assess design quality, code thoughtfulness, testing rigor, and potential anti-patterns.

Core Features & Use Cases

  • In-depth Code Assessment: Analyzes architectural design, abstraction quality, and adherence to best practices.
  • Testing Rigor Evaluation: Examines test coverage, assertion quality, and identifies potential test smells.
  • Security and Performance Focus: Deep dives into security vulnerabilities and performance bottlenecks.
  • Use Case: After a standard review flags basic issues, use this Skill to ensure the PR's design is robust, tests are thorough, and no subtle security or performance flaws are overlooked.

Quick Start

Run the deep review on the provided pull request URL.

Frequently Asked Questions about ok-pr-deep-review

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

FAQPage Schema
How do I perform a deep code review on a GitHub pull request?

A deep code review evaluates design quality, testing rigor, security, and performance in a GitHub pull request. It identifies language-specific anti-patterns and verifies integration contracts with external systems for robust software quality.

What is the difference between a standard and deep pull request analysis?

Deep pull request analysis goes beyond standard reviews by assessing architectural design, abstraction quality, and code thoughtfulness. It is used after a standard review flags basic issues to ensure no subtle security or performance flaws are overlooked.

Does deep PR analysis check testing rigor and test smells?

Yes, deep PR analysis checks testing rigor by examining test coverage, assertion quality, and identifying potential test smells. It ensures tests are thorough and validates the overall software quality of the proposed changes.

Can I use this to find security vulnerabilities and performance bottlenecks?

You can use this to find security vulnerabilities and performance bottlenecks within the code. The analysis deep dives into these specific areas to ensure the pull request meets strict security and performance standards.

Do I need a prior standard review before running an advanced PR analysis?

You need a prior standard review before running this advanced PR analysis, as it requires specific conversational context and PR data to be present. It builds upon that standard review to evaluate design quality and integration contracts.

When should I not use deep design analysis for my pull request?

You should not use deep design analysis if a standard review is sufficient for your needs or if the required conversational context and PR data are missing. It is intended for complex PRs requiring thorough evaluation of anti-patterns and external system contracts.