doc-check

Markdown documentation affected by code changes is detected by reading YAML frontmatter depends-on declarations and Markdown links to build a dependency graph, then matching it against git diff output to identify impacted files.

The depends-on frontmatter tracks documentation dependencies by accepting declared file paths or globs, which are parsed to calculate the impact scope when code files change, ensuring documentation stays synchronized with code modifications.

Keeping Markdown docs in sync with code changes is handled by a script that builds a dependency graph from frontmatter and links, detects impacted documents via git diff, and prompts for user-approved updates with diffs.

Manual approval is required for documentation updates detected through change tracking, as the workflow provides a user-driven update flow that presents diffs for review before applying any modifications to impacted Markdown files.

Markdown links are used to construct a dependency graph for change detection by extracting link references from the document body and cross-referencing them with git diff to pinpoint which documentation requires updates.

Documentation impact detection should be run after completing tasks that include code changes or by launching it directly, ensuring that Markdown files accompanying code modifications are identified and updated before finalizing the workflow.