github/awesome-copilot · Official

context-map

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

All-time #1553 First seen Feb 25, 2026
8-week activity · all time api

Installation

$ npx skills add github/awesome-copilot --skill context-map

Summary

  • Analyze codebases and map task-relevant files before implementing changes.
  • Automatically searches for related files, dependencies, tests, and similar code patterns to establish full context Generates structured markdown output with files to modify, dependency relationships, test coverage, and reference patterns Includes risk assessment checklist for breaking changes, migrations, and configuration updates Designed as a pre-implementation step to prevent missed dependencies and unintended side effects

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from github/awesome-copilot · top by installs.

npx skills add github/awesome-copilot

Browse all from github/awesome-copilot

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 38.8K
License LICENSE
Default branch main
Open issues 21
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents github-copilot

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,146 B
  • docs SUMMARY.md 87 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 9,700 installs

SKILL.md

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.