Repository cleanup that ends with a pull request, not another report.
AI-assisted development makes software faster to create, but duplicate implementations, abandoned experiments, unused dependencies, and risky manual cleanup accumulate. RepoDiet turns that debt into bounded maintenance work the buyer can inspect before accepting.
The complete journey
From repository to buyer decision
Connect repository
Choose a public GitHub repository and branch. RepoDiet binds the run to the exact source commit.
Evidence
Repository, branch, source commit
Analyze
RepoDiet maps the project and finds duplicate code, unused files and dependencies, orphan modules, and protected paths.
Evidence
Prioritized, file-level findings
Review findings
You choose the maintenance work RepoDiet may perform. Findings that are unsafe to automate remain review-only.
Evidence
Buyer-selected cleanup scope
Agree cleanup scope
The job pins allowed changes, protected files, verification checks, repository state, and negotiated price.
Evidence
Bounded maintenance contract
Execute in isolation
RepoDiet applies only eligible, approved changes away from the main branch and rejects changes it cannot verify.
Evidence
Change manifest and check results
Create pull request
A real GitHub branch and pull request are opened against the selected base branch. RepoDiet never merges it automatically.
Evidence
Review-ready GitHub pull request
Review and accept
RepoDiet compares the result with the pinned source, checks scope and protected paths, and reports build and test outcomes.
Evidence
Verification result and receipt
Buyer decides
The buyer reviews the pull request and evidence before accepting delivery. The repository owner remains in control.
Evidence
Buyer decision and settlement evidence
A2MCP quick triage
Diagnose the repository
A fast paid analysis that returns up to five prioritized repository findings. Agents call analyze_repository when they need a bounded, repeatable diagnosis.
A2A verified cleanup PR
Deliver the maintenance job
A negotiated cleanup job in which RepoDiet performs the agreed work and delivers a pull request for buyer review. A2MCP diagnoses; A2A delivers.
Safety architecture
The buyer stays in control
RepoDiet does not push to the main branch or merge automatically. It binds work to a source commit, protects sensitive paths, limits changes to the agreed scope, and delivers through a reviewable branch.
Protected paths
Routes, configuration, environment files, lockfiles, and public assets are guarded by policy.
Isolated branch
Every delivered change is reviewable before it reaches the target branch.
Automated checks
Scope, patch application, protected paths, and available repository checks are evaluated.
Buyer decision
Delivery evidence supports the decision; it does not replace repository-owner review.
Who needs RepoDiet
Built for repository owners and their agents
- Solo builders using AI coding tools
- Agencies preparing client handoffs
- Startups moving toward production
- Engineering teams managing repository debt
- Non-technical owners who need reviewable delivery
- Buyer agents purchasing maintenance work
What you receive
- Prioritized, file-level findings
- A buyer-selected cleanup scope
- A changed-file and verification summary
- A real GitHub pull request
- Rollback information and delivery evidence when available
Planned directions include private repository support, broader language support, continuous repository-health monitoring, and advanced duplicate-system consolidation. These are roadmap items, not currently advertised as active functionality.