agentleFS
Sign inStart free
educlopezeduclopez/mallard/skills/blast-radius/SKILL.md

blast-radius

Skill4 starsChanged 13 days agoMITView on GitHub

Before shipping a change, find what it could break outside the diff and prove the one fact it is safe because of by running real code. Use when the user says "blast radius", "qué puede romper esto", "revisa el impacto", "cambio de riesgo", or before touching shared code: a PrestaShop override or hook, a theme partial used on many pages, a module config, or mallard internals such as the skill registry, backups or agent adapters.

111 other projects use a version of this, 4 of them edited.

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

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 106 edited versions we read keep these.

  • 1

    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:

    Never invent a caller or an API.

    line 51

“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

Adapted from pstack's blast-radius. Listing callers is not the job, grep does that. The job is the breakage grep does not show. Read-only: it never edits the change. It does not launch parallel model reviews.

1. Read the change

The diff, the symbols added, changed or deleted, and what now behaves differently, including what the diff does not spell out.

2. Find the one fact it is safe because of

Most risky-looking changes are safe because of a single fact ("this hook only runs in the BO", "this symlink target is recreated on update"). Find it. Spend the time here, not on a long list of maybes.

3. Look where grep stops

  • PrestaShop: overrides and the class index cache, hooks registered by other modules, Smarty partials included from other templates, theme.yml and config.xml values read elsewhere, multistore and language differences, the DB column or config key another module reads.
  • Theme CSS: selectors that now match elsewhere, the compiled output versus its source.
  • mallard (Go): other agents' adapters, symlink and backup paths, Windows path handling, state read from ~/.mallard/state.json.

4. Rate how sure you are

For each fact the change depends on, get as far down this list as is cheap and say where you stopped:

  1. You said so (worthless alone).
  2. You pointed at a real file:line.
  3. You walked the failure step by step and it does not reach.
  4. You ran a script or test against the real code.
  5. You reproduced it in the running app (verify-ps-project).

5. Report

  • What it does. Including the non-obvious part.
  • The one safety fact. Proven (state the step) or unproven.
  • Risks. How it breaks, file:line, likelihood, cost, how to check.
  • Cleared. What you checked and why it is fine.
  • Before merge. The cheapest check that catches the real bug.

Never invent a caller or an API. A search that finds nothing is still an answer.

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.

Check your setup, free