Requests — codebase analysis | Verifii

Requests

37 files &middot;<br>765 findings &middot;<br>analysed 9 days ago

Ask anything about this codebase

Every answer is grounded in the extracted findings and cites file and line.

e.g.

How does session authentication work?<br>How are redirects followed and what are the limits?

Ask

Agent views — choose your perspective

🏢

Management<br>Executive summary — capabilities, risks, spec coverage

Ready

&rarr;

📋

Product Owner<br>Feature inventory, spec alignment, behavioural gaps

Ready

&rarr;

Engineer<br>Implementation detail, patterns, dependencies, gotchas

Ready

&rarr;

🏗

Architect<br>Coupling, patterns, Zones of Pain, refactoring priorities

Ready

&rarr;

🔒

Security<br>Verified security findings — no false positives

Ready

&rarr;

🧪

Tester<br>Untested behaviours, edge cases, test gap inventory

Ready

&rarr;

Documentation & tools

Product overview

What this product does, in plain English — no code knowledge needed

&rarr;

Engineer view

File-by-file structural breakdown with dependencies

&rarr;

Spec vs Reality

What the spec promised vs what the code actually delivers — gaps, undocumented behaviors, and risk flags. Every finding grounded in file:line evidence.

&rarr;

Full site

Complete MkDocs documentation

&rarr;

Intent document

● Auto-detected — using the project README. Paste your PRD or spec to override.

Set spec document

Paste your spec, PRD, or requirements

Or upload a file (.md .txt .rst)

Save & regenerate Spec vs Reality