code-reviewer

Identify defects, security risks, and edge-case gaps in code changes.

20|4|Updated Nov 10, 2025

Search Tags:#git #testing #architecture #security #quality #code-review

Ready to run

npx skills add https://github.com/MinBZK/regelrecht-mvp --skill code-reviewer-minbzk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/MinBZK/regelrecht-mvp/tree/main/.claude/skills/code-reviewer
Command: npx skills add https://github.com/MinBZK/regelrecht-mvp --skill code-reviewer-minbzk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a rigorous, skeptical code review process to catch edge cases, security gaps, and architectural issues before changes are merged.

Core Features & Use Cases

Context-driven review: Analyze diffs and read entire files to understand intent
Quality and security checks: Identify error handling gaps, boundary conditions, and potential vulnerabilities
Architectural feedback: Assess separation of concerns, coupling, and testing adequacy

Quick Start

Review the latest changes by inspecting the diff with git diff HEAD~1 and then run the recommended tests and checks before merging.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema

How do I review code changes for security vulnerabilities and edge cases?▼

Code review identifies security gaps, boundary-condition errors, and missing error handling by reading diffs and entire files to trace data flow. This catches vulnerabilities before merge, ensuring production-ready changes.

What should I check when reviewing pull requests across different languages and frameworks?▼

Thorough pull request review spans file-by-file inspection, architectural assessment, separation of concerns, test adequacy, and error handling evaluation. Apply these checks consistently regardless of language or framework to validate quality and security.

Can code review catch architectural issues before merging?▼

Yes. Architectural review assesses coupling, separation of concerns, and design patterns during pre-merge validation. This prevents structural debt and ensures changes align with system design before they ship.

How do I validate code quality and testing adequacy in a pull request?▼

Pre-merge validation examines error handling gaps, boundary conditions, test coverage, and production readiness through systematic file reading and data-flow analysis. This ensures changes meet quality standards before integration.

What's the best way to catch defects early in the development process?▼

Skeptical code review before shipping applies rigorous checks to diffs and staged changes, identifying defects and edge-case gaps through context-driven analysis. Early detection prevents issues from reaching production.

Do I need to review code from git staged changes or only pull requests?▼

Code review applies to pull requests, diffs, and staged changes across all languages and frameworks. This flexibility enables validation at multiple points in the workflow, from local changes through merge gates.