80-20-review

Prioritize code review effort using blast radius scoring and checkpoint scheduling.

224|87|Updated Dec 15, 2018
One-click install
npx skills add https://github.com/Resgrid/Core --skill 80-20-review-resgrid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 80-20-review
Source: https://github.com/Resgrid/Core/tree/main/.opencode/skills/80-20-review
Command: npx skills add https://github.com/Resgrid/Core --skill 80-20-review-resgrid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps engineers and reviewers focus their limited time on the small portion of code changes that most often cause production incidents, so reviews are faster without becoming shallow.

Core Features & Use Cases

  • Checkpoint-based review: Schedules self-review, pre-PR, post-integration, and post-deploy checks with the right focus and depth at each stage.
  • Risk-driven priorities: Uses blast radius scoring to decide how thoroughly to inspect changes, especially around shared and cross-cutting areas.
  • Targeted critical path inspection: Emphasizes data access, security, concurrency, external integrations, and message consumers while offering guidance on what can be glanced or skipped.
  • Consistent review safety checklist: Provides a repeatable batch checklist for common high-impact failure modes in .NET code.

Quick Start

Load this skill while reviewing a pull request to prioritize security, data access, concurrency, and integration boundaries based on blast radius and checkpoint timing.

Frequently Asked Questions about 80-20-review

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

FAQPage Schema
How do I focus code review on the riskiest changes in a pull request?

Focus code review by calculating blast radius scoring to prioritize data access, security, and concurrency boundaries, ensuring the riskiest 20% of changes are deeply reviewed while others are glanced or skipped.

What is blast radius scoring in PR review workflows?

Blast radius scoring is a risk-driven prioritization mechanism that evaluates how thoroughly to inspect code changes based on their potential impact across shared and cross-cutting operational paths.

How do I schedule checkpoints for pre-PR and post-integration code reviews?

Schedule checkpoints by aligning self-review, pre-PR, post-integration, and post-deploy checks, applying the correct review focus and depth at each stage to catch high-impact failure modes.

Does this code review checklist support .NET integration testing and concurrency checks?

Yes, the batch checklist specifically targets common high-impact failure modes in .NET code, guiding critical path inspection across external integrations, message consumers, and concurrency boundaries.

When should I not use a risk-driven approach for code review?

Avoid risk-driven code review when evaluating non-production architectural changes or isolated paths with zero shared state, as blast radius scoring relies on identifying high-impact data access and cross-cutting boundaries.