documentation-writer

To automate documentation updates in a pull request, this Skill computes the diff against the PR merge-base and applies incremental, docs-only edits to synchronize changes. It generates a single, idempotent commit restricted to documentation files.

Diff-based documentation synchronization computes code changes relative to the PR base and applies only the necessary documentation-related edits. This ensures repository docs accurately reflect the current codebase without modifying non-documentation files.

To keep Mermaid diagrams and README files in sync, this Skill applies diff-based updates during PR workflows. It restricts edits to docs/, root README, and diagram assets, ensuring documentation reflects the latest codebase changes.

No, this documentation update tool does not modify source code files. It enforces scope confinement by restricting all edits to the docs/ directory and root README, preventing churn in non-documentation files.

The best way to prevent duplicate documentation commits is using idempotent validation. This Skill verifies changes before writing and ensures repeated runs produce no additional commits, outputting a single docs-only commit per update.

You can only update docs outside the docs/ directory if it is the root README file. The Skill confines all other documentation updates strictly to the docs/ folder to avoid unnecessary file churn.