skills.rest
yiwei79
yiwei79OFFICIAL
Explore all skills by this author →
GitHub

context-map

Maps dependency graphs and blast radius before multi-file code changes.

1|Updated Apr 3, 2026
Search Tags:#code analysis#refactoring#impact analysis#risk assessment#dependency mapping#blast radius
One-click install
npx skills add https://github.com/yiwei79/root-azoth --skill context-map-yiwei79
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-map
Source: https://github.com/yiwei79/root-azoth/tree/main/.opencode/skills/context-map
Command: npx skills add https://github.com/yiwei79/root-azoth --skill context-map-yiwei79

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Making changes across multiple files without understanding dependencies leads to cascading failures, broken tests, and unexpected side effects. This Skill provides a structured process to identify targets, map upstream and downstream dependencies, and assess risk before any implementation begins. ## Core Features & Use Cases - Dependency Mapping: Identifies direct target files plus upstream dependencies and downstream consumers, including tests and documentation. - Blast Radius Assessment: Classifies changes into GREEN (<5 files), YELLOW (5-10 files), or RED (>10 files) zones with concrete action recommendations per zone. - Reusable Template: Provides a ready-to-use context map template covering targets, dependencies, risk factors, existing tests, and a scope decision. - Use Case: Before renaming an authentication module, map that it touches the handler, middleware, API routes, and tests, determine the change is YELLOW zone, and create a checkpoint before proceeding. ## Quick Start Ask the agent to map the blast radius and dependencies for the planned change before modifying any files.

Frequently Asked Questions about context-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assess the blast radius of a code change?▼

Identify the files you will directly modify, then map what those files depend on (upstream) and what depends on them (downstream), including tests and docs. Count total affected files and classify the change as GREEN (<5), YELLOW (5-10), or RED (>10).

When should I map dependencies before refactoring?▼

Map dependencies before any cross-cutting change such as renames, moves, or refactors, before pipeline implementation stages, and when entering unfamiliar code. Large changes especially need pre-mapping to keep entropy bounded.

What should a dependency map for a code change include?▼

Include direct target files with planned changes, upstream dependencies the targets rely on, downstream consumers including tests and documentation, a file count with risk zone, and a final decision to proceed, checkpoint, scope down, or seek approval.

When is a change too large to proceed without approval?▼

A change affecting more than 10 files is classified as RED zone and should be scoped down or escalated for human approval. Changes touching public APIs, config, or multiple modules raise risk even at smaller file counts.

Does context mapping replace running tests after a change?▼

No. Context mapping is a pre-change information gathering step that identifies which tests cover the affected files. Tests still must be run after implementation to verify the change did not break mapped dependents.

Related Skills

Explore More Software Engineering Skills→
ruvnetruvnet
4.5k

plan-change

Generates a minimal file-level implementation plan from a feature request before coding.

Community
Basic
PandaWithAPlanPandaWithAPlan
2

test-plan

Prioritize test cases by risk and impact from affected zones and past failures.

Community
Advanced
OrestesKOrestesK
2

semantic-git

Analyze structural code changes and downstream impact via semantic diffs.

Community
Basic
Dragoon0xDragoon0x
4

map

Map JavaScript and TypeScript codebase architecture via import graph regex analysis.

Community
Intermediate