Doctor Dev

A repository can pass its existing tests and still be fragile. Important error and authorization paths may have no test evidence, while environment variables, Docker settings, CI, runtime versions, ports, and README instructions can disagree. Developers often discover these gaps only during onboarding, review, or deployment because each tool checks a different piece of the system. Doctor Dev gives developers one place to inspect those connected risks. Enter a public GitHub URL or an allowed local repository path and start a read-only scan. The app profiles the stack and files, then runs two diagnostic engines. TestPilot maps tests to source code and API routes, highlights missing or incomplete behavior checks, and can produce starter test skeletons. ConfigDoctor compares code, environment templates, containers, CI, runtime metadata, and documentation to find inconsistencies. The dashboard groups findings by severity and confidence, shows the supporting file evidence, and recommends a specific next step. It also provides a health score and downloadable Markdown and JSON reports. The distinction is evidence quality. Doctor Dev uses an actual coverage percentage only when it finds a supported coverage artifact. Otherwise it labels the result as evidence based or unavailable instead of inventing a percentage. Its included demo repository contains deliberate testing and configuration gaps for a repeatable walkthrough, while the same analysis pipeline also accepts other repositories. It is designed for maintainers, reviewers, and new contributors who need to decide what to fix before a release or handoff. The prototype currently has its deepest analysis for JavaScript and TypeScript, with an initial Python adapter. Generated tests are starting points for developer review.