updatedocs

Update repository documentation by identifying affected Markdown files through a dependency matrix and applying targeted, pattern-preserving edits. This ensures docs accurately reflect code, service, and configuration changes without restructuring content.

Keeping project documentation synchronized involves matching change types like ports, services, and endpoints against a dependency matrix to find affected docs. It then applies surgical edits to modify only exact lines required, preserving existing tables and headings.

Identify affected Markdown files by matching specific change types, such as endpoints, agents, skills, or log paths, against a dependency matrix. This produces a precise list of documentation files requiring targeted updates.

Yes, you can update .claude reference docs and skill indexes without rewriting files by reading each target Markdown file completely, copying existing entry patterns, and modifying only the exact lines required to reflect the changes.

Yes, this approach preserves existing Markdown formatting and heading levels by validating format conventions and performing minimal, surgical edits. It modifies only exact lines required without reformatting content or altering document structure.

A key limitation is that surgical editing avoids restructuring content or changing heading levels, focusing solely on minimal pattern-preserving modifications. It requires reading each affected file in full to accurately match change types to the dependency matrix.