agentleFS
nb-99nb-99/skillektion/skills/blast-radius/SKILL.md

blast-radius

Skill1 starsChanged 3 months agoMITView on GitHub

Analyze what a change could break beyond its diff and prove the central safety invariant with executable evidence. Use for impact analysis, risky small diffs, schema or API changes, and "what could this break?" questions.

111 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ketchup-video, principle-never-block-on-the-human and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • tristanphvnSkill

    ketchup-video

    Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.

    Also in 14 projects that use this

  • jaydubya818Skill

    principle-never-block-on-the-human

    Apply when safe reversible implementation details can proceed inside scope.

    Also in 44 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 29 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 20 projects that use this

  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 25 projects that use this

  • jaydubya818Skill

    principle-make-operations-idempotent

    Apply when an operation must tolerate retries after partial completion.

    Also in 46 projects that use this

  • +6 more from jaydubya818

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 106 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the diff, changed symbols, callers, tests, and the behavior that changed.

    line 27
  2. Distinctive:

    Keep temporary proof artifacts outside the repository, leave them uncommitted, and use disposable or non-production state for reproductions.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 106 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Blast Radius

Find the breakage that a symbol search misses. The output is useful only when the fact that makes the change safe is proven or explicitly marked unproven.

Confidence Ladder

For every safety-critical claim, record the strongest evidence reached:

  1. Assertion only.
  2. Direct source citation.
  3. Traced execution path showing the bad case cannot occur.
  4. Executed script or test against the real code.
  5. Reproduction in the running system.

Reach level 4 when it is reasonably cheap. Do not present lower-confidence claims as settled facts.

Process

  1. Read the diff, changed symbols, callers, tests, and the behavior that changed.
  2. State the one or two invariants on which the change's safety depends.
  3. Inspect runtime boundaries a local search can miss: pinned dependencies, serialized data, databases, APIs, feature flags, other languages, lifecycle ordering, concurrency, and downstream consumers.
  4. Inspect relevant commit, pull-request, issue, and design history when available. Distinguish historical evidence from inference.
  5. Trace each plausible failure from input to effect. Separate reachable risks from hypothetical ones.
  6. Prove the central invariant with the cheapest existing focused test, script, or running-system reproduction. Add a new check only when existing checks cannot exercise the real path. Keep temporary proof artifacts outside the repository, leave them uncommitted, and use disposable or non-production state for reproductions.
  7. For a genuinely broad change, use independent read-only review passes when available and verify their high-impact findings against the code.

Output

  • Change: behavior changed, including non-obvious effects.
  • Safety invariant: the decisive fact, confidence level, and evidence.
  • Confirmed risks: failure path, location, likelihood, impact, and check.
  • Cleared risks: what was investigated and why it is safe.
  • Before merge: the cheapest regression check that exercises the real path.
  • Gaps: unavailable evidence and every claim left unproven.

The analysis is complete when every material risk is confirmed, cleared, or named as an evidence gap, and the central safety invariant is proven or marked unproven.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.