Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Detect and fix TypeScript error handling anti-patterns with state persistence and approval workflows. Use when scanning a codebase for silent error failures,...
Detect and fix TypeScript error handling anti-patterns with state persistence and approval workflows. Use when scanning a codebase for silent error failures,...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Autonomous agent that systematically identifies and fixes TypeScript error handling anti-patterns.
Run with Bun (no install required): bunx antipattern-czar bunx antipattern-czar --src lib bunx antipattern-czar --config my-config.json Config via .antipatternrc.json: { "srcDir": "src", "criticalPaths": ["DatabaseService.ts", "AuthHandler.ts"], "skipDirectories": ["node_modules", "dist", ".git"] }
Parse user intent to pick mode: User SaysModeAction"scan", "detect", "find"SCANRun detector, save state"review", "fix", "help me fix"REVIEWInteractive fix session"auto", "fix all", "autonomous"AUTOBatch fix with guardrails"resume", "continue"RESUMELoad state, continue"report", "status", "progress"REPORTShow current state
Always check .anti-pattern-state.json at the project root. On first SCAN, ask if resuming when it exists. { "session_id": "<uuid>", "started_at": "<ISO>", "target_path": "<path>", "issues": [], "history": [] } Issue schema: id, file, line, pattern, severity (critical/high/medium), is_critical_path, status (pending/fixed/approved_override/skipped), code_snippet.
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
Only suggest APPROVED_OVERRIDE when ALL are true: Error is expected and frequent Logging would create excessive noise There is explicit recovery/fallback logic Reason is specific and technical NEVER approve overrides on critical paths without exceptional user confirmation. Format: } catch { // [APPROVED_OVERRIDE] <specific technical reason> // Fallback: <what happens instead> }
See patterns.md for the full pattern list with severity, auto-fix eligibility, and code templates.
After each fix: โ Fixed: src/services/example.ts:42 Pattern: NO_LOGGING_IN_CATCH Solution: Added logger.error() with context Progress: 4/28 issues remaining โโโโโโโ 14%
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.