From miller
Use when querying another registered workspace with Miller, comparing repos, opening a workspace, or routing search/inspect/context/impact/trace through workspace_id.
How this skill is triggered — by the user, by Claude, or both
Slash command
/miller:miller-cross-workspace<workspacepath,displayid,orcross-repotask>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Miller can read registered workspaces without changing directories. Use `workspace_id` on read tools instead of shelling into another repo.
Miller can read registered workspaces without changing directories. Use workspace_id on read tools instead of shelling into another repo.
List known workspaces:
workspace(operation="list")
Valid workspace_id selectors:
currentprimaryPrime a repo that is not registered yet:
workspace(operation="open", path="<absolute-root>")
workspace open primes the index; it does not switch the live MCP server workspace.
Pass the selector to the read tool:
search(workspace_id="<selector>", query="<query>")
inspect(workspace_id="<selector>", target="<symbol-or-file>")
context(workspace_id="<selector>", query="<task>")
impact(workspace_id="<selector>", target="<symbol-or-file>")
trace(workspace_id="<selector>", target="<symbol>")
Explicit workspace_id defaults to refresh-first. Set ensure_fresh=false only when a fast, possibly stale read is acceptable.
Mention:
Do not manually cd and repeat shell searches when a Miller read tool can route to the workspace.
npx claudepluginhub anortham/miller --plugin millerGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.