context-map

Generate a context map of files, dependencies, tests, and documentation for a task.

Updated Dec 13, 2023
One-click install
npx skills add https://github.com/ranma2913/echo-api --skill context-map
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-map
Source: https://github.com/ranma2913/echo-api/tree/main/.github/skills/context-map
Command: npx skills add https://github.com/ranma2913/echo-api --skill context-map

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

An engineer often needs a clear, up-to-date map of a codebase before making changes to reduce risk and accelerate review.

Core Features & Use Cases

  • Generate a comprehensive inventory of files and modules related to a task.
  • Identify direct dependencies (imports/exports), related tests, and relevant references.
  • Provide a concise, actionable plan to guide changes and minimize regressions.

Quick Start

Inspect the repository and run the context-map skill to produce a map for the current task.

Frequently Asked Questions about context-map

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

FAQPage Schema
How do I map codebase dependencies before making changes?

A codebase context map inventories all files relevant to a task, identifies direct dependencies and related tests, and provides an actionable plan to guide changes and minimize regression risk.

What is the best way to identify related tests and documentation for a code change?

A context map scopes to the touched areas of a codebase, extracts direct dependencies, related tests, and relevant references to provide an actionable plan for reviewers and implementers.

How do I reduce regression risk when modifying a codebase?

Reduce regression risk by generating a comprehensive context map of all task-related files and modules, ensuring changes are scoped to touched areas and guided by an actionable plan.

Can I scope codebase analysis to only the files affected by my current task?

Yes, a context map scopes to the touched areas of a codebase, inventories only the modules related to your current task, and ensures the map is actionable for implementers and reviewers.

Do I need any external dependencies to generate a task context map?

No external dependencies are required to generate a task context map; the skill operates independently to inspect your repository and produce an actionable inventory of relevant files.

Why does my codebase need an inventory before implementing changes?

Your codebase needs an inventory before changes to provide a clear, up-to-date map of relevant files, which accelerates review and reduces the risk of introducing regressions.