anti-pattern-detectorlisted

# Anti-Pattern Detector Detects and prevents common reliability anti-patterns across performance, concurrency, caching, monitoring, infrastructure, and build/deploy. Complements `clean-code` (quality), `security-reviewer` (security), and `devops-engineer` (Docker/K8s) by covering operational reliability gaps. ## When to Use - Code review for reliability issues (auto-triggers with `code-review-excellence`) - Debugging race conditions, deadlocks, or performance regressions - Auditing cache strategies and invalidation patterns - Reviewing monitoring, logging, and alerting coverage - Validating infrastructure configs (Terraform, Docker, K8s manifests) - Checking build/deploy safety (dependencies, migrations, rollbacks) - Pre-deployment reliability checks ## Do not use when - Task is purely about code style or formatting (use `clean-code`) - Task is purely about security vulnerabilities (use `security-reviewer`) - Task is purely about Dockerfile optimization (use `docker-expert`) - Task is purely about Kubernetes manifests (use `kubernetes-specialist`) ## Core Workflow ### Phase 1 — Scan Try tool-based detection first, fall back to manual analysis. **Automated tools (run if available):** ```bash # Concurrency + performance patterns semgrep --config=auto --include-pattern='*.py' . semgrep --config=auto --include-pattern='*.js' . semgrep --config=auto --include-pattern='*.ts' . # Python-specific bandit -r ./src flake8 --select=G,C,N . # JavaScript/TypeScript eslint --plug