critic-rules

Review code changes adversarially and report critical defects with exact fixes.

2|1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/timgranlundmarsden/claude-agent-flow --skill critic-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critic-rules
Source: https://github.com/timgranlundmarsden/claude-agent-flow/tree/main/skills/critic-rules
Command: npx skills add https://github.com/timgranlundmarsden/claude-agent-flow --skill critic-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers aggressively uncover defects, edge cases, and security weaknesses in code changes before they are approved.

Core Features & Use Cases

  • Adversarial Review: Challenges implementations by constructing failure scenarios, boundary conditions, and hostile inputs.
  • Risk-Oriented Analysis: Focuses on concurrency, async failures, malformed data, authentication edge cases, and external dependency breakage.
  • Test and Visual Validation: Evaluates whether changes need regression coverage and whether HTML or CSS changes break layout on mobile.
  • Use Case: A developer submits a patch that looks fine at first glance, and this Skill pressures it until hidden bugs, missing tests, or security assumptions are exposed.

Quick Start

Review the attached code change as an adversarial critic and return only the most important defects with exact fixes.

Frequently Asked Questions about critic-rules

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

FAQPage Schema
How do I perform an adversarial code review to find security defects before approval?

Adversarial code review challenges implementations by constructing failure scenarios, boundary conditions, and hostile inputs to expose hidden bugs and security weaknesses in code changes. It pressures patches until missing tests or flawed assumptions are uncovered.

What is the best way to check for concurrency and async failures in a patch?

Risk-oriented analysis focuses on concurrency, async failures, malformed data, and external dependency breakage to find hidden defects. It targets these specific risk areas during code review to catch issues standard reviews might miss.

How do I validate frontend visual changes and ensure they do not break mobile layout?

Visual validation evaluates whether HTML or CSS changes break layout on mobile devices and checks if changes require regression coverage. This ensures frontend modifications maintain visual integrity across different screen sizes.

Does this code review approach work for refactors and new modules?

Adversarial review applies to bug fixes, refactors, new modules, frontend visual changes, and security-sensitive modifications. It requires failure scenarios and precise verdicts with exact fixes for each of these code change types.

How do I evaluate if a code change needs additional regression test coverage?

Test validation evaluates whether changes need regression coverage by analyzing the code modifications and identifying untested failure scenarios. It determines if existing tests adequately cover the new logic and boundary conditions introduced.