JavaScript
TypeScript
Python
React
Next.js
GitHub
npm
pipDiagnose
Finds what’s actually wrong, with evidence.
- ↗Broken imports
- ↗Dead files
- ↗Hardcoded secrets
- ↗Weak tests
DiagnosisEvidenceConfidenceSafe RepairVerification
Your codebase has symptoms. Repo Doctor finds the cause.
Repo Doctor examines messy repositories, explains what is wrong, and safely repairs maintainability issues one treatment at a time.
Health record
example-app
main0/100
Health ScoreAwaiting scan
Run an examination to populate this record
1
Critical
4
Warnings
3
Safe Treatments
Active diagnosesAwaiting scan
Hardcoded API key in config.js
High confidence17 imports resolve to missing files
High confidenceTest coverage dropped in auth flow
Medium confidenceWorks with the stack you already use.
JavaScriptTypeScriptPythonReactNext.jsGitHubnpmpip
Clinical approach
Not just another AI code reviewer.
Explain
Shows why it matters, in plain language.
- ↗Severity
- ↗Confidence
- ↗Affected files
- ↗Root cause
Repair
Fixes one issue at a time, safely.
- ↗Isolated working copy
- ↗Readable diff
- ↗Your approval required
- ↗Full verification
0
Treatment applied at a time
0%
Changes require your approval
0
Files touched without a diff shown first
Isolated
Every repair runs in a working copy, never the original
01
Intake
Provide a GitHub URL or ZIP upload. We map the repo structure, detect languages and frameworks.
02
Examination
Deterministic scanners check imports, secrets, tests, and structure first — before any AI runs.
03
Diagnosis
AI explains findings, estimates confidence and risk, and prioritizes what matters most.
04
Treatment
You review the proposed fix and diff, approve it, and Repo Doctor verifies tests still pass.
Sample health record
Evidence before intervention.
DIAGNOSIS / RD-018
Hardcoded API key in config.js
CRITICALHigh confidence
AFFECTED FILES
- config.js :12
- .env.example :3
EVIDENCE
A credential-shaped value is committed directly in a runtime configuration file and is reachable by the application.
WHY IT MATTERS
Secrets committed to source control can be copied into forks, logs, and build artifacts. Rotate the key and move it into a local environment variable.
Verification record
Show the difference.
BEFORE
0
Health Score
AFTER
0
Health Score
Built for the handoff
When the repo is unfamiliar.
Hackathon builders
“The demo is tomorrow and the project has three different entry points.”
Junior developers
“I can see the warnings, but I need help understanding which one to fix first.”
Solo founders
“My product works — now I need the code to survive the next feature.”
Open-source maintainers
“The issue queue grows faster than I can map unfamiliar contributions.”
Inherited teams
“We need a safe first pass through a repository nobody on the team wrote.”
How it compares
RepoDoctor VS Everyone Else
A practical view of how different review approaches support diagnosis, repair, and verification.
| Capability | Repo Doctor | Generic AI Code Reviewer | Manual Review |
|---|---|---|---|
| Finds issues with evidence, not just opinion | Yes | Partial | Yes |
| Explains confidence/severity per issue | Yes | Yes | No |
| Fixes issues one at a time with your approval | Yes | Partial | Yes |
| Runs in an isolated working copy (never touches original repo directly) | Yes | No | No |
| Re-verifies tests after each fix | Yes | Partial | Partial |
| Requires no setup beyond a repo URL | Yes | Partial | No |
Scroll horizontally to compare columns on smaller screens.
FAQ
Answers before you examine.
Security & privacy
Repo Doctor never modifies your original repository. Every treatment runs in an isolated working copy, and nothing is applied without your explicit approval.