code-review

Identify defects, regressions, risks, and missing tests in code changes.

3|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/aleen42/PersonalContext --skill code-review-aleen42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/aleen42/PersonalContext/tree/main/skills/code-review
Command: npx skills add https://github.com/aleen42/PersonalContext --skill code-review-aleen42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps identify defects, regressions, and risk introduced by code changes, surfacing concrete, actionable findings rather than generic summaries.

Core Features & Use Cases

  • Prioritized findings: correctness issues, regressions, risky assumptions, and missing tests.
  • Scope-aware reviews: focused on changed code, diffs, and likely runtime impact.
  • Explainability: clear rationale for each finding and how to reproduce.

Quick Start

Review the latest commit or diff and provide a focused set of concrete findings.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I identify regressions and bugs in a pull request diff?

A code review identifies defects and regressions in a pull request by analyzing the diff for correctness issues, risky assumptions, and missing tests. It provides concrete, actionable findings with clear rationale and reproduction steps rather than generic summaries.

What is the best way to check a commit for missing tests?

Checking a commit for missing tests involves a scope-aware review that evaluates test coverage against the changed code and its likely runtime impact. This surfaces concrete findings with clear rationale for each identified gap in the diff.

Does structured code review find risky assumptions in branch changes?

Yes, structured code review finds risky assumptions in branch changes by applying a workflow that emphasizes correctness and risk assessment. It analyzes the diff to surface prioritized findings regarding risky assumptions and their potential runtime impact.

Can I review code changes without receiving implementation proposals?

Yes, you can review code changes without receiving implementation proposals. The review workflow focuses exclusively on surfacing defects, regressions, risks, and missing tests without proposing implementation unless explicitly requested.

How to ensure correctness when reviewing diffs across software projects?

To ensure correctness when reviewing diffs across software projects, apply a structured workflow that emphasizes correctness, risk assessment, and test coverage. This method surfaces concrete, actionable findings scoped to the changed code.