code-review

Analyze diffs against the base branch for bugs, security, and compliance issues.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/norbert-pap/claudebert --skill code-review-norbert-pap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/norbert-pap/claudebert/tree/main/code-review
Command: npx skills add https://github.com/norbert-pap/claudebert --skill code-review-norbert-pap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing code review analyzes diffs against the base branch to surface bugs, edge cases, CLAUDE.md compliance issues, security vulnerabilities, and structural problems before merging.

Core Features & Use Cases

  • Diff analysis for pre-merge quality checks
  • Auto-fix suggestions following the Fix-First approach
  • Design review for frontend changes and structural issues
  • Clear, decision-ready outputs to guide PR outcomes

Quick Start

Provide the PR diff to the skill and ask it to surface findings and recommended fixes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for a PR diff before merging?

To automate pre-landing code review, you provide the PR diff to the skill for analysis against the base branch. It surfaces bugs, edge cases, security vulnerabilities, and architectural flaws before merging.

Can I automatically fix security vulnerabilities and bugs found during a code review?

Yes, the code review process prioritizes AUTO-FIX items when safe, suggesting fixes following a Fix-First approach. It outputs structured findings to guide your decision-making and recommended fixes.

What does pre-landing code review check for in frontend and backend changes?

Pre-landing code review enforces a five-axis evaluation covering Correctness, Readability, Architecture, Security, and Performance. It analyzes diffs to surface compliance issues, structural problems, and edge cases.

How do I check my code changes for architectural flaws and edge cases?

You can check your code changes by providing the diff to the skill and asking it to review your modifications. It evaluates the diff against the base branch to surface architectural flaws and edge cases.

Does this code review skill work with both frontend and backend pull requests?

Yes, the code review skill is applicable to PRs across both frontend and backend changes. It performs diff analysis and design review for structural issues regardless of the application layer.

What are the limitations of automated pre-landing code review?

Automated pre-landing code review outputs structured findings and auto-fix suggestions to guide decision-making, but still requires human judgment to evaluate the final PR outcome and validate architectural context.