blast-radius SKILL.md skillA
blast-radius from yeachan-heo/oh-my-claudecode is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yeachan-heo/oh-my-claudecode/blast-radius@git:20261108.ac1df7fPins git:20261108.ac1df7f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yeachan-heo/oh-my-claudecode
- Path
skills/blast-radius/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261108.ac1df7f, committed Nov 8, 2026
- Size
- 2,238 bytes
- Repository stars
- 40,827
- License
- MIT
Map what a change could break beyond the diff — dependents found by search and AST, classified certain/likely/unlikely — and prove the certain and likely ones by running their checks. Before risky refactors or signature changes.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Blast Radius The diff tells you what changed; it does not tell you what breaks. This skill maps the dependents of a change and proves what it can — by running code, not by reasoning alone. ## When to use - a signature, data shape, or behavior other code calls changed - a dependency bump, config default flip, or migration - the user asks "what could this break?" ## Workflow 1. **Name the change surface**: exported symbols, persisted formats, CLI flags, API contracts, timing assumptions. List them explicitly. 2. **Map dependents**: grep for each symbol; where available use AST search (`ast_grep_search` MCP tool) to catch structural uses text search misses; follow re-exports one more hop than feels necessary. 3. **Classify each dependent**: - **certain** — calls the changed surface directly - **likely** — consumes a type or format the change touches - **unlikely** — shares a module but not the surface 4. **Prove what you can**: for every certain and likely impact, run the exact check that would catch the break — its test, its typecheck, its build, or a one-off command exercising the path. Report real output. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3kkfmgeocddezsm6/7f189876c496d5caaa622cec9d01705314883397cc3efb3622cf0cd512d669b9.json
Then /plugin install blast-radius@markdownregistry-3kkfmgeocddezsm6 in Claude Code. It installs git:20261108.ac1df7f, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add yeachan-heo/oh-my-claudecode/blast-radius@sha256:7f189876c496d5caThe line at the top of this page pins the label git:20261108.ac1df7f, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3kkfmgeocddezsm6)
4 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in yeachan-heo/oh-my-claudecode/blast-radius since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of blast-radius from somewhere else? Ask it: where did my blast-radius come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 8, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/blast-radius/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2238 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yeachan-heo/oh-my-claudecode · 40,827 stars · license MIT · pushed 2026-11-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3kkfmgeocddezsm6 GET https://markdownregistry.com/api/v1/resolve?ref=yeachan-heo/oh-my-claudecode/blast-radius GET https://markdownregistry.com/api/v1/blob/7f189876c496d5caaa622cec9d01705314883397cc3efb3622cf0cd512d669b9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from yeachan-heo/oh-my-claudecode
Every file in yeachan-heo/oh-my-claudecode