paranoid-review

Analyze code diffs to identify bugs, security issues, and performance problems.

1|Updated Mar 15, 2026

Search Tags:#code review #code analysis #performance #security #race conditions #bug detection

Ready to run

npx skills add https://github.com/blakeox/llm-skills --skill paranoid-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: paranoid-review
Source: https://github.com/blakeox/llm-skills/tree/main/skills/paranoid-review
Command: npx skills add https://github.com/blakeox/llm-skills --skill paranoid-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps developers identify subtle bugs and vulnerabilities in code reviews that pass initial tests but may cause issues in production.

Core Features & Use Cases

Code Review Analysis: Examines code diffs to uncover race conditions, silent failures, and security vulnerabilities.
Best Practice Recommendations: Provides specific fixes for critical and high-severity issues found during review.
Use Case: A developer submits a pull request; this Skill analyzes the changes and highlights potential issues like race conditions or silent error swallowing, suggesting precise improvements.

Quick Start

Use this Skill to review a code diff in your pull request by providing the changed files and lines for analysis.

Frequently Asked Questions about paranoid-review

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

FAQPage Schema

How do I detect race conditions and silent failures during a code review?▼

To detect race conditions and silent failures during a code review, you analyze code diffs to identify potential bugs and security issues. This process uncovers subtle vulnerabilities that pass initial tests but may cause production problems.

What is the best way to find security vulnerabilities in a pull request before deployment?▼

The best way to find security vulnerabilities in a pull request before deployment is to run a pre-deployment code analysis on the changed files. This highlights critical issues and provides specific fixes for high-severity problems.

Can I use code analysis to identify performance problems in specific code changes?▼

Yes, you can use code analysis to identify performance problems in specific code changes. By providing the source code context and change details, the analysis targets the exact modifications to find potential issues.

Do I need to provide the full source code for effective bug detection?▼

You do not need the full source code for effective bug detection, but you must provide source code context and change details. Analyzing the code diffs from changed files and lines is sufficient for identifying production bugs.

Does code review analysis suggest fixes for the issues it finds?▼

Yes, code review analysis suggests fixes for the issues it finds. It provides best practice recommendations and specific improvements for critical and high-severity bugs, security issues, and performance problems detected in the diff.