consumer-map

Overview

consumer-map is a pure decision-support skill. It never edits files, never commits changes, and never dispatches write-path skills. Its sole artifact is an Impact Report with a machine-readable verdict.

Two input modes, one pipeline:

• Diff mode — pass a PR number, patch file, or git diff output. The skill parses the diff to extract files_touched and symbols_changed, then maps their consumer surface. Use when you have a change and want to know what it hits.
• Target mode — pass a symbol name, module path, config key, environment variable, API endpoint, or schema column. The skill resolves the target to concrete file paths and exported symbols, then maps their consumer surface. Use when you are considering a change and want to know who depends on the target.

If the input is ambiguous — a bare number that could be a PR or a line count, a name that matches multiple distinct entities — the skill stops and asks for disambiguation before dispatching any probes.

---

Wave 1 — Input normalization (inline, ≤5 tool calls, no agent dispatch)

Diff mode: Fetch the diff artifact (via git diff, gh pr diff <N>, or a passed file path) and parse it directly. Emit a structured manifest:

{ "files_touched": [...], "symbols_changed": [...], "hunk_map": { "<file>": [[start, end], ...] } }

symbols_changed captures: functions renamed or deleted, exported types modified, function signatures altered. If no diff artifact is obtainable:

BLOCKED: no diff artifact — run \git diff` or `gh pr diff ` and pass the output, or use target mode with a symbol name`

Target mode: Resolve <target> to a canonical name, source file, and type (function / module / type / config key / env var / schema column / other). Populate files_touched with the target's source file(s) and symbols_changed with the target's exported names.

If <target> is ambiguous — multiple symbols share the name across packages or the string matches more than one distinct entity — halt immediately and request disambiguation. Do not guess.