adversarial-reasoning

Included with Lifetime

$97 forever

Stress-test solutions using the STRIKE framework. Systematically attack proposals to find weaknesses before deployment.

Code Review

What this skill does


# Adversarial Reasoning (AR)

Validate and stress-test solutions by systematically attacking them.

## When to Use

- Solution already exists and needs validation
- High-stakes decisions requiring robustness
- Security or reliability critical
- Before committing to irreversible actions
- Pre-deployment validation

## Prerequisite

AR requires a proposed solution to attack. If no solution exists, use ToT or BoT first.

## STRIKE Framework

### S - Surface Attack Vectors
Identify all possible ways the solution could fail:
- Edge cases
- Adversarial inputs
- Environmental factors
- Dependency failures
- Human factors

### T - Test Systematically
For each attack vector, design and execute tests:
- Unit-level attacks
- Integration-level attacks
- System-level attacks
- Chaos engineering approaches

### R - Rate Severity
Score each vulnerability found:
- **Critical**: Solution fundamentally broken
- **High**: Major functionality impacted
- **Medium**: Degraded experience
- **Low**: Minor issues

### I - Identify Mitigations
For each vulnerability:
- Can it be fixed?
- What's the mitigation cost?
- Is the residual risk acceptable?

### K - Kill or Keep Decision
Based on findings:
- **KILL**: Too many critical issues
- **REVISE**: Fixable issues found
- **KEEP**: Robust enough to proceed

### E - Evidence Documentation
Document all findings for future reference.

## Output Template

```markdown
## AR Validation: [Solution Name]

### Solution Under Test
[Brief description of the proposed solution]

### Attack Surface Analysis

#### Attack Vector 1: [name]
- **Attack**: [how to break it]
- **Result**: [what happened]
- **Severity**: [Critical/High/Medium/Low]
- **Mitigation**: [fix or accept]

#### Attack Vector 2: [name]
...

### Vulnerability Summary
| Vector | Severity | Exploitable | Mitigation |
|--------|----------|-------------|------------|
| [name] | High | Yes | [action] |
| [name] | Medium | No | Accept |

### Stress Test Results
- Load test: [result]
- Failure injection: [result]
- Edge cases: [result]

### Verdict
**[KILL / REVISE / KEEP]**

Confidence: X%

### Required Changes (if REVISE)
1. [change 1]
2. [change 2]

### Residual Risks (if KEEP)
- [risk 1]: [acceptance rationale]
```

## Example

**Solution**: JWT authentication for API

**Attack Vectors Tested**:
1. Token expiration bypass → PASSED (properly enforced)
2. Algorithm confusion attack → FAILED (accepts "none")
3. Secret key brute force → PASSED (256-bit key)
4. Token replay attack → PARTIAL (no jti claim)

**Verdict**: REVISE
- Fix algorithm validation
- Add jti claim for replay protection

Then: KEEP with 85% confidence

Files: 1

Size: 2.8 KB

Complexity: 11/100

Category: Code Review

Source: https://github.com/kimasplund/clawdbot-skills-pack/tree/main/cognitive-patterns/adversarial-reasoning

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts