Skip to content
Skills Library
Programming · Analysis

qstack-blast-radius

/qstack-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.

Repository
qstack ↗
Licence
MIT
Last repository change
18.10.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
0
URLs in SKILL.md
1
Deprecation

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

Licence

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

What it does and when to use it

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.

Triggers from the description

what could this break?
Original author description

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.

How it works

  1. Trace the risk
  2. Prove the critical fact
  3. Report
Original SKILL.md headings · 56 lines, 387 words
SKILL.md preview
---
name: qstack-blast-radius
description: >
  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.
license: MIT
---

# QStack blast radius

Find the breakage that a symbol search or diff review would miss. The result is
analysis, not permission to edit, commit, push, publish, deploy, or message
anyone.

## Trace the risk

1. Resolve the exact change from the user's files, diff, branch, or recent work.
   Read the surrounding implementation and repository instructions.
2. State the one critical fact the change is safe because of. Use a second fact
   only when the safety case truly has two independent hinges.
3. Follow effects beyond direct callers. Check pinned dependency source and
   local patches, lifecycle timing, persisted data, wire formats, other
   languages reading the same bytes, feature flags, generated artifacts, and
   downstream consumers. Cite real paths and lines. A search with no matches is
   evidence when its scope is stated.
4. Separate confirmed risks from cleared risks. For each confirmed risk, name
   the failure path, likelihood, impact, and cheapest decisive check.

## Prove the critical fact

Push each safety fact as far down this ladder as is practical:

1. A claim only.
2. Direct source evidence at a real path and line.
3. A traced bad case that cannot reach the failure.
4. A script or test that executes the real shipped code and fails loudly when
   the fact is false.
5. A reproduction in the running artifact.

Anything below level 4 remains **unproven**. Say where proof stopped. Do not
round a plausible writeup up to a verified conclusion. For analysis-only work,
use existing tests or inline, read-only probes. Creating even a temporary proof
file requires write authorization. If direct proof is not authorized, keep the
fact unproven. Do not mutate production or exercise a destructive path merely
to reach a higher proof level.

## Report

- What changed, including behavior the diff does not make obvious.
- The critical safety fact, its proof level, and the observed evidence.
- Confirmed risks, ordered by likely cost.
- Cleared risks and the evidence that cleared them.
- The cheapest pre-merge check that catches the meaningful failure.

When an approved QStack execution loop is already active, put durable evidence
in its existing `execution.md` as that loop permits. Create no competing record.
Remove private data before sharing any evidence outside its authorized scope.

Adapted from Lauren Tan's PStack
[`blast-radius`](https://github.com/cursor/plugins/blob/60c641e4fad674784b30abcf9f8915dea39df38d/pstack/skills/blast-radius/SKILL.md)
at commit `60c641e4fad674784b30abcf9f8915dea39df38d` under the MIT License.
See [third-party notices](../../THIRD_PARTY_NOTICES.md).
Files in this package (2)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB

Versions

The database has no other skills named qstack-blast-radius.

Database snapshot: 13.11.2026 · package version facc7f9540d2 (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

  • 100blast-radius
    Find what a change could break outside the diff and prove the one fact it is safe because of by running real code. Use for 'blast radius of X', 'what could this break', or a small diff you do not trust. Use how for what code does, why for motivation.
  • 90blast-radius
    Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for /blast-radius, 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.
  • 90blast-radius
    Trace what a proposed or actual code change could break beyond its diff, and test the facts its safety depends on. Use for "blast radius," "what could this break," or checking an existing-code assertion before designing against it.
  • 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.
  • 90blast-radius
    Find what a change could break somewhere else before it ships, beyond the diff, and prove 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', or reviewing a small diff you don't trust.
  • 90blast-radius
    Find what a change could break somewhere else before it ships, beyond the diff, and prove 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', or reviewing a small diff you don't trust.

Feedback and reports

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