nacl-tl-diagnose

Analyze Git history, documentation drift, and code health to produce a DIAGNOSTIC-REPORT.md.

23|2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-diagnose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nacl-tl-diagnose
Source: https://github.com/ITSalt/NaCl/tree/main/nacl-tl-diagnose
Command: npx skills add https://github.com/ITSalt/NaCl --skill nacl-tl-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Project health diagnostics that systematically analyze Git history, documentation drift, and code health, producing a DIAGNOSTIC-REPORT.md to explain issues and actionable next steps.

Core Features & Use Cases

  • Parallel data collection using specialized agents to surface git health, documentation health, and code health metrics.
  • Aggregates metrics (commits, hot files, regression chains) and generates a comprehensive diagnostic report.
  • Use Case: when the project seems broken and you need a clear, evidence-based understanding of current health and recommended next actions.

Quick Start

Run /nacl-tl-diagnose to generate a DIAGNOSTIC-REPORT.md for the current project.

Frequently Asked Questions about nacl-tl-diagnose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a diagnostic report for project health issues?

Generating a diagnostic report for project health involves analyzing Git history, documentation drift, and code health to produce a structured DIAGNOSTIC-REPORT.md containing metrics, problem clusters, and actionable recommendations.

What is documentation drift and how does it affect code health?

Documentation drift occurs when project docs in directories like docs/ or .tl/ become outdated relative to code changes. It impacts code health by creating maintenance gaps, which the diagnostic analysis surfaces as problem clusters in the generated report.

Can I analyze regression chains and hot files from Git history?

Yes, you can analyze regression chains and hot files from Git history. The diagnostic tool aggregates these metrics over a configurable period to identify problem clusters and recommend next actions for active NaCl projects.

Does project health diagnosis work with docs kept in .tl/ directories?

Project health diagnosis works specifically with active NaCl projects that have Git histories and documentation primarily kept in docs/ and .tl/ directories, targeting your project's file structure for accurate health analysis.

When should I run a project health diagnostic analysis?

You should run a project health diagnostic analysis when the project seems broken and you need a clear, evidence-based understanding of current health, metrics, and recommended next actions to resolve issues.