80-20-review

Prioritize code review effort by scoring blast radius across .NET changes.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/shahdanish/vibepos --skill 80-20-review-shahdanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 80-20-review
Source: https://github.com/shahdanish/vibepos/tree/main/skills
Command: npx skills add https://github.com/shahdanish/vibepos --skill 80-20-review-shahdanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review code with limited time by concentrating effort on the smallest set of changes most likely to cause production failures, security incidents, or hard-to-debug behavior.

Core Features & Use Cases

  • Checkpoint-based review: self-review post-implementation, deeper pre-PR review, integration validation, and production-readiness checks.
  • Blast-radius guided depth: decide how long to review based on impact (critical/high/medium/low) rather than lines changed.
  • Critical-path focus: prioritizes data access, security, concurrency, external integrations, and message consumers, with a batch checklist for high-yield checks.
  • MCP-first workflow: suggests using project graph, diagnostics, antipattern detection, dead-code detection, dependency-cycle detection, and test coverage mapping before manual reading.

Quick Start

Use the 80-20-review skill to review a pull request by running the checkpoint checklist and focusing first on data access, auth boundaries, concurrency, and integration points.

Frequently Asked Questions about 80-20-review

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

FAQPage Schema
How do I prioritize code review for high-impact changes in a .NET pull request?

Prioritize code review by calculating a blast-radius score for each change to set review depth, focusing on data access, security, concurrency, and integration boundaries before reading line-by-line. This ensures the highest-risk defects are caught first.

What is blast-radius scoring and how does it guide PR checklist depth?

Blast-radius scoring assesses the potential impact of a change—critical, high, medium, or low—to determine how deeply you review. Critical-path changes to data access or concurrency receive deeper checks than low-impact modifications.

How do I review concurrency and data access issues before submitting a PR?

Run a pre-PR checkpoint checklist that batches critical checks for concurrency and data access boundaries. Use MCP-first diagnostics and antipattern detection to map test coverage and identify dead code before manual review.

Can I use this risk-based review approach for architecture and integration validation?

Yes, the checkpoint-based review supports architecture reviews and integration validation by focusing effort on external integrations and message consumers. It schedules self-review, deeper pre-PR review, and production-readiness checks.

What's the best way to reduce production defects when review time is limited?

The best way to reduce production defects with limited time is to concentrate review effort on the smallest set of changes most likely to cause failures. Apply a critical-path batch checklist targeting security, concurrency, and data access.

When should I not use a blast-radius guided code review?

You should not use blast-radius guided review when a pull request contains only low-impact changes with no data access, security, concurrency, or integration boundary modifications, as the scoring will not yield actionable prioritization.