Help us improve
Share bugs, ideas, or general feedback.
From doc-mirror
WHAT: the install/setup WIZARD for the doc-mirror plugin — it places doc-mirror's command-line tools (journal, vision, cursor, commit, search) on your PATH and records where the plugin lives, performing the host setup itself and telling you exactly what to run if the environment blocks it; non-destructive. WHEN: right after installing or enabling the doc-mirror plugin (first-time setup), or when a doc-mirror command is 'command not found', or when 'docmirror search' cannot find its prompt store (any of).
npx claudepluginhub sancovp/doc-mirror --plugin doc-mirrorHow this skill is triggered — by the user, by Claude, or both
Slash command
/doc-mirror:doc-mirror-installThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This is a **WIZARD**: *you (the agent) perform the host-level setup yourself*, verify it at the surface,
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
This is a WIZARD: you (the agent) perform the host-level setup yourself, verify it at the surface, and — only if the environment blocks you — tell the user the exact command to run. It is non-destructive: it places doc-mirror's CLI tools on PATH and records where the plugin lives. It writes only those, and deletes nothing.
When the doc-mirror plugin is enabled, Claude Code auto-discovers its skills/, hooks/hooks.json,
and rules/ straight from the plugin dir — those need no setup. Exactly two things a plugin manifest
cannot place, which this wizard handles:
bin/ CLIs (journal, vision, docmirror-cursor, doc-mirror-commit, docmirror search,
plan, projects, tracker, docmirror-sleep, …) must be on your PATH to be invocable;docmirror search bin runs as a host CLI (it does not receive CLAUDE_PLUGIN_ROOT at
call time), so it needs ~/.docmirror_plugin_root written to find the plugin's prompt store.<plugin-root>/skills/doc-mirror-install/. (If $CLAUDE_PLUGIN_ROOT is set in your shell, that is
the plugin root.) Confirm <plugin-root>/install.sh exists.bash "<plugin-root>/install.sh"
Read its output: it reports where it placed the bins, that it recorded the plugin root, and whether
your PATH needs an edit.docmirror-cursor show # a bin resolves on PATH
docmirror search "doc-mirror" --corpus prompts --limit 3 # the search bin finds the plugin's prompts
Both must succeed. "command not found" means PATH isn't updated in this shell yet.echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc && source ~/.bashrc, then re-verify.~/.local/bin not writable → have them re-run with a writable dir and add it to PATH:
DOCMIRROR_BIN_DST=<dir> bash "<plugin-root>/install.sh".docmirror-cursor show and docmirror search … --corpus prompts both work in a fresh shell. doc-mirror
is now operable — start any session with the doc-mirror-boot skill, which cascades everything else.