80-20-review

Prioritize code review effort on high-impact changes using blast-radius scoring.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Maj3D10/Training-Platform --skill 80-20-review-maj3d10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 80-20-review
Source: https://github.com/Maj3D10/Training-Platform/tree/main/.agent/skills/80-20-review
Command: npx skills add https://github.com/Maj3D10/Training-Platform --skill 80-20-review-maj3d10

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you use limited review time effectively by concentrating on the small portion of a codebase that most often drives production incidents, security failures, and integration breakdowns.

Core Features & Use Cases

  • Checkpoint-based review scheduling: Review at natural stages (post-implementation, pre-PR, post-integration, post-deploy) with different depth and focus per stage.
  • Risk-driven focus using blast radius: Allocate review effort based on how widely a change affects the system, prioritizing data access, security, concurrency, and integration boundaries.
  • Repeatable review checklists and workflows: Apply targeted checks such as SQL injection risk, auth gaps, N+1 queries, cancellation propagation, exception handling, and resource leaks, with guidance for MCP-assisted triage.
  • Critical path identification: Systematically find high-risk areas (EF/DbContext usage, authorization handlers, external service calls, shared state, message consumers) and downscope low-risk code (DTOs, straightforward wiring, configuration binding).

Quick Start

Use the 80-20-review skill while reviewing your .NET pull request or architecture change, especially when you want to know what to inspect first for security, data access correctness, concurrency safety, and integration risk.

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 security and concurrency risks in a pull request?

Prioritize code review by scoring the blast radius of changes to concentrate effort on data access, security, concurrency, and integration boundaries that most frequently cause production incidents.

What is blast radius scoring in software risk management?

Blast radius scoring measures how widely a code change affects the system, allocating review effort to high-impact areas like EF Core DbContext usage, authorization handlers, and external service calls.

How do I review EF Core data access for N+1 queries and SQL injection risks?

Apply targeted review checklists to EF Core data access to verify SQL injection risk, detect N+1 queries, and ensure correct DbContext usage during risk-focused audits and pull request reviews.

When do I need checkpoint-based code review scheduling?

Use checkpoint-based review scheduling at natural stages—post-implementation, pre-PR, post-integration, and post-deploy—to apply different review depth and focus per stage for effective risk coverage.

Can I use this code review approach for architecture decisions and risk audits?

Yes, this risk-driven review approach applies to architecture decisions and risk-focused audits by systematically identifying critical paths and downscoping low-risk code like DTOs and configuration binding.

What code review checks should I perform for concurrency and cancellation propagation?

Perform targeted checks for concurrency safety, cancellation propagation, exception handling, and resource leaks on shared state and message consumers to prevent production failures.