detect_antipatterns
Detect performance and design antipatterns in code: N+1 queries, missing indexes, god classes, and more. Returns categorized findings with severity and suggestions.
Instructions
Detect performance & design antipatterns: N+1 query risks, missing eager loading, unbounded queries, event listener leaks (via callSites — framework-managed listeners like Livewire/Socket.IO/NestJS gateways/Mongoose/Sequelize hooks are excluded), circular ORM association cycles, missing FK indexes, memory leaks (unbounded caches, closure-captured growing collections), god classes (>=25 methods or >=500 LOC), long methods (>=60 LOC), long parameter lists (>=6 params), deep nesting (>=5 indent levels). ORM-scoped signals require an active ORM plugin; size/complexity detectors (god_class, long_method, long_parameter_list, deep_nesting) run on every indexed symbol. For ES/CJS import cycles use get_circular_imports. For code quality (TODOs, debug artifacts, hardcoded values) use scan_code_smells. For security use scan_security. Read-only. Returns JSON: { findings: [{ category, severity, file, line, message, suggestion }], total }.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max findings to return (default: 100) | |
| category | No | Antipattern categories to check (default: all) | |
| file_pattern | No | Filter to files matching this pattern | |
| output_format | No | Output format. "json" (default) returns the native finding shape; "sarif" emits a SARIF 2.1.0 log for code-scanning ingestion. | |
| severity_threshold | No | Minimum severity to report (default: low) |