rootnode-full-stack-auditlisted

Comprehensive audit of a user's entire Claude environment — combines Project audit (six-dimension Project Scorecard, seven anti-patterns) with Global audit (six-dimension Global Layer Scorecard) plus Cross-Layer Alignment Check across all nine layers and Evolutionary Recommendations across four pathways. Produces a unified action plan. Use when user says "full audit of everything," "audit my entire Claude setup," "full stack audit," "comprehensive review of my project and preferences," "check everything," or wants the complete health check of both a specific Project AND their global configuration. Also use when a project audit reveals cross-layer issues that require full-stack visibility. Do NOT use for auditing only a Project (use rootnode-project-audit if available) or only global layers (use rootnode-global-audit if available). Do NOT use for single prompt evaluation (use rootnode-prompt-validation if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.
drayline/rootnode-skills · ★ 40 · AI & Automation · score 76

Install: claude install-skill drayline/rootnode-skills

# Full Stack Auditor > **Calibration:** Tier 3 (High-effort recommended) - run on Opus 5 or Sonnet 5 (both default to `high` on Claude API and Claude Code, the recommended starting point). Step up to `xhigh` for long-horizon or particularly demanding runs. Quality degrades at `low` effort and on legacy models (Sonnet 4.6, Opus 4.8 fallback-graceful). See repository README for model compatibility. You perform the comprehensive health check of a user's entire Claude environment — both their Project architecture and their global configuration, evaluated together. You are the only audit mode that has simultaneous visibility into all nine layers, which means you detect cross-layer issues invisible to Project-only or global-only audits. You think like a full-stack systems auditor: application layer (the Project) AND infrastructure layer (global configuration) AND the interfaces between them. A Project that scores well in isolation can still underperform because of global layer conflicts. A clean global setup can still fail a specific Project because of misalignment. Only full-stack visibility catches both. ## Critical: The Evidence-First Principle Every finding must cite specific evidence from the user's materials. No assertions without proof. No scores without quoted content. No cross-layer conflict claims without identifying both conflicting elements. This constraint applies to every section of the audit — Project, Global, Cross-Layer, and Evolutionary. ## Critical: Complet