critical-code-reviewer

Identify critical defects and risks in code submissions with severity labels.

466|38|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/posit-dev/skills --skill critical-code-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critical-code-reviewer
Source: https://github.com/posit-dev/skills/tree/main/posit-dev/critical-code-reviewer
Command: npx skills add https://github.com/posit-dev/skills --skill critical-code-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify flaws, inefficiencies, and bad practices in submitted code with ruthless scrutiny to protect the codebase from entropy.

Core Features & Use Cases

  • Structured, severity-based feedback with Blocking, Required, and Suggestions.
  • Identifies security holes, edge cases, performance issues, and accessibility concerns across languages and frameworks.
  • Use Case: when reviewing a PR, produce concrete, actionable recommendations and a remediation plan.

Quick Start

Review the provided patch or code segment and return a structured, prioritized list of actionable fixes with severity labels.

Frequently Asked Questions about critical-code-reviewer

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

FAQPage Schema
How do I get actionable code review feedback for a pull request diff?

Code review for pull request diffs evaluates security, reliability, and performance concerns to produce a structured, prioritized list of concrete fixes with severity labels. This provides testable recommendations and a remediation plan for fast, safe shipping.

Can I use static analysis to identify security holes and edge cases across different frameworks?

Static analysis identifies security holes, edge cases, and performance issues across languages and frameworks. It evaluates single functions or entire modules to articulate critical defects and potential risks using ruthless scrutiny.

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

The best way to prioritize fixes is using severity labels: Blocking, Required, and Suggestions. This structured feedback enables fast, safe shipping by highlighting critical defects and providing concrete remediation steps.

Does this code review approach work for evaluating entire modules or just single functions?

This code review approach works across languages and frameworks for evaluating PR diffs, single functions, or entire modules. It identifies bad practices and inefficiencies to protect the codebase from entropy.

How does adversarial thinking help find potential risks in submitted code?

Adversarial thinking applies ruthless scrutiny to submitted code, identifying flaws, inefficiencies, and bad practices. It articulates all critical defects and potential risks to protect the codebase from entropy.