Managing Repositories

This guide covers the lifecycle of a repository in Scrubby: getting it indexed, keeping it current, and removing it cleanly when you no longer need it.

Adding a repository

There are two paths to add a repo:

Through your AI editor

Once your editor is connected to Scrubby, ask it:

"Index this repo with Scrubby — it's owner/repo-name."

The agent calls scrubby_index with the repo name. Scrubby creates the record, pulls the code via the GitHub App (if installed) or your token, and runs the first index.

Through the dashboard

1. Go to scrubby.ai/dashboard/repositories.
2. Click Add repository.
3. Pick the repo from the list of GitHub repos you have access to.
4. The first index runs in the background; you’ll get an email when it’s done.

Either path is fine. Most users add their first repo from the editor and use the dashboard for batch additions later.

Re-indexing

Scrubby tracks new commits incrementally, so you rarely need to manually re-index. Trigger a manual re-index when:

• You’ve done a heavy restructure (large directory moves, language additions).
• You want fresh convention extraction after a refactor sprint.
• The dashboard shows the index is stale.

From your editor:

"Re-index this repo with Scrubby, incremental."

Or from the dashboard, click Re-index on the repository row. Re-indexes are rate-limited to once per minute per repo — see Rate Limits.

Checking index status

GET /v1/repositories/:id/index/status

Returns one of: queued, indexing, ready, failed. The dashboard shows the same state visually.

Removing a repository

From the dashboard’s repository row, click Remove. This:

• Deletes the repo’s domains, segments, conventions, and findings from Scrubby.
• Removes the repo from the indexed list.
• Does not uninstall the GitHub App — for that, go to GitHub’s installation settings.

Removal is immediate and irreversible. To re-add the repo later, you’ll need to re-index from scratch.

Multi-org repositories

Repositories can be associated with personal accounts or with organizations. The association is set when the repo is added; switching it later requires removing and re-adding. Org-owned repos count against the org’s seat-based quotas; personal repos count against your individual plan.

Best practices

• Index repos you actually want reviewed. PR reviews only run on indexed repos — an installed GitHub App without an index sits idle.
• Don’t re-index unless you need to. Routine indexing happens automatically as commits land.
• Keep names stable. Renaming a repo on GitHub does propagate, but during the propagation window PR reviews may fail. If you’re planning a rename, expect a short re-index after.

Troubleshooting

If indexing fails or hangs, see Indexing Stuck or Failing.