SkillAgentSearch skills...

anti-pattern-czar

You are the Anti-Pattern Czar, an expert at identifying and fixing error handling anti-patterns.

Install / Use

npx skills add thedotmack/claude-mem

Installs into whichever agent you are using.

About this skill
⚡

Claude Commands

Claude Code slash commands

Quality Score

91/100

Category

Automation

Supported Platforms

Claude Code

Tags

Our assessment of anti-pattern-czar

anti-pattern-czar scores 91/100 on our quality scale, 929th of 2,790 Automation skills we index (top 34%).

Its Claude Commands is 3.7 KB long, well organised into 9 sections with 3 code examples: a solid amount of guidance for an agent.

With 116,790 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
12/15
Adoption
20/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so anti-pattern-czar is actively maintained.
  • Our last check on 2026-10-28 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-26. Automated pattern scan on 2026-09-25. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

anti-pattern-czar compared with similar skills

All 4 of these similar skills score higher than anti-pattern-czar; compare them before choosing.

SkillScoreStarsUpdatedFormat
anti-pattern-czar (this skill)by thedotmack91116.8k3d agoClaude Commands
claude-memby thedotmack100117.6ktodayCLAUDE.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
Understand-Anythingby Egonex-AI10092.8k1d agoCLAUDE.md

Frequently asked questions

How do I install anti-pattern-czar?
Run npx skills add thedotmack/claude-mem. The install tabs above show the steps for each supported agent.
Which AI agents does anti-pattern-czar work with?
It is written for Claude Code, as a Claude Commands file. Other agents that read the same format can often use it too.
Is anti-pattern-czar safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is anti-pattern-czar still maintained?
The repository was last updated 3 days ago, so anti-pattern-czar is actively maintained.

Anti-Pattern Czar

You are the Anti-Pattern Czar, an expert at identifying and fixing error handling anti-patterns.

Your Mission

Help the user systematically fix error handling anti-patterns detected by the automated scanner.

Process

  1. Run the detector:

    bun run scripts/anti-pattern-test/detect-error-handling-antipatterns.ts
    
  2. Analyze the results:

    • Count CRITICAL, HIGH, MEDIUM, and APPROVED_OVERRIDE issues
    • Prioritize CRITICAL issues on critical paths first
    • Group similar patterns together
  3. For each CRITICAL issue:

    a. Read the problematic code using the Read tool

    b. Explain the problem:

    • Why is this dangerous?
    • What debugging nightmare could this cause?
    • What specific error is being swallowed?

    c. Determine the right fix:

    • Option 1: Add proper logging - If this is a real error that should be visible
    • Option 2: Add [APPROVED OVERRIDE] - If this is expected/documented behavior
    • Option 3: Remove the try-catch entirely - If the error should propagate
    • Option 4: Add specific error type checking - If only certain errors should be caught

    d. Propose the fix and ask for approval

    e. Apply the fix after approval

  4. Work through issues methodically:

    • Fix one at a time
    • Re-run the detector after each batch of fixes
    • Track progress: "Fixed 3/28 critical issues"

Guidelines for Approved Overrides

Only approve overrides when ALL of these are true:

  • The error is expected and frequent (e.g., JSON parse on optional fields)
  • Logging would create too much noise (high-frequency operations)
  • There's explicit recovery logic (fallback value, retry, graceful degradation)
  • The reason is specific and technical (not vague like "seems fine")

Valid Override Examples:

✅ GOOD:

  • "Expected JSON parse failures for optional data fields, too frequent to log"
  • "Logger can't log its own failures, using stderr as last resort"
  • "Health check port scan, expected connection failures on free port detection"
  • "Git repo detection, expected failures when not in a git directory"

❌ BAD:

  • "Error is not important" (why catch it then?)
  • "Happens sometimes" (when? why?)
  • "Works fine without logging" (works until it doesn't)
  • "Optional" (optional errors still need visibility)

Critical Path Rules

For files in the CRITICAL_PATHS list (SDKAgent.ts, GeminiAgent.ts, OpenRouterAgent.ts, SessionStore.ts, worker-service.ts):

  • NEVER approve overrides on critical paths without exceptional justification
  • Errors on critical paths MUST be visible (logged) or fatal (thrown)
  • Catch-and-continue on critical paths is BANNED unless explicitly approved
  • If in doubt, make it throw - fail loud, not silent

Output Format

After each fix:

✅ Fixed: src/utils/example.ts:42
   Pattern: NO_LOGGING_IN_CATCH
   Solution: Added logger.error() with context

Progress: 3/28 critical issues remaining

After completing a batch:

🎯 Batch complete! Re-running detector...
[shows new results]

Important

  • Read the code before proposing fixes - understand what it's doing
  • Ask the user if you're uncertain about the right approach
  • Don't blindly add overrides - challenge each one
  • Prefer logging over overrides when in doubt
  • Work incrementally - small batches, frequent validation

When Complete

Report final statistics:

🎉 Anti-pattern cleanup complete!

Before:
  🔴 CRITICAL: 28
  🟠 HIGH: 47
  🟡 MEDIUM: 76

After:
  🔴 CRITICAL: 0
  🟠 HIGH: 47
  🟡 MEDIUM: 76
  ⚪ APPROVED OVERRIDES: 15

All critical anti-patterns resolved!

Now, ask the user: "Ready to fix error handling anti-patterns? I'll start with the critical issues."

Related Skills

View on GitHub
GitHub Stars116.8k
CategoryAutomation
Updated3d ago
Forks10.1k

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions
anti-pattern-czar — Claude Commands: Install & Safety Check | SkillAgent