agentleFS
TheOnlyFusionCubeTheOnlyFusionCube/potetos-for-everyone/skills/blast-radius/SKILL.md

blast-radius

Skill18 starsChanged 53 days agoMITView on GitHub

Prove what a small-looking change can affect before or after editing. Use for compatibility, caller, state, schema, or behavior impact analysis.

Files
SKILL.md

Blast Radius

  1. Name the changed contract: type, value, state transition, API, storage shape, timing, style token, or side effect.
  2. Enumerate direct readers/writers/callers and any serialized/public boundaries.
  3. Trace transitive assumptions by search, type references, tests, runtime wiring, and history as available.
  4. Identify the strongest fact that would make the change safe and prove that fact by running or inspecting code when possible.
  5. Return affected surfaces grouped as definite, plausible, and ruled out with evidence. Never write "safe" without the proof behind it.

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.