CodeAtlas

Repository Understanding Workspace

Import Repository

View State

Dashboard Variants

Repository

codeatlas-platform

Branch

main

Languages

TypeScript · Go · SQL

Last Indexed

2 min ago

Status

Ready

Project Panorama

Repository Structure + Dependency Lens

Open Interactive Graph

Directory Tree

  • apps/web
  • services/api
  • packages/domain
  • infra/docker

Module Dependency Graph

3-Minute Understanding

Project Essentials

  • Purpose: Build unified engineering metrics and code insight APIs.
  • Core Modules: `auth`, `repo-indexer`, `insight-engine`, `reporting`.
  • Entrypoints: `apps/web/src/main.tsx`, `services/api/cmd/server/main.go`.

Run & Build Guide

First Run Steps

  1. Install dependencies: `npm install && go mod tidy`
  2. Start API: `go run ./cmd/server`
  3. Start Web: `npm run dev`

Risk Hotspots

Areas to Review First

  • services/api/handlers/order.go (high churn + complexity)
  • packages/domain/pricing.ts (dense logic, low tests)
  • apps/web/src/features/login/* (dependency fan-out)

Change Entry Suggestions

Where to Edit

  • Candidate 1: packages/domain/pricing.ts#L120-L220
  • Candidate 2: services/api/handlers/checkout.go#L45-L93
  • Suggested tests: pricing.spec.ts, checkout_handler_test.go

AI Q&A

Ask about architecture or implementation

Answer Snapshot

Order status transition is handled in the service layer and triggered by checkout completion events.

Evidence: services/api/handlers/order.go · handleStatusTransition() · line 78