context-map

Maps affected files, dependencies, tests, reference patterns, and risks before code changes.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/serpro-workshop-fortaleza/datacorp-sifap-modernization-team-kit --skill context-map-serpro-workshop-fortaleza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-map
Source: https://github.com/serpro-workshop-fortaleza/datacorp-sifap-modernization-team-kit/tree/main/.github/skills/context-map
Command: npx skills add https://github.com/serpro-workshop-fortaleza/datacorp-sifap-modernization-team-kit --skill context-map-serpro-workshop-fortaleza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting implementation without knowing the blast radius of a change leads to missed files, broken dependencies, untested code paths, and surprise regressions. This Skill produces a written context map that delimits exactly what a task affects before any code is written. ## Core Features & Use Cases - Impact Delimitation: Lists every file to create or modify, with the concrete change described for each. - Dependency and Test Tracing: Follows imports and exports to find what breaks when a signature changes, and identifies existing test coverage plus gaps marked as "to write". - Risk Signaling: Flags public API contract changes, database migrations, and configuration or secret modifications before programming starts. - Use Case: Before adding a status field to a payments API, generate a map listing the controller to modify, the enum to create, the frontend page that renders the status, the tests to extend, and an existing PATCH pattern to follow. ## Quick Start Ask the AI to map the impact of your planned change, for example: "Delimit the impact of adding a status field to the payments API before I start coding."

Frequently Asked Questions about context-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan the impact of a code change before implementing it?▼

Write a context map listing every file to create or modify, the direct dependencies of each changed signature, existing and missing tests, a reference pattern to follow, and flagged risks. Review and approve the map before writing any code.

What should a change impact analysis include?▼

An impact analysis should include entry-point files, direct dependencies traced through imports and exports, test coverage status, at least one reference pattern from existing code, and explicit risks for public APIs, database migrations, and configuration changes.

How do I find which tests cover the code I am changing?▼

Identify unit and integration tests that already exercise the affected files and record them in the map. Where no test covers the target code, add a "test to write" line before programming to avoid regression risk.

When does a code change require a database migration?▼

A migration is required whenever the change modifies a JPA entity or database schema. The context map flags this by adding a db/migration line so the migration is planned alongside the code change.

What are the risks of changing a public API contract?▼

Changing a public /api/v1 contract extends the impact radius to every caller of that endpoint. The map requires listing all callers and planning an API compatibility note before the change is implemented.