context-map ยท diff
git:20260310.e140a97 to v1.0.0
3 added, 0 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
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.