blast-radius
Skill74 starsChanged 2 days agoLicence not identifiedView on GitHub
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.
118 other projects use a version of this, 69 of them edited; 43 of 67 edited versions we compared changed its rules; 5 new projects in the last 4 weeks, against 3 the 4 before.
How people change it
43 of 67 edited versions changed its rules, and some changes recur.
Of the 67 edited versions we compared: 22 keep every rule, 2 are an older text, 43 made changes of their own.
Not in older versions
- Read the change. The diff, the symbols it adds, changes, and deletes, and what it now does differently, including the part the diff doesn't spell out. Use
whystep 2 to pull the PR and commits.missing from 2 of 2
Rules people drop
- Write it through
unslop, cite real code, and strip anything private before it goes anywhere public.dropped by 16 of 43 - Read the change. The diff, the symbols it adds, changes, and deletes, and what it now does differently, including the part the diff doesn't spell out. Use
whystep 2 to pull the PR and commits.dropped by 15 of 43
Rules people add
- Risks. Only the real ones. Each names how it breaks, the
file:line, how likely and how bad, and how to check. Paste the proof for the ones that matter.added by 28 of 43 - Prove the one fact. Write the test or the drive, run it and paste what happened.added by 2 of 43
- A rule we can't quote: its licence doesn't allow itadded by 2 of 43
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Rising: 5 new projects took it in the last 4 weeks, 1.7× the 4 weeks before.thin data
Most recently taken up by
- GoBeromsu/craft-skillsedited, first seen Nov 16, 2026
- gfunc/skillsword for word, first seen Nov 16, 2026
- shiwenbin1617/pstackword for word, first seen Nov 16, 2026
- pantheon-org/tekhneedited, first seen Nov 15, 2026
- backnotprop/pstackedited, first seen Nov 15, 2026
- sammyjoyce/prime-pstackedited, first seen Nov 15, 2026
Other versions118 projects use a version of this.
Word for word · 11
- pixeltable/pixeltable★ 1.7k100% same
- moeru-ai/xsai★ 667100% same
- adjohn/pstack★ 9100% same
- anis-dr/skills★ 4100% same
- shiwenbin1617/pstack★ 4100% same
- kwaa/skills★ 2100% same
- gfunc/skills★ 1100% same
- PickleBoxer/pstack★ 1100% same
- Tashila-109/tstack-skills★ 1100% same
- upamune/skills★ 1100% same
1 more not listed
Edited · 69
- backnotprop/pstack★ 4.2k98% same
- savannahfeder/agentbox★ 41916% same
- jtaroreh/agystack★ 12886% same
- uzairansaruzi/p3-stack★ 12698% same
- Dimon94/dverity★ 10785% same
- Dimon94/skills★ 10785% same
- dsebban/skills★ 7196% same
- timharris707/skills★ 4432% same
- korallis/agent-stack★ 4210% same
- painhardcore/pstack★ 2299% same
59 more not listed
Wrote their own version · 38
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- pedrohcgs/claude-code-my-workflow★ 1.7ksame name
- marmot-protocol/mdk★ 69same name
- JetBrains/context★ 38same name
- TheOnlyFusionCube/potetos-for-everyone★ 21same name
- korallis/skills-collection★ 14same name
- rizzn/Public-Agent-Kit★ 11same name
- jjxmonster/skills★ 8same name
- anotherben/claude-harness★ 7same name
28 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository73 other files it gives its agents.
- algorithms/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-reachSkill
- architectSkill
- arenaSkill
- automate-meSkill
- benchmark-checklistSkill
- bklite-ops-product-designSkill
- broSkill
- codebase-designSkill
- code-reviewSkill
- correctSkill
- create-formal-verification-skillSkill
- create-verification-skillSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- figure-it-outSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- howSkill
- implementSkill
- improve-codebase-architectureSkill
- interrogateSkill
- in-your-own-wordsSkill
- ketchupSkill
- ketchup-videoSkill
- maintain-formal-verification-skillSkill
- maintain-verification-skillSkill
- make-bot-uiSkill
- no-commentsSkill
- poteto-modeSkill
- principle-attack-the-premiseSkill
- principle-boundary-disciplineSkill
- principle-build-the-leverSkill
- principle-encode-lessons-in-structureSkill
- principle-exhaust-the-design-spaceSkill
- principle-experience-firstSkill
- principle-explain-the-numberSkill
- principle-fix-root-causesSkill
- principle-foundational-thinkingSkill
- principle-guard-the-context-windowSkill
- principle-laziness-protocolSkill
- principle-make-operations-idempotentSkill
- principle-migrate-callers-then-delete-legacy-apisSkill
- principle-minimize-reader-loadSkill
- principle-model-the-domainSkill
- principle-never-block-on-the-humanSkill
- principle-outcome-oriented-executionSkill
- principle-prove-it-worksSkill
- principle-redesign-from-first-principlesSkill
- principle-separate-before-serializing-shared-stateSkill
- principle-sequence-verifiable-unitsSkill
- principle-subtract-before-you-addSkill
- principle-test-behavior-not-implementationSkill
- principle-type-system-disciplineSkill
- recallSkill
- reflectSkill
- setup-matt-pocock-skillsSkill
- setup-pstackSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 103 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 103 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.
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
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.

