context-map

Identify files, dependencies, and tests affected by a planned change.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mberetvas/dbt-migrator --skill context-map-mberetvas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-map
Source: https://github.com/mberetvas/dbt-migrator/tree/main/.github/skills/context-map
Command: npx skills add https://github.com/mberetvas/dbt-migrator --skill context-map-mberetvas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a concise context map that reveals the scope of files, dependencies, and tests impacted by a planned change, enabling safer planning and coordination.

Core Features & Use Cases

  • Scan the repository to identify files touched by a task.
  • Enumerate direct dependencies and related tests to anticipate impact.
  • Locate and reference patterns from existing code to guide implementation and risk assessment.

Quick Start

Identify the scope of your change and generate a context map before implementing changes.

Frequently Asked Questions about context-map

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

FAQPage Schema
How do I map all files affected by a codebase change before implementing it?▼

To map affected files before a codebase change, identify modified files, enumerate dependencies, and list related tests to anticipate impact. This generates a structured context map detailing reference patterns to guide safer implementation across multi-module projects.

What is a context map for codebase refactoring and migrations?▼

A context map for codebase refactoring is a structured output revealing the scope of files, dependencies, and tests impacted by a planned change. It locates existing code patterns to assess risk and enables safer coordination during multi-module migrations.

How do I identify direct dependencies and tests impacted by a planned feature?▼

Identify impacted dependencies and tests by scanning the repository to enumerate direct references related to the planned feature. This assembles a context map that anticipates coordination needs and highlights reference patterns for implementation.

Does codebase impact analysis work for multi-module project refactoring?▼

Codebase impact analysis works for multi-module project refactoring by scanning the repository to identify touched files and related dependencies. It anticipates impact across modules and enforces a structured output detailing tests and reference patterns.

What's the best way to assess risk before modifying existing code patterns?▼

The best way to assess risk before modifying code patterns is to locate and reference existing implementations within the codebase. Generating a context map reveals the scope of impacted files and dependencies, enabling safer planning and coordination.

Why do I need to scan the repository before starting a codebase migration?▼

You need to scan the repository before a codebase migration to identify all touched files and direct dependencies. This anticipates the impact of your changes and produces a context map that coordinates tests and reference patterns across modules.