Find the pages about things you removed or never built

• You pick up to 50 Notion pages, watched or not, and the repos to check them against. Every connected repo is ticked by default.
• Each page gets a verdict: a candidate to remove, needs a correction, moved to another repo, keep, a historical record, out of scope, or cannot tell.
• You can export the report as CSV or Markdown for teammates who do not use Amendary.
• Run it before you start watching pages: watch the ones worth keeping, and delete the candidates yourself.

1. The estimate comes first: a line for the pages and one for each repo. Nothing is read by a model until you start.
2. Amendary reads each page once and lists the names it uses for things in the code.
3. Each repo is copied to a temporary folder on our server, one at a time, searched (the code today and every commit in its history), then deleted.
4. Each page is judged with the evidence from every repo. A rule in code combines them: Removed or Not found only when the name is gone from every repo checked and every search finished.
5. The report shows each verdict with its evidence and links to GitHub at the commit.

• It never edits, archives, deletes or maps a page on its own. The only actions are yours: Watch and map, Ignore, or Mark reviewed.
• It never says “never built”. A Not found verdict names the repos checked and the date each one’s history starts, because squashed or imported history can hide real code.
• It never marks a page for removal from a plain product word. Only a name that reads as code (in backticks, a file path, a setting key, a URL) can prove something is gone.
• It never runs on a schedule and never adds anything to the Queue.

A Removed page shows the commit that added the name, the commit that removed it, and the first tag after the removal. A name that lives on in another repo turns the page into “Moved to another repo”, which is never a candidate to remove.

A repo that could not be searched (too large, or could not be copied) blocks Removed and Not found, and the report says why. The report keeps references only (repo, commit, file path, tag), never page text or code. What each verdict means is in the Cleanup help page.

• Up to 50 pages per cleanup, from Notion. Pages in a GitHub docs folder or wiki are not in the picker yet.
• A repo over 300 MB is skipped, and the repos of one cleanup can add up to 1 GB. At most 400 names are searched per cleanup.
• Searching takes at most 20 minutes per repo and 90 minutes per cleanup. A name left unsearched cannot prove an absence.
• A cleanup that reaches your daily model budget pauses and continues after the daily reset. The owner or the person who started it can pause, resume or cancel it.

A cleanup spends credits for reading the pages and judging them. Searching code and history happens on our side and costs no credits. Credits are held when you start and the unused part is refunded at the end. Watching a page afterwards, and the daily checks that follow, cost nothing extra. See Billing & plans.