agentleFS
Sign inStart free
totvstotvs/engpro-advpl-tlpp-skills/skills/advpl-tlpp/context-map/SKILL.md

context-map

Skill166 starsChanged 5 months agoMITView on GitHub

Generate a context map of all files relevant to a task before implementing changes. Use when a user says "map the codebase for this change", "what files are affected", "show me dependencies", or before starting implementation to identify files to modify, dependencies, test files, and reference patterns.

We split this skill into the rules it gives an agent

5 rules. 1 is common, 4 are distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 6 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 17
  2. Distinctive:

    Before implementing any changes, analyze the codebase and create a context map.

    line 24
  3. Distinctive:

    Search the codebase for files related to this task

    line 32
  4. Distinctive:

    Look for similar patterns in existing code

    line 35
  5. Common:

    Do not proceed with implementation until this map is reviewed.

    line 68

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Context Map

When to Use

Use this skill when:

  • Preparing to implement changes and need to understand the affected codebase
  • Identifying all files, dependencies, and tests related to a task
  • Finding reference patterns and similar implementations in the codebase
  • Creating a pre-implementation analysis to reduce missed changes

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free