docs-update-from-diff

Update documentation from git diff by first running git status and git diff --stat to identify changed files, then editing the targeted docs/ pages to accurately reflect the new code behavior.

Documentation drifts from code changes when docs/ files are not refreshed after features or refactors, leaving readers with outdated text that fails to match the actual updated behavior.

Keep docs synced with uncommitted changes by analyzing git diff findings, referencing docs-surface guidelines, and editing targeted docs/ pages to precisely align with the current code updates.

Yes, you should inspect git diff before editing docs files to ensure updates are grounded in actual code changes, preventing outdated terminology and aligning descriptions with updated behavior.

Add new documentation pages for features revealed by git status by following the docs surface map to select the right docs/developers page and updating the corresponding _meta.ts file to register it.

After updating documentation from git diff, confirm links and examples match the current CLI, search for removed names, and re-read the updated docs alongside the original diff to verify accuracy.