Trace spec graph dependencies to generate a focused scope document.
npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill scope-edonghyun
Please help me install this Agent Skill. Skill: scope Source: https://github.com/edonghyun/donghyuns-agent-tools/tree/main/plugins/spec-mirror/skills/scope Command: npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill scope-edonghyun
This Skill helps you understand the full impact of a proposed change before you edit anything, so you can avoid breaking dependent specs, flows, and tests.
Ask for the blast radius of a specific spec target, and this Skill will generate a focused scope document that shows what depends on it and what it depends on.
High-intent search queries and answers about installing and using this skill.
Blast radius analysis traces the spec graph forward and backward from a target element to identify direct dependencies and dependents. You need it before refactors, API changes, or schema migrations to avoid breaking dependent specs, flows, and tests.
To trace dependency graph impacts for a schema migration, request a blast radius analysis on your specific spec target. This generates a focused scope document showing what depends on the target, what it depends on, and what may break.
Yes, you can infer the test surface affected by an API change. The analysis applies test-surface inference alongside dependency graph traversal and refs mention lookup to identify what tests are likely impacted by your modification.
Impact analysis works with layered specs, flows, and source-file references. It applies depth-2 blast-radius analysis to traverse these structures and resolve exact targets before generating a single-file markdown scope document.
The best way to plan a refactor without breaking dependent specs is to generate a focused mini-scope document. It tells you what to read, what may break, and what test surface is likely affected before you edit anything.
A limitation of depth-2 blast-radius analysis is that it requires exact target resolution to traverse the dependency graph. If your spec target cannot be precisely identified, the scope document cannot accurately map the test surface or dependent flows.
alvazoneDerive dependency-ordered build sequences from traversable spec graphs.
CANTAGESTUDIOAssess refactoring risk across blast radius, reversibility, and test coverage for go/no-go decisions.
drhaltoTrace dependency paths and estimate change impact across project files.
TimMoyenceGuide users to GitNexus MCP tools, resources, and knowledge graph schema.
