Skip to content
Skills Library
Programming · Review & audit

blast-radius

/blast-radius

Find what a code, schema, API, config, or behavior change could break beyond its visible diff, then prove the safety-critical assumption with real code. Use whenever the user asks what could break, requests a blast-radius review, or distrusts a deceptively small change.

Repository
skills ↗
Licence
MIT
Last repository change
24.08.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 24.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

Find what a code, schema, API, config, or behavior change could break beyond its visible diff, then prove the safety-critical assumption with real code. Use whenever the user asks what could break, requests a blast-radius review, or distrusts a deceptively small change.

Original author description

Find what a code, schema, API, config, or behavior change could break beyond its visible diff, then prove the safety-critical assumption with real code. Use whenever the user asks what could break, requests a blast-radius review, or distrusts a deceptively small change.

How it works

  1. Evidence ladder
  2. Tool availability
  3. Process
  4. Output contract
Original SKILL.md headings · 48 lines, 495 words
SKILL.md preview
---
name: blast-radius
description: Find what a code, schema, API, config, or behavior change could break beyond its visible diff, then prove the safety-critical assumption with real code. Use whenever the user asks what could break, requests a blast-radius review, or distrusts a deceptively small change.
---

# Blast radius

Find breakage a caller list will miss. The deliverable is not a convincing risk essay; it is the one safety-critical fact either proved against real behavior or marked unproven.

## Evidence ladder

For every fact the change's safety depends on, climb as far as practical and report where you stopped:

1. An unsupported assertion—never sufficient.
2. A concrete `file:line`, pinned dependency source, schema, or contract.
3. A traced bad case showing whether it can reach the changed behavior.
4. A script or test that calls the real code and fails loudly if the fact is false.
5. A reproduction through the running product.

Any safety fact below level 4 stays explicitly unproven.

## Tool availability

| Need | Preferred route | Fallback |
|---|---|---|
| Change and history | Local git diff/log plus an available source-control connector | Local repository only; name missing PR context |
| Downstream consumers | Code search, schemas, generated clients, migrations, pinned dependency source | Trace the reachable local chain and mark external consumers unknown |
| Runtime proof | Existing tests, verification harness, or a small deterministic script | Minimal isolated repro; if execution is impossible, stop at the evidence level reached |
| Independent review | Invoke `interrogate` when the user authorizes a multi-agent review | One lead-review pass; disclose the missing independent signal |

## Process

1. **Read the change.** Inspect the diff, changed symbols, deleted behavior, commits, and surrounding contracts. State what now behaves differently, including effects the diff does not spell out.
2. **Name the safety fact.** Find the one or two assumptions that collapse most scary cases if true. Spend effort here instead of producing a long speculative list.
3. **Look past symbol search.** Check pinned library behavior and local patches; event timing and teardown; serialized data, database columns, wire formats, other-language consumers, feature flags, jobs, caches, and code several hops downstream.
4. **Trace real risks.** For each candidate, show a reachable failure path, likelihood, cost, and a concrete check. A search that finds nothing is evidence when the search scope is stated.
5. **Prove the safety fact.** Prefer the smallest script or test importing the same code the product ships. Run it and retain output. Reproduce through the product when proportionate.
6. **Widen only when useful.** For a broad or high-risk change, suggest `interrogate`; do not launch agents unless current policy and user intent allow it.

## Output contract

- **What changed:** the visible and implicit behavior change.
- **Safety fact:** the assumption, evidence level reached, and proof output; otherwise `UNPROVEN`.
- **Risks:** only reachable risks, each with location, likelihood, impact, and check.
- **Cleared:** candidates investigated and why they do not reach.
- **Before merge:** the cheapest test or repro that catches the real failure.
- **Coverage gaps:** unavailable repositories, services, connectors, or runtime paths.

Use plain language, cite real code, and remove private material before public sharing.

<!-- Adapted from poteto/pstack blast-radius, MIT License, Lauren Tan, cursor/plugins@51a96e0. -->
Files in this package (2)
  • LICENSE 1 KB
  • SKILL.md 3 KB

Versions

RepositoryScoreLicence
This page · caezium/skills90MIT
rpraharaj/forward-deployed-engineer100MIT
Calvin-LLC/skills100MIT
Cimento-AI/agent-blast-radius100Apache-2.0
vahaah/astack100MIT
requie/endostack100MIT
OutlineDriven/outline-driven-development100Apache-2.0
pedrohcgs/claude-code-my-workflow100MIT
sma1lboy/rove90MIT

Database snapshot: 13.11.2026 · package version dd73be097804 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100prove-blast-radius
    Find what a change could break outside its diff, and prove the fact that makes it safe by running real code. Reports confirmed, open and cleared risks. Use when asked what a change could break, for a small diff you don't trust, or as Reviewer E of review-pr.
  • 100eng-blast-radius
    Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it is safe because of by running real code. Use when asked for the "blast radius of X" or "what could this break", or when reviewing a small diff you do not trust.
  • 90qstack-blast-radius
    Assess what a proposed or recent change could break beyond its direct diff, identify the critical safety fact, and prove it with real code or mark it unproven. Use for blast-radius analysis, "what could this break?", or a small change whose downstream effects are uncertain.
  • 90check-impact
    Finds what a change could break somewhere else before it ships, beyond the diff, and proves the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief…
  • 90check-blast-radius
    Find what a change could break outside the changed lines and prove the one failure with a repro or test. Use when the question is fallout beyond the diff; not for a multi-angle attack on the diff itself (use adversarial-review) or a routine review pass (use /review).
  • 100my-cabbages
    Toph's my cabbages, for finding who gets hit before a change ships. The cabbage merchant's cart gets wrecked in every chase scene, because nobody looks at who is standing nearby. Look first. Use for blast-radius, /blast-radius, "blast radius of X", "what could this break", "who…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.