Argus
  • Features
  • Memory
  • Pricing
  • Compare
  • Changelog
  • Docs
Home/Glossary

Code Review Glossary

In-depth explanations of the concepts that power modern code review — from institutional memory to failure scenario simulation. Each term includes why it matters and how Argus implements it.

Code Review Automation

Code review automation is the use of software tools to automatically analyze, evaluate, and provide feedback on source code changes — typica…

Institutional Memory

Institutional memory in code review is the accumulated knowledge of a codebase's past decisions, incidents, patterns, and architectural cons…

PR Enrichment

PR enrichment is the process of augmenting a pull request with additional context beyond the raw diff — including architectural diagrams, de…

Code Simulation

Code simulation is the analysis technique of reasoning about what happens when code changes are executed in specific scenarios — such as inc…

Architecture Tracing

Architecture tracing is the analysis of how code changes propagate through a system's dependency graph — identifying which modules, services…

Dependency Graph

A dependency graph is a directed graph representing the import and call relationships between modules in a codebase. Nodes are files, module…

Pattern Learning

Pattern learning in code review is the ability of a review system to identify recurring code patterns, anti-patterns, and codebase-specific …

Static Analysis

Static analysis is the examination of source code without executing it, using rule-based pattern matching to detect known issues like securi…

Blast Radius

Blast radius is a measure of how far the impact of a code change propagates through a system — how many modules, services, endpoints, and da…

SAST (Static Application Security Testing)

SAST is a category of security testing that analyzes source code, bytecode, or binaries for security vulnerabilities without executing the a…

Tech Debt Tracking

Tech debt tracking is the systematic identification, quantification, and monitoring of accumulated technical debt in a codebase — areas wher…

Failure Scenario Testing

Failure scenario testing is the practice of analyzing code changes by reasoning about what happens under adverse conditions — network timeou…

Cross-PR Analysis

Cross-PR analysis is the practice of evaluating how multiple open or recent pull requests interact with each other — detecting conflicting c…

Review Fatigue

Review fatigue is the decline in review quality that occurs when reviewers are overloaded with review requests — leading to rubber-stamp app…