review-code

Reviewing code diffs before a pull request merge involves collecting file changes and applying dynamic perspective selection to identify correctness, security, and reliability issues. The output is a severity-ranked markdown document with actionable findings and positive notes.

Performing a security audit on a specific file diff requires applying targeted review perspectives to file-specific or glob-matched changes. This generates severity-classified findings that highlight security vulnerabilities and maintainability concerns in the modified code.

Automated code review can inspect staged, unstaged, untracked, file-specific, and glob-matched changes within a repository. It dynamically selects relevant review perspectives to evaluate the diff and saves a structured markdown review document.

Diff analysis classifies the severity of maintainability and performance issues by dynamically selecting review perspectives based on the code changes. It produces a prioritized markdown review with severity-ranked findings, positive notes, and action items.

Pre-merge quality checks on a code diff can include design-document reference scanning to ensure changes align with intended architecture. This reference scanning is part of producing a comprehensive, prioritized markdown review document.