patterns

# Pattern Analysis **Recommended model tier:** balanced (sonnet) - this skill combines search with structured analysis Analyze codebase patterns using static analysis findings. Surface complexity hotspots, code duplication, coupling issues, and potential secrets. Use this skill to understand code health and identify areas that need attention. ## Prerequisites Findings must be generated first by running analyzers via the CLI: ```bash # Run all analyzers ./.aide/bin/aide findings run --path . # Run specific analyzers ./.aide/bin/aide findings run --path . --analyzer complexity ./.aide/bin/aide findings run --path . --analyzer coupling ./.aide/bin/aide findings run --path . --analyzer secrets ./.aide/bin/aide findings run --path . --analyzer clones ``` **Binary location:** The aide binary is at `.aide/bin/aide`. If it's on your `$PATH`, you can use `aide` directly. ## Available Tools ### 1. Search Findings (`mcp__plugin_aide_aide__findings_search`) Full-text search across all findings. Supports Bleve query syntax for advanced searches. **Parameters:** - `query` (required) — Search term or Bleve query - `analyzer` (optional) — Filter to one analyzer: `complexity`, `coupling`, `secrets`, `clones` - `severity` (optional) — Filter by severity: `info`, `warning`, `critical` - `file` (optional) — Filter by file path substring - `limit` (optional) — Max results (default 20) **Example usage:** ``` Search for: "high complexity" -> findings_search query="complexity" severity...