Documentation drifts as a product changes. This page is the routine for keeping it current.
After a product change
Run doxloop update to bring documentation in line with what changed since the last successful run:
doxloop update "Update affected pages for the latest product changes."Doxloop reports committed and uncommitted source changes since the recorded synchronization baseline and directs the agent to the affected pages only, instead of a full re-read.
.doxloop/sync-state.json when your team should share one update baseline, so the next person to run update doesn't re-inspect changes someone else already documented.Periodic review
Run a read-only quality pass on a schedule, or before a release:
doxloop reviewreview never edits files, so it's safe to run on a schedule without risking unintended changes, and it reports prioritized findings across accuracy, coverage, information architecture, editorial quality, accessibility, and maintainability.
Keep skills current
Doxloop's project-local skills can drift from the packaged version if you or a teammate customized them, or if you upgrade Doxloop itself. Check status and update deliberately:
doxloop agent status
doxloop agent updateagent status reports each skill as missing, current, or modified. Review a modified skill's diff before running agent update, which replaces it unconditionally.
Upgrade Doxloop itself
npm install --global @doxbrix/doxloop@latest
doxloop --versionAfter upgrading, run doxloop agent update in each project to pick up any skill changes, and doxloop generator doctor to confirm an external generator package is still compatible.
Keep generator packages current
For a project using an external generator, keep its package updated alongside your other dev dependencies (npm update, pnpm update, or yarn upgrade, depending on your package manager), then confirm it's still working:
doxloop generator doctor