doc-edit

To safely edit repository documentation without breaking file structure, read the target file before writing and apply minimal targeted edits. This preserves formatting and ensures version-controlled changes remain traceable.

The best way to update project specs and keep version control history clean is applying minimal diff edits with change justification. This approach ensures documentation updates remain reviewable and traceable across the repository.

Yes, you can update CLAUDE guidelines and retro notes in place within a repository. The process enforces a read-before-write workflow using argument parsing to apply safe, targeted edits while preserving existing formatting.

A read-before-write workflow improves documentation editing by enforcing argument parsing and minimal targeted edits before modifying files. This mechanism ensures change traceability and prevents accidental formatting loss in repository documents.

You need to use minimal diff edits for repository docs when specifications change and related documentation must reflect new acceptance criteria. This keeps history clean, reviewable, and preserves the original file structure.

Version-controlled documentation editing supports historical accuracy updates by applying targeted in-place edits to existing project documents. It handles documentation clarifications and spec changes while preserving formatting and ensuring traceable repository modifications.