Analyzes what a code diff breaks outside its changed lines before merging.
npx skills add https://github.com/blauwtje/exo --skill blast-radius-blauwtje
Please help me install this Agent Skill. Skill: blast-radius Source: https://github.com/blauwtje/exo/tree/main/skills/blast-radius Command: npx skills add https://github.com/blauwtje/exo --skill blast-radius-blauwtje
High-intent search queries and answers about installing and using this skill.
Run a blast radius analysis on the diff: state what behavior changes, name the one fact its safety rests on, trace consumers beyond grep including callbacks and built keys, then run the real code to prove or disprove that fact before the merge proceeds.
Grep misses dynamically built keys, callbacks and hooks, code in other languages, and separate processes reading the same data. A blast radius check names exactly what was searched and follows those indirect paths that symbol search stops at.
No. The test suite covers the diff's own code, while breakage outside the diff runs in no test the change touched. Safety claims need to be proven by running the real code, not inferred from a passing pipeline.
Skip it for failures already observed, which belong to debugging, for explaining how code works with no decision riding on it, for checking a finished branch against its plan, and for edits whose effect stays inside one function.
They rank proof strength: [1 asserted] is an unverified claim, [2 file:line] cites code, [3 traced] follows the path, [4 ran] executes the real code, and [5 live] reproduces in the running app. Claims below level 4 are reported as unproven, never as safe.
agents-repoRefines an existing draft plan against repository context with labeled assumptions in one pass.
ai-heroStash uncommitted changes and switch away from an unmerged Git branch.
anomalyarmorDiagnose root causes of stale data and triggered alerts using lineage and historical monitoring data.
ShtianAnalyze what a code change could break beyond the diff and prove safety by running real code.
