Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.
Inspect local diffs, derive the documentation impact, and update only the repository's docs/ pages. Treat the current code as the source of truth and keep changes scoped, specific, and navigable.
Read references/docs-surface.md before editing if the affected feature does not map cleanly to an existing docs section.
Start from local Git state, not from assumptions.
git status --short, git diff --stat, and targeted git diff output.README.md and other non-docs/ content unless they help confirm intent.For every changed behavior, extract the user-facing or developer-facing facts that documentation must reflect.
Prefer updating an existing page over creating a new page. Create a new page only when the feature introduces a stable topic that would make an existing page harder to follow.
Map each change to the smallest correct documentation surface:
docs/users/**docs/developers/**docs/** and _meta.tsIf you add a new page, update the nearest _meta.ts in the same docs section so the page is discoverable.
Edit documentation with the following bar:
Verify that the updated docs cover the actual delta:
docs/ for old names, removed flags, or outdated examples_meta.tsdocs/users/configuration/settings.md, feature pages, and auth/provider docs.docs/users/features/** and docs/developers/tools/** when relevant.Produce the docs edits under docs/ that make the current local changes understandable to a reader who has not seen the diff. Keep the final summary short and identify which pages were updated.