doc-amend

To amend missing documentation files into specific git commits, you use an interactive rebase workflow that analyzes commit history, drafts missing README, tests, and markdown files, then prompts you to approve each amendment per commit during the rebase process.

The best way to ensure every commit ships with complete documentation is running a phase-based workflow that analyzes commits, drafts missing docs, confirms the plan, and executes an interactive rebase with per-commit prompts to update README, tests, stories, and markdown.

Yes, you can update README and tests across split commits without losing the original structure by using an interactive rebase workflow that pauses at each commit to prompt you for confirmation before amending the missing documentation files directly into that specific commit.

To review and amend missing documentation across the last five commits, run the doc-amend command with HEAD~5 to initiate commit analysis, draft missing files, confirm the plan, and execute per-commit amendments during an interactive rebase.

The documentation files targeted for commit amendment include README files, tests, stories, and markdown files that may be missing or incomplete across your split commits in a multi-commit feature, fix, or removal workflow.

You should use an interactive rebase workflow to amend missing docs when your project follows a multi-commit feature, fix, or removal workflow where documentation is split across commits and requires per-commit confirmation to ensure complete project docs are shipped.