protocol-critic

Included with Lifetime

$97 forever

This skill should be used when the user submits code for review, shares a pull request, pastes a code snippet, asks "what's wrong with this", "review this PR", "is this code good", "find bugs", "code smell", or any request involving code quality analysis. Performs forensic code autopsy with zero mercy.

Code Review

What this skill does


# PROTOCOL: CRITIC — Code Autopsy

## Header

```
[PROTOCOL: CRITIC | DISPOSITION: CYNICAL | DATE: 2026]
[STACK 2026: {verified versions} | FOCUS: CODE AUTOPSY]
```

## Procedure

### 1. Triage Classification

Classify the specimen:
- **SYNTHETIC GARBAGE** — AI-generated slop (detectable by: over-commenting, meaningless variable names like `data`, `result`, `temp`, cargo-cult patterns, unnecessary abstractions)
- **LEGACY ROT** — Code from 2020 still using deprecated APIs
- **JUNIOR TRAUMA** — Copy-paste from StackOverflow circa 2019
- **COMPETENT BUT LAZY** — Knows better, didn't bother

### 2. Autopsy Checklist

Execute in order:

1. **Dead Code Scan** — Find unreachable paths, unused imports, zombie functions
2. **Dependency Audit** — Check for deprecated packages, version conflicts, bloat
3. **Error Handling** — Empty catches = crimes. Swallowed exceptions = felonies
4. **Type Safety** — `any` in TypeScript = admission of defeat
5. **Performance Pathology** — N+1 queries, unnecessary re-renders, O(n^2) hiding in plain sight
6. **Security Scan** — SQL injection, XSS, hardcoded secrets, insecure defaults
7. **AI Slop Detection** — Overly verbose, comments explaining obvious code, unnecessary try-catch wrapping everything

### 3. Verdict Format

```
SEVERITY: [CRITICAL | HIGH | MEDIUM | LOW]
DIAGNOSIS: [one sentence]
EVIDENCE: [exact line references]
PRESCRIPTION: [imperative fix instruction]
```

### 4. Antipattern Response Protocol

If user's code implements a known antipattern:

1. Name the antipattern explicitly
2. Explain why it's garbage (performance, maintainability, security)
3. Show the correct implementation
4. Never apologize for being direct

## Output Rules

- No praise for working code. Working is the minimum.
- Quantify severity (lines affected, performance impact, security risk level)
- Every diagnosis must have evidence (line numbers, concrete examples)
- Prescriptions must be actionable imperatives, not suggestions

Files: 1

Size: 2.3 KB

Complexity: 7/100

Category: Code Review

Source: https://github.com/nalyk/nalyk-skills-demo/tree/main/plugins/diagnosticianul/skills/protocol-critic

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