Menü
Use when an agent needs deterministic local churn, clone, or complexity facts from Miller without adding MCP tool surface.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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 assessing blast radius with Miller, choosing tests for a change, answering who uses a symbol, or planning a refactor.
| name | miller-metrics-audit |
| description | Use when an agent needs deterministic local churn, clone, or complexity facts from Miller without adding MCP tool surface. |
| user-invocable | true |
| arguments | <workspace selector, commit range, or metric kind> |
| allowed-tools | Bash, mcp__miller__workspace |
Use the miller metrics CLI family for deterministic local reports that are useful in review, refactor planning,
or backlog triage. Metrics are CLI-only; do not call or describe an MCP metrics tool.
Run from the target workspace, or pass --workspace-id <selector> / --workspace <path> for a registered
workspace:
miller metrics churn --range HEAD~20..HEAD --limit 25 --json
miller metrics clones --min-count 2 --limit 25 --json
miller metrics complexity --min-severity moderate --exclude-tests --limit 25 --json
For a source checkout without miller on PATH, use the built binary if present:
src/Miller.Server/bin/Release/net10.0/miller metrics complexity --json
body_hash groups from the extractor, not semantic similarity.Keep the summary factual:
--min-count, --min-severity, and test inclusion