Catalog
github/context-map

github

context-map

Generate a map of all files relevant to a task before making changes

v1.0Latest
New~276Updated Jun 26, 2026

Context Map

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

Task

{{task_description}}

Instructions

  1. Search the codebase for files related to this task
  2. Identify direct dependencies (imports/exports)
  3. Find related tests
  4. 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.

Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

78/100

Grade

B

Good

Safety

92

Quality

72

Clarity

82

Completeness

68

Summary

The Context Map skill guides AI agents to analyze codebases and generate a structured map of files, dependencies, tests, and patterns relevant to a task before implementation. It enforces a discovery-first workflow by requiring explicit review before changes proceed, reducing the risk of incomplete or breaking modifications.

Detected Capabilities

codebase analysisfile searchdependency detectiontest file identificationpattern recognitionrisk assessment output

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

analyze code impactmap dependenciesscope before refactoridentify breaking changescodebase discoverydependency review

Use Cases

  • Review scope impact before modifying shared code
  • Understand dependency chains in complex projects
  • Identify breaking changes to public APIs
  • Plan refactoring across multiple related files
  • Document required test updates alongside code changes
  • Prevent unintended side effects in tightly coupled modules

Quality Notes

  • Instructions are clear and actionable — agent understands the workflow (search → analyze → output → review)
  • Output format is well-structured with Markdown tables for readability and machine-parseability
  • Risk assessment checklist is practical (breaking changes, migrations, config updates)
  • The skill operates entirely in analysis mode — no file writes, shell execution, or external calls
  • Good boundary enforcement: agent must not proceed to implementation without explicit review
  • Minor limitation: does not specify search scope or tool recommendations (grep, ast parsing, etc.) — relies on agent's built-in search capability
  • Could benefit from examples of what 'similar patterns' means and how to identify them
  • No guidance on handling ambiguous dependencies or circular imports
Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use github/context-map in your dev environment

Command Palette

Search for a command to run...