skills.rest
hoonsubin
hoonsubinCOMMUNITY
Explore all skills by this author →
Website𝕏@hoonsubinGitHub

context-map

Generates a structured map of files, dependencies, and tests relevant to a coding task.

Updated Apr 22, 2026
Search Tags:#code analysis#impact analysis#context map#dependency tracing#pre-implementation#codebase search#test discovery
One-click install
npx skills add https://github.com/hoonsubin/scrum-master-mcp-server --skill context-map-hoonsubin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-map
Source: https://github.com/hoonsubin/scrum-master-mcp-server/tree/main/.roo/skills/context-map
Command: npx skills add https://github.com/hoonsubin/scrum-master-mcp-server --skill context-map-hoonsubin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers often start changing code without understanding which files, dependencies, and tests are affected, leading to broken imports, missed test updates, and unreviewed risks. This Skill enforces a pre-implementation analysis step that maps the full blast radius of a task before any code is modified. ## Core Features & Use Cases - Codebase Discovery: Searches the repository for files related to the task and identifies direct import/export dependencies. - Structured Output: Produces a Markdown context map with tables for files to modify, dependencies, test files, reference patterns, and a risk assessment checklist. - Use Case: Before refactoring a shared utility module, run this Skill to list every file importing it, the tests covering it, and similar patterns to follow, then review the map before writing any code. ## Quick Start Ask the AI to generate a context map for your task, for example: create a context map for adding pagination to the sprint backlog endpoint before making any changes.

Frequently Asked Questions about context-map

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

FAQPage Schema
How do I analyze code impact before making changes?▼

Use this Skill to generate a context map before editing code. It searches the codebase for task-related files, traces import/export dependencies, finds related tests, and outputs a structured Markdown table for review.

How to find all files affected by a code change?▼

The context map identifies direct dependencies by tracing imports and exports from the files you plan to modify. It also locates test files covering the affected functionality and similar existing patterns to follow.

What should a pre-implementation code analysis include?▼

It should list files to modify with their purposes, dependent files that may need updates, relevant test files, reference patterns from existing code, and a risk checklist covering breaking API changes, migrations, and configuration updates.

Does the context map skill modify any code?▼

No, it only performs read-only analysis and produces a Markdown report. The instructions explicitly block implementation until the generated map has been reviewed.

When should I skip generating a context map?▼

For trivial single-file changes with no external consumers, a full context map adds little value. It is most useful for changes touching shared modules, public APIs, or functionality covered by multiple tests.

Related Skills

Explore More Software Engineering Skills→
microsoftmicrosoft
561

github-repo-explore

Search, clone, and explore external GitHub repositories using the GitHub CLI.

Official
Intermediate
SkastVnTSkastVnT
7

test-impact-mapper

Map changed files to the smallest sufficient test verification set.

Community
Advanced
flutterflutter
2.8k

dart-run-static-analysis

Run Dart static analysis and apply automated lint fixes.

Official
Intermediate
sudohakansudohakan

using-gh-cli

Guide GitHub CLI usage for repositories, PRs, issues, and API calls.

Community
Intermediate