framework-rot-auditlisted

Framework-internal rot/silo audit. Detects wiring/reference rot in a DevForgeAI install — artifacts DEFINED but never wired in (orphaned agents/hooks/skills = silos) and references that point at a NON-EXISTENT artifact (dangling) — and orchestrates the existing dead-code-detector for function-level dead code, then synthesizes a GROUNDED inventory report. Read-only: it never mutates the repo and never asserts a false orphan (mentioned-but-uninvoked is INCONCLUSIVE, not orphan). Use when the user runs /audit-rot, asks to audit the framework for orphans / dead code / silos / rot, or asks "what is defined but never used here". Do NOT use for structural orphans like backups/duplicates/dual-path size-drift (use /audit-orphans) or for a reference-sweep migration (use /migrate-refs).
bankielewicz/DevForgeAI · ★ 4 · AI & Automation · score 66

Install: claude install-skill bankielewicz/DevForgeAI

# Framework Rot Audit A **read-only** audit of a DevForgeAI install for wiring/reference rot. It complements the existing detectors rather than duplicating them: | Concern | Owner | |---|---| | **Wiring rot** — defined-but-unwired (orphan/silo) + dangling references | **this skill** (via `devforgeai-validate audit-wiring`) | | Function-level dead code (unused functions) | `dead-code-detector` subagent (orchestrated in Phase 02) | | Structural orphans (backups, duplicates, dual-path size-drift, skill-dirs) | `/audit-orphans` (NOT re-run here; cross-referenced) | | Dual-path byte-drift | `Verify Mirror Sync` CI (NOT re-run here) | **Core principle — never assert a false orphan.** A GROUNDED orphan exists only when an artifact's name appears NOWHERE outside its own definition. A name that appears but in no invocation form is INCONCLUSIVE ("mentioned, wiring unconfirmed"), never an orphan. Every finding records the forms searched. See `.claude/rules/core/epistemic-integrity.md`. **If ambiguous or conflicts detected: HALT and use AskUserQuestion.** --- ## Execution Model This skill expands inline. After invocation, execute Phase 00 immediately; run the phases in order. This is a **read-only audit** — there is no TDD phase-state machine, no `phase-init`/`phase-record` CLI gates, and no spec-file/test-file writes. The deterministic engine is `devforgeai-validate audit-wiring`; its JSON output (not LLM judgment) is the source of every wiring finding. **Behavioral admonitions*