Eng Blast Radius
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it is safe because of by running real code. Use when asked for the "blast radius of X" or "what could this break", or when reviewing a small diff you do not trust.
Install
npx skills add jpoehnelt/skills --skill eng-blast-radiusgit clone --depth 1 https://github.com/jpoehnelt/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/eng-blast-radius ~/.claude/skills/eng-blast-radiusPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Blast radius Find what a change breaks somewhere else, before it ships. `comms-how` explains what code does and `comms-why` explains why it is shaped that way. This skill finds what the change breaks elsewhere. Listing callers is not the job, because grep does that in a second. The job is the breakage grep will not show. Repo facts (from AGENTS.md or CLAUDE.md): cross-package or cross-service contracts, generated outputs and their consumers, and the task runner's affected-package query. ## Do not trust your own writeup A blast-radius writeup that sounds right is worthless, because it reads as convincing whether or not it is true. Find the one or two facts the safety claim depends on and prove them by running code. For each such fact, 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`, or at the library's own source. 3. You walked the failure step by step and showed it cannot happen. 4. You ran a script or test that calls the real code and fails loudly if you are wrong. 5. You reproduced it in the running app. Step 4 is usually one small script that imports the same library the app ships and calls the exact function you worry about. ## Steps 1. Read the change: the diff, the symbols it adds, changes, and deletes, and what behaves differently, including the part the diff does not spell out. Use `comms-why` to pull the PR and commits.
Details
- Skill name
eng-blast-radius- Repository
- jpoehnelt/skills
- Path
eng-blast-radius/SKILL.md- License
- MIT
- Repo updated
- 12 November 2026
FAQ
What does the Eng Blast Radius skill do?
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it is safe because of by running real code. Use when asked for the "blast radius of X" or "what could this break", or when reviewing a small diff you do not trust.
How do I install the Eng Blast Radius skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jpoehnelt/skills --skill eng-blast-radius. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Eng Blast Radius popular?
It lives in jpoehnelt/skills, which has 23 GitHub stars and 1 forks.
Related skills
Agents Correct
23jpoehnelt/skills
Find the mistakes agents keep repeating in a repo and make each one impossible, trying architecture first, then types, lint, tests, and docs last. Use when the operator keeps correcting the same mistake, or for /agents-correct.
Agents Create Verification Skill
23jpoehnelt/skills
Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-create-verification-skill, "make a verify skill for this repo", or when a project has no scripted way to prove UI, CLI, or service behavior.
Agents Reflect
23jpoehnelt/skills
After a work session, review what went wrong and right and turn each lesson into a concrete edit to an existing skill or AGENTS.md line. Use when the user says "reflect" or /agents-reflect.
Isms P Audit
9basejb/isms-p-audit-skill
ISMS-P 인증 사전 점검을 위한 코드/IaC 정적 분석 스킬. 사용자가 "ISMS 점검", "ISMS-P 준비", "보안 감사", "통제항목 점검", "개인정보보호 감사", "정보보호 인증 준비"를 언급하거나, NestJS/ Spring/Django/Rails 같은 백엔드 프로젝트에서 IAM·로깅·암호화·접근통제 미흡 사항을 식별해 달라고 요청할 때 호출한다. Glob/Grep/Read로 코드와 Terraform/CloudFormation/Kubernetes 매니페스트를 스캔해 ISMS-P 통제항목과 매핑된 리스크 보고서를 생성한다. EN: Static analysis skill for ISMS-P (Korean Personal Information & Information Security Management System) pre-audit. Triggers on phrases like "ISMS audit", "ISMS-P readiness", "security compliance check", "Korean privacy audit". Scans source code and IaC to map findings to ISMS-P controls and
Effect
23jpoehnelt/skills
Apply Effect v4 conventions for services, layers, tagged errors, boundary runners, resources, retries, deadlines, HTTP, and tests. Use when writing or reviewing TypeScript that imports effect, adds a service or error class, chooses where to run a program, bounds external I/O, or tests Effect code.
Software Audit Skill
9luigimorel/software-audit-skill
Security and privacy audit for web and mobile apps built fast with AI assistance ("vibe coded"). Checks for OWASP Top 10 issues, leaked secrets, broken access control, sensitive data in logs, APIs that expose too much data, misconfigured Supabase/Firebase rules, insecure mobile storage, and risky dependencies. Use this skill whenever the user asks to audit, review, harden, pen-test, sanity-check, or "make safe" an app or repo, asks "is my app secure?", "is this safe to launch/ship?", "am I leaking anything?", or mentions OWASP, MASVS, RLS, exposed API keys, or logging sensitive data, rate limi
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.