documentation

To detect stale documentation in a monorepo, run git diff to list changed implementation files and map them to expected docs paths. This identifies which documentation pages may need updates after recent code changes.

Documentation drift occurs when implementation changes outpace documented API surfaces. Identify it by comparing modified files from git diff against existing docs to see if core APIs, types, configs, or plugins have changed without corresponding documentation updates.

Check which API docs need updating by matching changed packages/*/src/ files to specific documentation targets. The Skill compares implementation versus documented API signals and reports which doc pages are likely stale.

This documentation freshness check applies to core APIs, types, configs, plugins, and package-level docs within the monorepo where API surface drift is possible. It focuses on implementation files under packages/*/src/ rather than every file.

Run a documentation audit when this Skill reports that multiple API surfaces have drifted after code changes. The Skill produces a concise recommendation on whether a full audit is warranted based on detected implementation versus documentation mismatches.

You can automate documentation freshness checks by running this Skill right after updating code in packages/*/src/ within your developer workflow. It uses git diff output to produce a concise list of documentation pages that may need refresh without a full sweep.