GitHub only
Architecture review of an unfamiliar codebase
Ask Devin where a multi-tenant change to Cal.com would break, and it answers with an architecture diagram and a risk list that cite the code, without writing any code itself.
Steps
- Open app.devin.ai. No repo copy needed, since Cal.com is public.
- Optional: open DeepWiki for cal.com in another tab to compare.
- Start a session and paste the prompt below.
Prompt
Act as an architecture consultant on an unfamiliar large codebase: https://github.com/calcom/cal.com (use DeepWiki / Ask Devin and read the code; do not write code). Question: we want to make Cal.com fully multi-tenant (hard isolation between organizations sharing one deployment). Where would this change break? Deliver: (1) a Mermaid architecture diagram of the request → auth → data path, (2) a ranked risk list (data model, auth/session, caching, background jobs, webhooks, integrations/credentials, billing, search) where every claim cites file paths, (3) the smallest safe first milestone and how to test it. Clearly separate what you verified in code from what you infer.
What to watch
- Click a few citations and check that they point at real files.
- Facts it verified in the code are kept separate from its inferences.
You're done when
- You have a Mermaid diagram of request → auth → data.
- You have a ranked risk list where every item cites a file path.
- It proposes a small first milestone you could actually ship.
Go further
Run the same prompt against a repo from your own company.