Cleanup
Cleanup finds the pages in your docs that describe things you removed or never built. It checks the pages you pick against today's code and the full history of the repos you pick, and gives each page a verdict with the commit that proves it. It never changes a page. Cleanup has its own screen in the sidebar, under Generate docs.
Who can use it?
In early access: turned on per team. Write to hello@amendary.com to try it. Once it is on, Cleanup has its own entry in the sidebar, and the Pages tab links to it with “Find pages to clean up”.
What does a cleanup do?
- From the Cleanup screen, start a new cleanup and pick Notion pages by destination and parent, watched or not, up to 50 per cleanup. Pages in a GitHub docs folder or wiki are not in the picker yet.
- You pick the repos to check them against. Every connected repo is ticked by default.
- You see the estimate in credits, with a line per repo, before anything runs.
- Amendary reads each page once, then searches each repo in turn: the code as it is today and every commit in its history.
- Each page gets a verdict, the evidence behind it, and anything that could not be checked.
- Every cleanup is listed on the Cleanup screen. Open one to see its report, filter it by verdict, and open a page for its claims and evidence.
What does each verdict mean?
- Removed. The page names code that was in the product and is now gone from every repo checked. The row shows the commit that added it, the commit that removed it, and the first tag after the removal.
- Not found in {repos} history since {date}. The page names code that never appeared in the product code of any repo checked, as far back as each repo's history goes.
- Moved to another repo. The name was removed from one repo and lives in another today. The page is not wrong about the product, but its links and paths may point at the old place. It is never a candidate to remove.
- Stale. The thing still exists, but something the page says about it changed, for example a renamed setting.
- Partially true. Some of what the page describes is gone and some is still in the code.
- Keep. Enough of what the page says still matches the code today.
- Historical record. A dated record of the past, like a changelog or a decision record. Later changes do not make it wrong.
- Cannot tell. Too little could be checked to say. Open the page in the report to see which names were searched.
- Out of scope. The page is about process, policy or people, not code.
Does "Not found" mean it was never built?
Not always. Not found means the name never showed up in the product code of the repos checked, since the date each repo’s history starts. If code was squashed into one commit, imported from another repo, or lives in a repo you did not tick, it can be real and still not found. That is why the verdict always names the repos and the dates, and never says “never built”.
Why check several repos?
A page describes the product, not one repo. If a name is gone from your API repo but lives in your web app, the page is not wrong. So a page is marked Removed or Not found only when the name is gone from every repo checked.
A repo that could not be searched (too large, or could not be copied) blocks Removed and Not found for every page, and a name left unsearched when time ran out blocks them for that name. The report says why. A repo you untick is named in the verdict, for example “(acme/infra not checked)”.
Why are some pages "Cannot tell"?
Only a name that reads as code can prove something is gone: a name in backticks, a file path, a setting key or a URL. A page that only uses product words, like “Slack” or “CSV export”, cannot be proven gone, because the code may call the feature something else. Those pages read Cannot tell, which is an honest answer, not a failure.
What does it never do?
Cleanup never edits, archives, deletes or maps a page on its own. It only reports. You decide what happens to each page.
From a row you can Ignore it (with a reason), Mark reviewed (with what you did), or Watch and map it, which goes through the normal mapping step and your plan’s page limit, like mapping from the Pages tab. Watching a page hands it to the daily checks.
What does it cost?
A cleanup spends credits, like generating docs from scratch. Before it starts you see an estimate: a line for the pages and a line for each repo. Credits are held when you start and the part a cleanup does not use is refunded when it ends. Searching code and history happens on our side and costs no credits. See Billing & plans for credit packs.
A cleanup that reaches your team’s daily model budget pauses and picks up after the daily reset. The team owner or the person who started it can pause, resume or cancel it; a cancel refunds the unspent credits. Watching a page afterwards, and the daily checks that follow, cost no credits.
What is stored, and can I share the report?
Each repo is copied to a temporary folder on our server, one at a time, for the length of its search, and deleted right after. The report keeps references only (repo, commit, file path, tag), never page text or code. Each claim’s short paraphrase is stored encrypted.
Export gives a CSV or a Markdown file of what the report’s filters show, with links to each page and each commit, so a teammate without an Amendary seat can act on it. Claim paraphrases are left out unless you ask for them.
Try Amendary on your own docs
Connect GitHub and the docs you already keep in Notion or GitHub. During setup you can replay a recent release against your help pages to see what Amendary would draft, with its evidence.
Free for 7 days, no card. Every edit waits for your review unless an owner turns on auto mode. Code is never touched.