doc-source-reconciliation

Installation
SKILL.md

Doc–Source Reconciliation

Use this skill to verify that a document claiming to describe the current codebase actually matches it, before that document is trusted, merged, or handed off. The recurring failure mode it prevents is silent drift: a spec that still says .hpp after the code moved to .h, lists a dependency that was removed, names an example target that was renamed, enumerates an error enum that gained members, or bakes in "127 tests" that is now wrong.

The governing rule: facts that the tree can confirm are verified against the tree, not copied from a prior artifact or from memory.

When to Use

Use when a doc is described as "amended from implementation", "current state", "reflects the code", or is simply older than recent changes and about to be relied on (merged, published, used for handoff). Out of scope: forward-looking design docs that intentionally describe a future state, and pure product requirements with no implementation claims yet.

Required Inputs

  • The doc (or section) that claims to reflect current source.
  • The repository or path to reconcile against (read-only inspection).

If the repository is unavailable, emit the ## Unverifiable section (a BLOCK result) listing every claim you could not confirm, rather than asserting any of them are correct.

What To Reconcile

Installs
3
GitHub Stars
2
First Seen
Aug 27, 2026