memtrace-impactlisted
Install: claude install-skill syncable-dev/memtrace-public
## Overview
Compute the blast radius of changing a specific symbol. Traces upstream (what depends on this) and downstream (what this depends on) through the knowledge graph to quantify risk before making modifications.
## Quick Reference
| Tool | Purpose |
|------|---------|
| `get_impact` | Blast radius from a symbol **name** (`target`) |
| `detect_changes` | Scope symbols affected by a diff/patch |
> **Parameter types:** MCP parameters are strictly typed. Numbers (`depth`, `limit`, etc.) must be JSON numbers — not strings.
## Required parameters — `get_impact`
| Parameter | Required | Default | Notes |
|---|---|---|---|
| `repo_id` | yes | — | |
| `target` | yes | — | Symbol name (e.g. `"validateToken"`) — **not** `symbol_id` |
| `direction` | no | `"both"` | `"upstream"` \| `"downstream"` \| `"both"` |
| `depth` | no | `5` | BFS depth (max 15) |
| `as_of` | no | now | ISO-8601 for time-travel |
```json
{ "repo_id": "memdb", "target": "validateToken", "direction": "both", "depth": 5 }
```
Full parameter spec for every Memtrace tool: `references/mcp-parameters.md` (bundled at the memtrace-skills plugin root).
## Steps
### 1. Identify the symbol name
If you don't know the exact name:
- `find_symbol(name="...")` for exact identifiers
- `find_code(query="...")` for natural-language queries
Use the returned **`name`** (and optional `file_path` hint) — graph tools resolve by name, not internal IDs.
### 2. Run impact analysis
```json
{
"repo_id": "memdb",
"target