src/orchestrator/skills/context-map/SKILL.md
Maps file dependencies, flags shared imports, and groups files for safe parallel editing before code changes. Use when planning a refactoring, analyzing change impact, or understanding which files a modification will affect.
npx skillsauth add etylsarin/opencastle context-mapInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate a file impact map before code changes to identify affected files, relationships, and cascades — improving agent file partitions for parallel work.
| Use | Skip |
|-----|------|
| Feature implementation (Phase 1) | Isolated bug fixes ≤2 files |
| Refactoring (Phase 1 Scope) | |
| Schema changes cascading through queries/components | |
| Any task touching libs/ | |
Identify files that MUST change from the task description.
Find consumers of entry-point exports:
grep_search("import.*from.*places", isRegexp=true) # find importers
vscode_listCodeUsages("PlaceCard") # find component consumers
grep_search("places.*route|/places", isRegexp=true) # find route references
Find what entry points depend on:
grep_search("from.*libs/", includePattern="src/places/**") # shared lib deps
grep_search("from.*config", includePattern="src/places/**") # config deps
Produce a compact Context Map for the Team Lead and downstream agents. Example minimal map (inline):
Context Map — Feature: Add priceRange
- Entry points:
- src/lib/place/schema.ts
- src/components/PriceRangeFilter/PriceRangeFilter.tsx
- Dependents (trace outward):
- src/pages/places/page.tsx
- src/components/PlacesList/PlaceCard.tsx
- Sources (trace inward):
- src/lib/filters.ts
- src/shared/types/place.ts
- Unaffected (optional):
- src/components/Account/**
Validation checkpoint: run grep_search and vscode_listCodeUsages results into the map and confirm all listed files open without errors (CI: pnpm typecheck). For full template and Team Lead integration snippets see REFERENCE.md in this directory.
grep_search / list_code_usagesdevelopment
Defines 10 sequential validation gates: secret scanning, lint/test/build checks, blast radius analysis, dependency auditing, browser testing, cache management, regression checks, and smoke tests. Use when running pre-deploy validation or CI checks, CI/CD pipelines, deployment pipeline validation, pre-merge checks, continuous integration, or pull request validation.
development
Generates test plans, writes unit/integration/E2E test files, identifies coverage gaps, and flags common testing anti-patterns. Use when writing tests, creating test suites, planning test strategies, mocking dependencies, measuring code coverage, or test planning.
development
Provides model routing rules, validates delegation prerequisites, supplies cost tracking templates, and defines dead-letter queue formats for Team Lead orchestration. Load when assigning tasks to agents, choosing model tiers, starting a delegation session, running a multi-agent workflow, delegating work, choosing which model to use, or assigning tasks.
testing
Saves and restores session state including task progress, file changes, and delegation history. Use when saving progress, resuming interrupted work, picking up where you left off, or checkpointing current work.