agentleFS
Sign inStart free
sreejithramansreejithraman/SreeStack/skills/blast-radius/SKILL.md

blast-radius

Skill1 starsChanged 16 days agoMITView on GitHub

Assess a code change's blast radius beyond its diff. Use for subtle contract changes, migrations, or an explicit question about what else could break.

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

3 rules. 0 are common, 2 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Trace outward: Follow observable boundaries that can carry the change farther than a direct call: persisted data, wire formats, generated …

    line 11
  2. Distinctive:

    Name the safety assumptions: Write the smallest set of facts on which the change's safety depends and a concrete bad case if each fact is …

    line 12
  3. Very specific:

    When the task is a code review, return findings to its review owner.

    line 16

“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 consequential effects a symbol search could miss. Keep the investigation proportional to the changed contract and the cost of being wrong.

  1. Anchor the change. Identify the intended behavior, affected revision or diff, changed symbols and data shapes, and the relevant callers. Include uncommitted work when it is in scope. State any ambiguity in the change being assessed.
  2. Trace outward. Follow observable boundaries that can carry the change farther than a direct call: persisted data, wire formats, generated code, other languages, background jobs, lifecycle ordering, library behavior at the pinned version, and feature flags. Search only paths relevant to a plausible failure.
  3. Name the safety assumptions. Write the smallest set of facts on which the change's safety depends and a concrete bad case if each fact is false. Distinguish a real failure path from an imagined caller or a generic possibility.
  4. Test the important facts. Prefer an existing test or runnable product path. When it is cheap and useful, make a small check that executes the real code and would fail for the bad case; keep a one-off probe outside the product diff unless it is a valuable regression test. Use isolated fixtures or a safe test mode for code with consequential side effects. Record the command, observed result, and relevant revision without exposing credentials or private data. A code citation or argument can support a fact when execution is unavailable, but label the remaining uncertainty.
  5. Report the verdict. State what changed, the assumptions and their proof level, confirmed risks with likely impact, risks checked and cleared, and the cheapest remaining check. Use unproven for a critical fact you could not verify. Do not turn an incomplete check into a pass.

When the task is a code review, return findings to its review owner. When it includes a fix, verify the changed user workflow through verify if product behavior needs hands-on acceptance.

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.

Reviews can't be read right now.

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.

Check your setup, free