blast-radius

Analyze a pull request's impact surface and generate a verification checklist.

1|1|Updated Feb 25, 2026

Search Tags:#testing #code review #impact analysis #risk assessment #pr #blast radius

One-click install

npx skills add https://github.com/teambrilliant/tap-skills --skill blast-radius-teambrilliant

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: blast-radius
Source: https://github.com/teambrilliant/tap-skills/tree/main/skills/blast-radius
Command: npx skills add https://github.com/teambrilliant/tap-skills --skill blast-radius-teambrilliant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps human reviewers understand the potential consequences of merging a Pull Request, reducing the risk of introducing regressions or unexpected side effects.

Core Features & Use Cases

Impact Analysis: Identifies files, functions, and components affected by a PR.
Risk Assessment: Assigns a risk level (Low, Medium, High) to the changes.
Verification Checklist: Generates a targeted list of items for manual testing.
Use Case: Before merging a complex feature PR, use this Skill to get a clear picture of what might break and what specific areas need thorough manual testing.

Quick Start

Analyze the impact of the current branch's changes against main.

Frequently Asked Questions about blast-radius

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

FAQPage Schema

How do I assess the impact of a pull request before merging?▼

How do I analyze the blast radius of code changes?

How do I generate a manual verification checklist for a PR?▼

How do I generate a manual verification checklist for a PR?

What is the best way to map PR risk for a mixed human-agent development team?▼

What is the best way to map PR risk for a mixed human-agent development team?

Can I assign a risk level to unmerged code changes?▼

Can I assign a risk level to unmerged code changes?

When do I need a structured impact analysis for code review?▼

You need a structured impact analysis for code review when evaluating complex feature pull requests. It provides a clear picture of what might break, reducing the risk of introducing unexpected side effects or regressions.