Index of every page on this site: llms.txt
All skills
github avatar

/context-map

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

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

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/context-map

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈20 tokens for metadata: the name and description. ≈259 when used: this file.

Description uses 1.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈82 characters, or 1.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill is a planning utility that guides the agent to analyze the codebase and document dependencies before making changes. It consists entirely of text instructions and does not execute code, access sensitive files, or perform network operations.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 7 months ago
  • Refactoring
  • codebase-analysis
  • dependencies
  • task-planning
  • code-navigation

README badge

README badge for github/awesome-copilot/context-map

Generates a dependency map of files relevant to a task before implementation, identifying direct imports, related tests, and similar code patterns. Use this skill to audit scope and risk before making changes to an unfamiliar codebase.

Generated from the current SKILL.md.

What does this skill do before making code changes?
It analyzes the codebase to identify all files relevant to a task, including direct dependencies, related tests, and similar patterns, then outputs a structured context map as markdown.
Does this skill actually implement changes?
No. It only generates a map for review. Implementation happens in a separate step after the map is approved.
What information does the context map include?
Files to modify, dependencies that may need updates, related test files, reference patterns from existing code, and a risk assessment checklist.

Generated from the current SKILL.md. These answers refresh after source changes.