context-map
Generate a map of all files relevant to a task before making changes
Profile →npx skills add github/awesome-copilot --skill context-map --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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.
- Task
- Instructions
- Output Format
What does the context-map skill do?
Generate a map of all files relevant to a task before making changes
How do I install it?
Run `npx skills add github/awesome-copilot --skill context-map --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.