solution-critic

Critique proposed bug fixes to identify failure modes, edge cases, and security concerns.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/yuridefranca/ai-prompts --skill solution-critic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solution-critic
Source: https://github.com/yuridefranca/ai-prompts/tree/main/src/skills/solution-critic
Command: npx skills add https://github.com/yuridefranca/ai-prompts --skill solution-critic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents premature or incomplete bug fixes by adversarially stress-testing proposed solutions to uncover failure modes, edge cases, performance regressions, security holes, and unintended side effects before implementation.

Core Features & Use Cases

  • Adversarial Failure Mode Discovery: Systematically identify at least two plausible ways the proposed fix can fail across data, timing, state, integration, and scale categories.
  • Edge Case & Boundary Analysis: Enumerate uncommon but valid inputs and boundary conditions (empty, extreme, unicode, special characters) that the fix may not handle.
  • Performance and Security Review: Surface N+1 patterns, blocking operations, missing indexes, injection/XSS/authorization issues, and sensitive-data leaks.
  • Use Cases: Validate hotfixes for production incidents, review patches in code review, and vet design changes for high-impact features.

Quick Start

Use the solution-critic skill to adversarially review the proposed fix and produce at least two failure modes, edge cases, performance concerns, security issues, side effects, and concrete mitigations.

Frequently Asked Questions about solution-critic

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

FAQPage Schema
How do I find failure modes in a proposed bug fix before implementation?

You can validate a hotfix by running an adversarial review that surfaces unintended side effects, missing indexes, blocking operations, and injection risks before the patch ships to production.

What is adversarial code review for pre-implementation patches?

Edge case analysis during security review targets uncommon but valid inputs, enumerating boundary conditions like empty values, extreme limits, unicode, and special characters that a proposed fix may not handle correctly.

How do I review a hotfix for performance and security regressions?

Edge case analysis during security review targets uncommon but valid inputs, enumerating boundary conditions like empty values, extreme limits, unicode, and special characters that a proposed fix may not handle correctly.

Can I use failure mode analysis for post-root-cause incident response?

To find failure modes in a bug fix, apply adversarial critique to the change plan and its assumptions, systematically uncovering at least two plausible ways the fix can fail across data, timing, state, integration, and scale categories.

When should I not rely solely on a proposed fix for critical bugs?

Review a hotfix for regressions by analyzing the change plan for N+1 query patterns, blocking operations, missing indexes, injection vulnerabilities, XSS risks, authorization issues, and sensitive-data leaks.