repo-cartographer

To map repository architecture, apply an automated audit to your full-stack codebase to inventory frontend routes, backend services, external dependencies, and database tables. This generates a comprehensive markdown report summarizing the entire structure.

The best way to audit frontend routes and backend services is generating a comprehensive architecture map. This identifies integration points and environment state, eliminating guesswork by producing detailed markdown reports of your current codebase.

Yes, you can inventory database tables and external dependencies without modifying code. The mapping process reads your repository structure to list table totals and integration points, ensuring your source files remain untouched during the audit.

Codebase mapping for onboarding works by generating a current architecture map that covers App Router components, API routes, and library modules. This gives new engineers an up-to-date overview of route counts and integration points to accelerate orientation.

No, repository mapping requires no external dependencies or libraries to function. You can directly apply the skill to your full-stack codebase to generate markdown reports summarizing environment state and table totals.

A full-stack repository architecture audit includes a frontend map covering the App Router and components, a backend map of API routes and cron jobs, plus lists of external services, environment variables, and database table counts.