context-map · v1.0.0 · 2026-05-18 · sha256 ee830e85e86043bb
context-map v1.0.0A
Immutable. This exact content never changes and is served at /api/v1/blob/ee830e85e86043bb.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ijiuolxhu76qprsc/ee830e85e86043bbf4c037ceb204bb587111868db015092f71283e0eeaec99d3.json
Then /plugin install context-map@markdownregistry-ijiuolxhu76qprsc in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
name: context-map
description: "Generate a map of all files relevant to a task before making changes"
metadata:
author: Ronnasayd Machado - github.com/Ronnasayd
version: "1.0.0"
---
# 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
```markdown
## 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.