Menú
Use when assessing blast radius with Miller, choosing tests for a change, answering who uses a symbol, or planning a refactor.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use before changing existing indexed files with Miller edit, especially symbol rewrites, text replacements, renames, or refactors.
Use when an agent needs extractor-recognized code-shape facts such as routes, htmx attributes, Alpine directives, SQL DDL/DML, or data-document structure.
Use when starting a Miller task, choosing a Miller tool, or choosing a Miller search mode.
Use when tracing Miller bridge paths in supported providers: dotnet-web URL literals and fetch/axios client requests to ASP.NET signals, client requests to Next.js route handlers or Nuxt server routes, Next.js/Nuxt route references to file routes, Vue/React references to route definitions, or backend-http client requests to Express/FastAPI/Flask/Django/Spring/Go/gin/echo/Rails/NestJS/Laravel/Phoenix/axum/actix/Symfony/Ktor route facts.
Use when orienting on an unfamiliar code area with Miller, explaining a module, finding entry points, or gathering context before a change.
Use when resuming Miller-backed work from a handoff packet or validating a packet before continuing in another harness, model, or session.
| name | miller-impact-analysis |
| description | Use when assessing blast radius with Miller, choosing tests for a change, answering who uses a symbol, or planning a refactor. |
| user-invocable | true |
| arguments | <symbol, file path, diff, or change target> |
| allowed-tools | mcp__miller__impact, mcp__miller__search, mcp__miller__inspect, mcp__miller__trace, mcp__miller__context, mcp__miller__workspace |
Use Miller's graph-backed impact tool before refactors or shared behavior changes. One impact call should replace manual reference greps.
search(query="<symbol or concept>")
inspect(target="<candidate>")
impact()
impact(target="<symbol-or-file>")
impact(changed_paths=["<file1>", "<file2>"])
impact(diff="<unified diff>")
With no args, impact() reads the working-tree git diff and maps changed ranges to impacted symbols plus likely
tests — run it after edits, before committing, to see what your uncommitted change affects. Use git=true
(base/staged imply git) to scope to a specific git diff instead.
inspect(target="<impacted-symbol>", depth="full")
trace(target="<impacted-symbol>")
trace(target="<source>", mode="path", to="<sink>")
impact reports likely tests, treat that list as the starting verification set. Add broader tests when the touched surface is shared infrastructure or cross-workspace behavior.Lead with:
Do not replace impact with rg unless Miller cannot resolve the target.