agentleFS
Sign inStart free
aicodekingaicodeking/deepseek-stack/skills/ds-blast-radius/SKILL.md

ds-blast-radius

Skill80 starsChanged 15 days agoMITView on GitHub

Find what a change could break outside its own diff, then prove the key safety fact by running real code. Use before shipping a risky or untrusted change, for 'what could this break', 'blast radius of X', or /ds-blast-radius.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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 change: the diff, the symbols it adds, changes or removes, and the behavior it now has that the diff does not spell out.

    line 12
  2. Distinctive:

    Look where search stops. Read the source of libraries you call at their pinned version.

    line 14
  3. Distinctive:

    Every key fact is at level 4 or higher, or you have said why it could not be, and the report is written.

    line 26
  4. Distinctive:

    Do not fix anything here. Hand fixes to the normal flow.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

ds-blast-radius

Listing callers is easy. The job is finding the breakage that a text search will not show, and proving the change is safe with a run instead of an argument.

Steps

  1. Read the change: the diff, the symbols it adds, changes or removes, and the behavior it now has that the diff does not spell out.
  2. Find the one or two facts the change is safe because of, for example "this only removes cache entries that are already expired". Most risk clears if that fact holds. Spend your effort here.
  3. Look where search stops. Read the source of libraries you call at their pinned version. Check timing: async ordering, teardown, retries. Follow data that leaves the code: API responses, database columns, file formats, config, other languages reading the same data.
  4. Grade each key fact by how far you proved it:
    1. you said so (worthless alone),
    2. you pointed at a real file and line,
    3. you traced the failure path and showed it cannot be reached,
    4. you ran a script or test against the real code that fails loudly if you are wrong,
    5. you reproduced it in the running app.
  5. Push each key fact to level 4 when it is cheap. Usually that is one small script calling the exact function in question.
  6. Report: the key facts, their proof level with the command and output, any real breakage found, and what stayed unproven.

Stop when

  • Every key fact is at level 4 or higher, or you have said why it could not be, and the report is written.
  • Or you found a real break. Report it with the repro and stop.

Rules

  • A convincing write-up is not proof. Show output.
  • Do not fix anything here. Hand fixes to the normal flow.

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