update-project-documentation

Run a delta analysis comparing recent code changes against existing docs, then update only the affected sections. This Skill maps each change type, such as new APIs or config options, to the specific document that owns it and verifies parity afterward.

Modified signatures require updating parameter tables, return type docs, and code examples in the affected reference pages. Breaking changes should also include migration notes, and removed APIs get deprecation notices before full removal after one release cycle.

Generator-owned content such as catalog tables, benchmark charts, and stats blocks is never hand-edited. The Skill runs the project's generators instead, for example via make update-all, and only manually edits human-owned sections.

When an expected documentation file is not found, the Skill reports the missing path and recommends running the documentation generation skill first rather than creating unstructured replacements.

Yes, architecture and component relationship changes trigger updates to Mermaid diagrams in the relevant docs. If diagram rendering fails, the Skill provides the Mermaid source and flags it for manual validation.