harness-doctorlisted

Scans a project's harness structure (.claude/ directory, CLAUDE.md, rules, agents) to diagnose complexity, drift, missing files, and broken references, then suggests improvements. `--lint` flag adds language-pattern scan (self-marketing, cushion words, version brags). Triggered by "harness check", "structure diagnosis", "CLAUDE.md audit".
chrono-meta/forge-harness · ★ 2 · AI & Automation · score 74

Install: claude install-skill chrono-meta/forge-harness

# harness-doctor — Harness Structure Diagnosis + Prescription "A good harness gets simpler over time. If it's getting more complex, something is wrong." Diagnoses harness structural health across 5 layers and proposes M/S/R prescriptions: 1. **L1 Structural completeness** — required file existence (CLAUDE.md · .claudeignore · .claude/) 2. **L2 Complexity** — current state vs. simplification principle (line count · unused files · duplicate definitions) 3. **L3 Drift** — rule vs. actual pattern mismatch (broken references · stale files · conflicting rules) 4. **L4 Connection diagnosis** *(FH environment only)* — meta hub ↔ field project reference consistency 5. **L5 Pattern analysis** *(FH environment only)* — skill activity · call context appropriateness · effect metrics --- ## Execution Steps ### Step 1. Confirm Diagnostic Target Check current cwd harness file structure and determine if FH environment (tracks/ + knowledge/ + plugins/ all present). ### Step 2. L1 — Structural Completeness | File | When Missing | |---|---| | `CLAUDE.md` | **M-tier** — harness entry impossible | | `.claudeignore` | S-tier — context-doctor execution recommended | | `.claude/` directory | M-tier (when rule files exist) | ### Step 3. L2 — Complexity Diagnosis | Check | Verdict | |---|---| | CLAUDE.md ~100 lines | Normal (project) / FH threshold: 500 lines | | CLAUDE.md 100~200 lines | S-tier warning | | CLAUDE.md 200+ lines | M-tier — separation or reduction needed | | 15+ `##` sections