code-review

Review code diffs for behavioral regressions, security risks, and maintenance concerns.

2|Updated May 18, 2022
One-click install
npx skills add https://github.com/alexfalkowski/bin --skill code-review-alexfalkowski
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/alexfalkowski/bin/tree/main/skills/code-review
Command: npx skills add https://github.com/alexfalkowski/bin --skill code-review-alexfalkowski

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the inconsistency and lack of rigor in manual code reviews by enforcing an evidence-based, skeptical approach that prioritizes behavioral risks over subjective style preferences.

Core Features & Use Cases

  • Risk-Focused Analysis: Automatically prioritizes bugs, regressions, and security vulnerabilities over stylistic nits.
  • Evidence-Backed Findings: Requires all feedback to be grounded in concrete code changes, test coverage, or documented contracts.
  • Use Case: Use this during a pull request review to identify silent behavior changes, missing test coverage, or documentation gaps that might otherwise be missed by human reviewers.

Quick Start

Use the code-review skill to analyze the current diff for behavioral risks and documentation gaps.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform an evidence-based code review on a pull request?

An evidence-based code review analyzes pull requests by grounding all feedback in concrete code changes and test coverage to identify behavioral regressions and security risks. It prioritizes documented contracts over subjective style preferences.

What is the best way to find behavioral regressions in a branch diff?

To find behavioral regressions in a branch diff, apply a skeptical, risk-focused analysis that cross-references code changes against existing test coverage and project documentation to catch silent behavior changes.

How does a security audit work during code review?

A security audit during code review works by rigorously examining software changes to detect security vulnerabilities and maintenance concerns, requiring feedback to be backed by verifiable evidence from the diff.

Can I use automated code review for various programming languages?

Yes, you can use automated code review across various programming languages. It evaluates pull requests and branch comparisons by focusing on severity, confidence, and actionable formatting rather than language-specific styling.

When do I need an automated code review instead of manual checks?

You need an automated code review when manual checks lack consistency and rigor, especially to enforce strict adherence to severity standards and ensure verifiable feedback for high-quality PRs.

Why does my code review miss silent behavior changes in diffs?

Code reviews miss silent behavior changes when they focus on stylistic nits instead of evidence-backed analysis. Prioritizing behavioral risks and documentation gaps ensures these regressions are identified.