context-map

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

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/juanjaragavi/utilities-manager --skill context-map-juanjaragavi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-map
Source: https://github.com/juanjaragavi/utilities-manager/tree/main/.agents/skills/context-map
Command: npx skills add https://github.com/juanjaragavi/utilities-manager --skill context-map-juanjaragavi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Making code changes without understanding the surrounding codebase leads to broken imports, missed test updates, and unintended side effects. This Skill forces a pre-implementation analysis step that maps every file a task touches before any code is written. ## Core Features & Use Cases - Dependency Discovery: Searches the codebase for files related to the task and identifies direct import/export relationships. - Test and Pattern Identification: Locates related test files and similar existing code patterns to follow as references. - Structured Risk Output: Produces a Markdown report with tables for files to modify, dependencies, tests, reference patterns, and a risk checklist covering breaking API changes, migrations, and configuration updates. - Use Case: Before refactoring a shared utility module, run this Skill to list every consumer of that module, the tests covering it, and whether the change breaks a public API. ## Quick Start Ask the AI to generate a context map for your task, for example: create a context map before adding pagination to the user list endpoint.

Frequently Asked Questions about context-map

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

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

Run a context map analysis that searches the codebase for files related to your task, traces direct import/export dependencies, and lists affected tests. Review the generated report before writing any implementation code.

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

Search for files related to the task, then trace direct dependencies through imports and exports. The context map output organizes these into tables covering files to modify, dependent files, and related test coverage.

What should a pre-implementation code analysis include?▼

It should include files to modify with planned changes, dependency relationships, test files covering affected functionality, similar existing patterns to follow, and a risk checklist for breaking API changes, migrations, and configuration updates.

When should I skip creating 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.

Does a context map prevent breaking changes?▼

It reduces risk by surfacing dependencies and a risk checklist before implementation, but it does not guarantee safety. The map must be reviewed and acted on, since it only identifies impact rather than enforcing correctness.