nacl-tl-reconcile

Reconcile project documentation with current code state without altering code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Emergency documentation-code reconciliation. When documentation has drifted from code, you systematically bring everything back in sync. You fix ONLY documentation — never code. If code is wrong, recommend /nacl-tl-fix.

Core Features & Use Cases

  • Phase-driven workflow: diagnosis, planning, execution, validation, and reporting to align docs with current code.
  • Supports diffing between code and docs, generating minimal, scoped updates, and keeping a health score.
  • Allows user control with flags like --report, --scope, --dry-run, and --force to plan or execute reconciliation.

Quick Start

Run /nacl-tl-reconcile to begin emergency documentation reconciliation, with optional flags like --report, --scope, or --dry-run.

Frequently Asked Questions about nacl-tl-reconcile

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

FAQPage Schema
How do I reconcile documentation drift with code without altering the source code?

To reconcile documentation drift, run the tool to diagnose discrepancies, generate an executable plan, and apply minimal scoped updates to the docs. It strictly modifies documentation to match code reality while keeping source code unaltered.

What is the best way to plan documentation updates for large-scale drift across multiple domains?

The best way to plan documentation updates for large-scale drift is using a dry-run flag to generate a diagnostic report. This identifies scope across multiple domains and screen specs before executing any actual file changes.

Can I generate a validation report after syncing project docs to the current code state?

Yes, you can generate a validation report after syncing project docs. The workflow includes a dedicated reporting phase that maintains a health score and updates the changelog and status files to confirm successful reconciliation.

Does documentation reconciliation work for multiple use cases and screen specs at once?

Documentation reconciliation handles large-scale drift across multiple use cases, domains, and screen specs simultaneously. It systematically applies minimal changes to align all affected documentation with the current code state in a single operation.

When should I force a documentation update instead of recommending a code fix?

You should force a documentation update when the code is correct but the docs are outdated. If the code itself is wrong, you should instead recommend a code fix rather than reconciling the documentation to match broken code.