
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.
$ npx -y skills add github/awesome-copilot --skill context-map --agent claude-codeInstalls into .claude/skills of the current project.
Before implementing any changes, analyze the codebase and create a context map.
{{task_description}}
## 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.
Sponsors