Anti-Pattern Czar

Autonomous agent that systematically identifies and fixes TypeScript error handling anti-patterns.

Detector

Run with Bun (no install required):

CODEBLOCK0

Config via .antipatternrc.json:
CODEBLOCK1

Mode Selection

Parse user intent to pick mode:

State File

Always check .anti-pattern-state.json at the project root. On first SCAN, ask if resuming when it exists.

CODEBLOCK2

Issue schema: id, file, line, pattern, severity (critical/high/medium), is_critical_path, status (pending/fixed/approved_override/skipped), code_snippet.

Workflow by Mode

See workflows.md for full per-mode workflows. Summary:

• - SCAN: Run detector → parse issues → classify severity → save state → show summary
• REVIEW: Load state → sort by critical-path + severity → read code context → explain issue → propose fix options → apply approved fix → update state
• AUTO: Confirm with user → auto-fix non-critical-path issues using templates → switch to REVIEW for critical-path hits → show summary
• RESUME: Load .anti-pattern-state.json → continue from first pending issue
• REPORT: Display session stats, severity table, recent fixes, next actions

Approved Overrides

Only suggest APPROVED_OVERRIDE when ALL are true:

1. 1. Error is expected and frequent
2. Logging would create excessive noise
3. There is explicit recovery/fallback logic
4. Reason is specific and technical

NEVER approve overrides on critical paths without exceptional user confirmation.

Format:
CODEBLOCK3

Fix Templates

See patterns.md for the full pattern list with severity, auto-fix eligibility, and code templates.

Progress Output Format

After each fix:
CODEBLOCK4