light-md-driftupdate

name	light-md-DriftUpdate
description	Scan project markdown docs (CLAUDE.md, README.md, docs/*.md) for drift after code changes. Flag sections out of sync with current code — class names, file paths, settings keys, procedure signatures, architecture claims. Propose and apply concrete edits. Use when user says "update md", "check docs", "refresh claude.md", "verify docs", or invokes /light-md-DriftUpdate.

Update MD docs (launcher)

This skill is a thin launcher. The scan-verify-fix work is done by the light-md-DriftUpdate agent in its own context window (reading every doc + grepping the code is heavy — keep it out of the main context). Your job: decide whether to run, resolve the scope, launch the agent, relay its report.

When to run

User invokes /light-md-DriftUpdate OR says a variant: "update md", "check docs", "verify docs", "refresh claude.md", "are the docs still accurate", "doc drift check".

Also run proactively IF all of these hold:

• Session touched 3+ source files (code changes, not just reads)
• User about to end turn / close / commit
• Project has CLAUDE.md

If uncertain whether to run, ask first.

Steps

1. Resolve scope (ask here if needed — the agent cannot). Glob **/*.md under the project root, excluding node_modules/, .git/, build/, Win32/, Win64/, __history/, *.dproj/, External/, vendored deps. If more than ~20 MD files match, ask the user which scope:

   • Root only (CLAUDE.md, README.md) — the default if they don't care
   • Root + docs/
   • All

   With $args naming a file/glob, use that as the scope and skip the question.

2. Launch the light-md-DriftUpdate agent via the Agent tool with subagent_type: light-md-DriftUpdate. Pass the resolved scope (the concrete file list or the chosen breadth) in the prompt.

3. Print the agent's returned report verbatim. It lists BROKEN / STALE / NEW fixes it applied, plus any NEEDS CONFIRMATION items it left unapplied — surface those so the user can decide.

That's it. No scanning, no claim-verification, no edits in the skill itself — the agent does all of it and applies the surgical fixes.

Where the rules live (for the agent, not for you)

The agent loads the Delphi vocabulary + clarity references from c:\Users\trei\.claude\skills\light-md-DelphiIdiom\references\ so any new prose it writes is already Delphi-idiomatic, and it holds the claim-extraction / verify / skip / anti-pattern rules. See .claude/agents/light-md-DriftUpdate.md.