Context map
Skill tbc-servicos/dataagile-agent-kit/protheus/skills/context-map
Plugin Claude Code para Protheus e ADVPL/TLPP — base 155k+ registros, Agent Teams, compilação TDS-CLI, testes TIR e MCP PO-UI
npx -y skills add tbc-servicos/dataagile-agent-kit --skill context-mapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.8 KB, as published. Nobody here has run it
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
- Search the codebase for files related to this task
- Identify direct dependencies (imports/exports)
- Find related tests
- 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.