Drift on merge
Live code paths compared to the docs that describe them.
Documentation drift detection
Catch documentation drift before the wiki goes quiet
Code merges without doc updates create drift. Moxie re-checks on every merge, flags gaps, and packages fixes into one weekly reviewable PR.
- On every merge. Drift is caught while the change is still fresh.
- Visible gaps. Missing or stale pages show up in the workspace.
- Human review. Cleanup PRs are drafts - your team merges.
What you get
Gap detection
See what is undocumented before onboarding or agents hit it.
Friday Cleanup
One scoped docs PR per week - review and merge when ready.
Search still works
Jump from the index to source citations even when a page is stale.
How it works
- 01
Connect GitHub
Install the app on the repos you want watched.
- 02
First index
Baseline docs and conventions from source.
- 03
Ship as usual
Every merge re-checks. Gaps accumulate in the workspace.
- 04
Friday Cleanup
Approve or edit the weekly docs PR.
FAQ
What counts as documentation drift?+
When code changes make an existing doc wrong or incomplete - renamed modules, new flows, removed endpoints, or outdated conventions.
Does Moxie edit docs without asking?+
No. Updates arrive as GitHub pull requests. Your team reviews and merges.
Can drift detection run without Friday Cleanup PRs?+
Yes. Gaps show in the workspace as soon as they are found. Friday Cleanup is the optional weekly PR rhythm.