memtrace-quality

## Overview Code quality via graph analysis — dead code, complexity hotspots, repository stats. ## Quick Reference | Tool | Purpose | Required | Key optional | |------|---------|----------|--------------| | `find_dead_code` | Zero-caller symbols | `repo_id` | `include_tests`, `limit`, `kinds[]` | | `find_most_complex_functions` | Ranked complexity hotspots | `repo_id` | **`top_n`** (def 20) — not `limit` | | `calculate_cyclomatic_complexity` | Score one symbol | `repo_id`, **`target`** | — | | `get_repository_stats` | Repository overview | `repo_id` | `branch` | > **Parameter types:** numbers must be JSON numbers — `limit: 20`, never `"20"` (MCP error -32602). Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root). ## Steps ### 1. Repository overview ```json { "repo_id": "memdb" } ``` ### 2. Dead code ```json { "repo_id": "memdb", "include_tests": false, "limit": 50 } ``` Exported symbols and entry points excluded by default. Results are candidates, not proof — callers via dynamic dispatch or reflection are invisible to the graph; verify before deleting. ### 3. Complexity hotspots ```json { "repo_id": "memdb", "top_n": 10 } ``` Ordered by call-graph out-degree. | Score | Rating | Action | |-------|--------|--------| | <5 | Low | Fine | | 5-10 | Medium | Consider simplifying | | 10-20 | High | Refactor candidate | | >20 | Critical | Refactor priority | ### 4. Single symbol complexity ```json { "...