code-review-and-quality

Identify defects, risks, and quality gaps in code diffs.

1|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/mortenbroesby/playground --skill code-review-and-quality-mortenbroesby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/mortenbroesby/playground/tree/main/.skills/code-review-and-quality
Command: npx skills add https://github.com/mortenbroesby/playground --skill code-review-and-quality-mortenbroesby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams identify real defects and risk in code changes by evaluating correctness, readability, architecture, security, performance, and verification gaps.

Core Features & Use Cases

  • Structured evaluation of diffs to surface correctness issues, architectural concerns, and potential security or performance risks.
  • Prioritized reporting that ranks findings by severity and documents file references to facilitate quick remediation.
  • Coverage of common scenarios such as new features, refactors, and dependency updates, with guidance on test adequacy and potential regressions.

Quick Start

Provide the changes you want reviewed and the assistant will generate a structured quality assessment with prioritized findings.

Frequently Asked Questions about code-review-and-quality

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

FAQPage Schema
What does a structured code review cover beyond basic correctness?

A structured code review evaluates correctness, readability, architecture, security, performance, and verification gaps to identify real defects and risks in code changes.

How do I review code diffs before a merge to catch potential regressions?

To review code diffs before a merge, provide the changes to generate a structured quality assessment that prioritizes findings by severity and documents file references for quick remediation.

Can I use this approach to assess test adequacy for dependency updates and refactors?

Yes, you can assess test adequacy for dependency updates and refactors by evaluating the code changes to surface potential regressions and verification gaps.

What is the best way to prioritize findings during a code risk audit?

The best way to prioritize findings during a code risk audit is to rank them by severity, documenting specific file references to facilitate quick and targeted remediation of architectural and security concerns.

When do I need a comprehensive quality assessment for new features?

You need a comprehensive quality assessment for new features when you want to surface correctness issues, architectural concerns, and potential security or performance risks before merging code changes.