- Home
- Skills
- Technical Documentation
- Codebase Atlas
Codebase Atlas
Generate evidence-backed architecture diagrams and code walkthroughs to map and document software repositories.
Free
Works with the AI Agents you already use
Codebase Atlas
Example session with this skill installed
Generate a workflow diagram for our user registration process in the services/auth directory and explain the main components.
- Read your context and instructions
- Compiled the codebase atlas
I have analyzed the services/auth directory and its related entry points. Based on the source code in registration.go, validator.go, and the user database schema, here is the registration workflow.
User Registration Workflow
This diagram traces a registration request from the API gateway through validation to persistence in the Postgres store.
graph TD
Client[Client Browser/App] -->|POST /api/register| Gateway[API Gateway]
Gateway -->|Forward Request| AuthSvc[Auth Service: registration.go]
AuthSvc -->|Validate Payload| Val[Validation Logic: validator.go]
Val -->|Check Complexity| PWD[Password Hasher: bcrypt]
AuthSvc -->|Check Duplicate| DB[(User Store: Postgres)]
AuthSvc -->|Write Record| DB
AuthSvc -->|Emit Event| EventBus[Redis Event Bus]
style AuthSvc fill:#f9f,stroke:#333,stroke-width:2px
style DB fill:#bbf,stroke:#333,stroke-width:2px
Component Responsibilities
Registration Logic (services/auth/registration.go): Orchestrates the flow, handles hashing, and manages the database transaction.
- Validation (
services/auth/validator.go): Enforces input constraints and sanitizes data before processing. - User Store (
db/schema.sql): Confirmed via migrations to use a unique constraint on the email field.
Event Bus: Inferred from the Close() method in pubsub.go, used for downstream notification of new user accounts.
Evidence & Assumptions
- CONFIRMED: Database writes and password hashing are directly visible in
registration.go.
INFERRED: The connection to Redis for the Event Bus is implied by the config/queue.yaml settings but the specific emitter call was not found in the primary registration path.
Next steps
- Review the
services/auth/registration.gofile to confirm the Redis emitter implementation. - I can save this diagram to
docs/architecture/registration_workflow.mdif you need persistent documentation. - Ask for a Deep Dive into the
Password Hasherif you need to see specific security parameters.
Connects securely to your tools. The creator never sees your data.
About this skill
Onboarding to a new codebase usually involves hours of reading imports and chasing function calls just to understand the data flow. This skill automates that discovery process, producing evidence-backed architecture diagrams and walkthroughs directly from your source.
What it does
- Visualizes Architecture: Generates Mermaid diagrams for systems, components, and workflows.
- Maps Workflows: Traces execution paths and call sequences across multiple files.
- Documents Databases: Creates entity relationship diagrams by inspecting schemas and migrations.
- Identifies Dependencies: Maps interactions between subsystems and external services.
- Maintains Documentation: Updates existing architecture files in
docs/architecture/with version tracking.
How it works
- Scope definition: The agent identifies the subsystem or workflow you want to visualize and selects an investigation depth.
- Static exploration: It inspects manifests, entry points, and configurations to build a conceptual map without running your code.
- Evidence collection: Every node and relationship is categorized as confirmed or inferred based on source code analysis.
- Diagram generation: The agent produces GitHub-compatible Mermaid code accompanied by a plain-language explanation and file citations.
Frameworks & tools
This skill is language-agnostic and works with any standard software repository. It thrives in environments with README.md files, standard manifests (e.g., package.json, go.mod, requirements.txt), and structured schemas.
Why this beats prompting it yourself
Generic prompts often hallucinate relationships based on file names or outdated documentation. This skill enforces a strict evidence-based procedure, distinguishing between confirmed source logic and inferred patterns while providing direct file references you can verify.
Use cases
- Map the data flow of a complex authentication or checkout workflow.
- Generate a high-level system overview for onboarding new developers.
- Visualize database relationships and foreign key constraints for a specific module.
- Create sequence diagrams to debug race conditions or interaction order.
Known limitations
Does not execute code, installation scripts, or migrations. Analysis is limited to static source code and available documentation. Verification is only as accurate as the accessible files.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.
Requires static access to source files. Cannot run scripts or migrations to determine runtime behavior. Accuracy depends on the clarity of code and manifests.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 7 days ago
- Free with an Agensi account
- Software
Node.js