What is PR Enrichment?
Last updated
PR enrichment is the process of augmenting a pull request with context beyond the raw diff, such as architectural diagrams, dependency maps, risk assessments, and scenario analysis, so that reviewers have the information they need without manually tracing code paths.
Why does PR enrichment matter for engineering teams?
A typical PR shows you what changed, not what it affects. Reviewers end up tracing dependencies and call chains by hand before they can judge the change. PR enrichment gathers some of that context up front, so reviewers start with a map instead of drawing one.
How does Argus handle PR enrichment?
After posting its review, Argus appends an 'Also in this PR' list and up to two Mermaid diagrams (sequence, data flow, or dependency) to the PR description. A diagram may only use the changed files as nodes and code-graph edges between them; a validator drops any diagram with an edge the graph does not contain. Nothing outside the diff is drawn, and the description gets no blast-radius score or risk rating. Diagrams appear only when the Mermaid validator is configured: MERMAID_VALIDATOR_BASE_URL on the backend, and the same MERMAID_VALIDATOR_SECRET on the backend and the web app.