blast-radius
Prove what a small-looking change can affect before or after editing. Use for compatibility, caller, state, schema, or behavior impact analysis.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 22
- Forks
- 1
01 前言 Front Matter
- name
- blast-radius
- description
- Prove what a small-looking change can affect before or after editing. Use for compatibility, caller, state, schema, or behavior impact analysis.
03 SKILL.md 正文
Blast Radius
- Name the changed contract: type, value, state transition, API, storage shape, timing, style token, or side effect.
- Enumerate direct readers/writers/callers and any serialized/public boundaries.
- Trace transitive assumptions by search, type references, tests, runtime wiring, and history as available.
- Identify the strongest fact that would make the change safe and prove that fact by running or inspecting code when possible.
- Return affected surfaces grouped as definite, plausible, and ruled out with evidence. Never write "safe" without the proof behind it.
04 同仓库更多 Skills
why
Recover why a system or decision exists by triangulating source history and connected evidence. Use for rationale archaeology and historical questions.
unslop
Cut AI tells, filler prose, superficial -ing phrases, and bloated commentary from writing and code. Use for all written deliverables and code cleanup.
typescript-best-practices
Apply disciplined TypeScript modeling and boundary parsing. Use when reading or editing TypeScript.
technical-writing
Write maintainable technical docs, RFCs, READMEs, PR descriptions, and commit messages. Use for durable engineering prose.
teach
Teach a subsystem or change so the reader can reason about it, combining how and why evidence. Use for real understanding rather than summary.
tdd
Write a minimal failing test before implementation, make it pass with the simplest code, and refactor cleanly. Use when implementing bug fixes or features with clear verification targets.