Before and after changing anything shared — a function's return value, a signature, a schema, a label set, a config default, a constant, a file format — find every consumer and actually run them. Catches the change that looks purely additive but silently breaks a contract in a file you never opened. Use when editing shared code, adding a field/column/return element, renaming, changing units or defaults, or touching a pipeline that produces reported numbers.
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/blast-radius/SKILL.mdThis skill's instructions live in .claude/skills/blast-radius/SKILL.md.
Read that file now and follow it, with the files it points to. Read AGENTS.md
first if you have not already.
It was written for Claude Code. Running it from Codex, Antigravity or another agent:
$ARGUMENTS, use what the user asked for..claude/agents/ (through the
Agent or Task tool), do that step where it appears in the procedure: never later, and never
skip it. A step that gates what follows still gates it (/commit runs its verifier before it
commits). Read the agent's file for what the step checks./verify-claims for citations) before
relying on it.allowed-tools, model, effort, argument-hint and
disable-model-invocation in the source's frontmatter configure Claude Code. Ignore them.AGENTS.md
yourself; the git pre-commit gate and CI still apply to your commits.pedrohcgs/claude-code-my-workflow
fe70774
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.