weekly-maintenancelisted

______________________________________________________________________ ## weekly-maintenance Execute comprehensive weekly maintenance routine (1-2 hours, Friday recommended): ## 1. Codebase Health Check Run the project's quality/health tools (from CLAUDE.md Commands section): ```bash # Use project-specific commands, e.g.: # just health, npm run lint, cargo clippy, etc. ``` Report on: - Complexity trends (should be stable or decreasing) - Duplication percentage (target: <5%) - High-churn files that may need attention - Dead code: unused exports, orphaned functions (run monthly or when codebase > 5K LOC) ## 2. Code Quality Agent Review Use the code-quality skill to analyze the entire codebase: - Flag any functions with CCN >10 - Identify duplication patterns - Check for pattern consistency violations ## 3. Documentation Review Check key documentation for accuracy: - @CLAUDE.md accuracy (commands, paths, patterns still correct?) - @docs/progress.md completeness - Any drift between docs and implementation - **Documentation efficiency**: Key context files (CLAUDE.md, progress.md, BACKLOG_INDEX.md) are loaded every session — keep them lean. Archive stale content, deduplicate, condense verbose sections. - **Metrics freshness**: If `docs/progress.md` → `## Sprint History` has ≥2 data rows but `## Metrics` table still shows "—" values, sprint-end is not computing metrics — flag as a measurement gap. The feedback loop is broken: data collected but not surfaced. ## 4. Depe