registry-code-review

Automated code review for Swedish registry microdata pull requests evaluates logic correctness, architectural standards, and data-safety risks. It fetches PR metadata and diffs using GitHub CLI to generate a diagnostic report identifying blocking issues, non-blocking improvements, and test gaps.

GitHub CLI access is required to review pull requests in the Registry Research Toolkit. The workflow depends on the CLI to fetch PR metadata and diffs, which are then analyzed against data-safety requirements and architectural standards for Swedish registry microdata.

An independent code review workflow checks pull requests for logic bugs, contract violations, and material data-safety risks. It operates in a decoupled subagent environment to ensure reviews remain unbiased and produce reports separating blocking issues from non-blocking improvements.

You can use this process to identify potential test gaps in your pull request. The diagnostic checklist evaluates logic correctness and architectural consistency, automatically generating a report that highlights missing tests alongside blocking issues and non-blocking improvements.

Automated code review for registry microdata is limited to evaluating architectural standards, data-safety requirements, and logic correctness. It focuses on material risk assessment rather than manual oversight, and requires GitHub CLI access to fetch the necessary pull request diffs.

The best way to ensure code quality and architectural consistency in Registry Research Toolkit pull requests is using a standardized, independent review workflow. It decouples the review from the authoring session and evaluates code against data-safety requirements specific to Swedish registry microdata.