registry-code-review

Review Registry Research Toolkit pull requests for logic and data-safety issues.

2|Updated Mar 20, 2026

Search Tags:#workflow #quality assurance #code review #pull request #registry #microdata

Ready to run

npx skills add https://github.com/adamaltmejd/registry-research-toolkit --skill registry-code-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: registry-code-review
Source: https://github.com/adamaltmejd/registry-research-toolkit/tree/main/.agents/skills/registry-code-review
Command: npx skills add https://github.com/adamaltmejd/registry-research-toolkit --skill registry-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, independent review workflow for Registry Research Toolkit pull requests, ensuring code quality and architectural consistency without manual oversight.

Core Features & Use Cases

Independent Review: Executes a diagnostic checklist in a subagent environment to ensure reviews remain decoupled from the authoring session.
Material Risk Assessment: Focuses on logic bugs, contract violations, and data-safety risks specific to Swedish registry microdata.
Use Case: Use this when a pull request is submitted to the repository to automatically generate a report identifying blocking issues, non-blocking improvements, and potential test gaps.

Quick Start

Use the registry-code-review skill to perform an independent review of the pull request number 123.

Frequently Asked Questions about registry-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I perform an automated code review for Swedish registry microdata pull requests?▼

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.

Do I need GitHub CLI access to review pull requests in the Registry Research Toolkit?▼

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.

What does an independent code review workflow check for in a pull request?▼

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.

Can I use this code review process to identify potential test gaps in my pull request?▼

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.

What are the limitations of automated code review for registry microdata?▼

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.

What is the best way to ensure code quality and architectural consistency in Registry Research Toolkit pull requests?▼

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.