Context Map

Before you start coding, this generates a structured map of every file that might be affected by your changes. It searches for direct dependencies, related tests, similar patterns you can reference, and flags potential breaking changes or required migrations. Think of it as mandatory reconnaissance before touching anything important. The output is a markdown table that forces you to actually understand the blast radius of your changes instead of diving in blind. Honestly saves more time than it costs, especially on unfamiliar codebases where you'd otherwise spend hours tracking down mysterious test failures.

skills.sh installs: 9.7K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill context-map --agent claude-code

Installs into .claude/skills of the current project.

Files

Context Map

Before implementing any changes, analyze the codebase and create a context map.

Task

Instructions

Search the codebase for files related to this task
Identify direct dependencies (imports/exports)
Find related tests
Look for similar patterns in existing code

Output Format

## Context Map

### Files to Modify
| File | Purpose | Changes Needed |
|------|---------|----------------|
| path/to/file | description | what changes |

### Dependencies (may need updates)
| File | Relationship |
|------|--------------|
| path/to/dep | imports X from modified file |

### Test Files
| Test | Coverage |
|------|----------|
| path/to/test | tests affected functionality |

### Reference Patterns
| File | Pattern |
|------|---------|
| path/to/similar | example to follow |

### Risk Assessment
- [ ] Breaking changes to public API
- [ ] Database migrations needed
- [ ] Configuration changes required

Do not proceed with implementation until this map is reviewed.

SKILL.md on GitHub