repowiseAgent plugins
The Claude Code and Codex plugins bundle the MCP server, lifecycle hooks, skills, and slash commands into one install. What each plugin ships, how to install it, and what activates when.
Repowise ships two agent plugins. Both bundle the MCP server, lifecycle hooks, and a set of skills into a single install, so you do not wire up each piece by hand.
| Claude Code | Codex | |
|---|---|---|
| MCP server | Yes | Yes |
| Lifecycle hooks | Yes | Yes, opt-in in current Codex releases |
| Skills | 6 | 6 |
| Slash commands | 18 | None, Codex has no equivalent |
| Install source | Public marketplace | Local marketplace from a repo clone |
Both are AGPL-3.0 and live in the
OSS repo under plugins/.
A plugin is the convenience, not the requirement. Everything it wires up
works standalone: repowise init already registers the MCP server and
writes .mcp.json for you. See
Set up with your agent if you just want
the shortest path.
Claude Code plugin
/plugin marketplace add repowise-dev/repowise
/plugin install repowise@repowiseThat is the whole install. It brings the MCP server, 18 slash commands, six skills, and three hooks.
Slash commands
Explicit, you type them. Each maps to a CLI command and formats the result for reading rather than parsing.
| Command | What it does |
|---|---|
/repowise:ask | Ask a codebase question and get a cited, synthesized answer with a confidence rating. Costs an LLM call. |
/repowise:context | Triage card for a file, module, or symbol: layer, hotspot, fix history, freshness. |
/repowise:coverage | Ingest or inspect test-coverage reports, so untested-hotspot markers and impacted-tests work. |
/repowise:dead-code | Unreachable files, unused exports, and zombie packages, tiered by confidence. |
/repowise:decision | Architectural decisions: list, inspect health, add, or confirm auto-proposed ones. |
/repowise:doctor | Diagnose the setup (install, keys, index drift) and optionally repair it. |
/repowise:export | Export the wiki, or an architecture model, to markdown, HTML, JSON, or Structurizr DSL. |
/repowise:health | Code health: KPIs, lowest-scoring files, refactoring targets, trends, per-file markers. |
/repowise:impacted-tests | Tests whose coverage intersects a change's changed lines, for a commit, range, or staged diff. |
/repowise:init | Set up repowise here. Installs the CLI if needed, asks about preferences, runs the indexing. |
/repowise:reindex | Rebuild the vector store by re-embedding wiki pages. No LLM calls, embeddings only. |
/repowise:risk | Defect risk for a commit or a base..head range, as a 0 to 10 score with drivers. |
/repowise:search | Search the wiki by natural language, full text, or symbol. |
/repowise:security | Scan for security signals. Use --history to walk full git history for leaked secrets. |
/repowise:status | Index health: sync state, page counts, provider, token usage. |
/repowise:symbol | Read one function, class, or constant's body with live-verified line bounds. |
/repowise:update | Incremental update so the docs match recent commits. |
/repowise:why | Why the code is shaped this way: decisions, rationale, and git archaeology. |
Skills
Implicit, they activate on their own when the work matches. Each checks for
a .repowise/ directory first and stays out of the way if the repo is not
indexed, so installing the plugin globally does no harm in unindexed repos.
| Skill | Activates when |
|---|---|
codebase-exploration | Understanding or explaining a codebase: how does X work, where is Y implemented, what does this module do. |
pre-modification-check | Before editing, refactoring, or deleting files, especially shared utilities and core modules the user did not name. |
change-review | Reviewing a PR, a branch diff, or working-tree changes before they merge. Blast radius, missing co-changes, test gaps. |
architectural-decisions | Questions about why code is built a certain way, or before diverging from an established pattern. |
code-health | Quality, complexity, technical debt, what to refactor next, untested hotspots, coverage gaps. |
dead-code-cleanup | Cleanup, removing unused code, reducing bundle size, repository hygiene. |
Hooks
Three, all calling the repowise-augment entry point:
| Hook | Fires on | Why |
|---|---|---|
SessionStart | startup, resume, clear | The session opens with repo context already loaded, so the first question does not cost a round-trip. |
PostToolUse | Grep, Glob, Read, Edit, Write, and repowise MCP calls | Nudges the agent toward the index after file and search operations, and flags when a git operation has made the wiki stale. |
PostToolUseFailure | Read, Edit, Write, Grep, Glob, NotebookEdit | Checks codebase context after a failed file operation, so a bad path or stale assumption gets caught before the agent retries blind. |
Claude Code also gets search-result enrichment on Grep and Glob, which
the Codex setup does not attempt. Full detail in
Agent hooks.
Codex plugin
Repowise supports Codex three separate ways, and they are worth keeping apart:
- Project setup for Codex MCP and lifecycle hooks, via
repowise init --codex. - The
codex_cliprovider, which generates wiki pages through your authenticated Codex CLI subscription instead of an API key. - The plugin, which bundles MCP, hooks, and skills.
Prerequisites
npm install -g @openai/codex
codex login
codex login statusRepowise checks codex --version and codex login status. When both
succeed, interactive repowise init offers Codex project setup.
Non-interactive runs need --codex explicitly; --no-codex skips the
prompt.
Project setup
repowise init --codexThis writes project-local files, not your global
~/.codex/config.toml. It merges into .codex/config.toml:
[mcp_servers.repowise]
command = "repowise"
args = ["mcp"]
cwd = "/absolute/path/to/repo"
startup_timeout_sec = 20
[features]
hooks = trueThe server runs repowise mcp with no path argument. In no-path mode it
walks upward from the current directory to the nearest initialized
.repowise repo. Smoke check with codex mcp list.
Installing the plugin
The Codex plugin installs from a local marketplace rather than a public one, so you need a clone of the repo:
git clone https://github.com/repowise-dev/repowise
cd repowise
codex plugin marketplace add .
codex
/pluginsIt bundles the MCP server, lifecycle hooks, and the same six skills in Codex-neutral form. It adds no slash commands, because Codex has no equivalent surface.
Plugin-bundled hooks are opt-in in current Codex releases. Set
[features] plugin_hooks = true if you want hooks loaded from an installed
plugin. Hooks written by repowise init --codex land in
.codex/hooks.json and are not subject to that flag.
Codex hooks
Written to .codex/hooks.json, not inline [hooks] tables:
| Hook | Fires on | Why |
|---|---|---|
SessionStart | startup, resume, clear | Adds repowise MCP workflow guidance. |
UserPromptSubmit | Every prompt | Reminds Codex that repowise context is available. |
PostToolUse | Bash | Detects git operations that make the wiki stale. |
PostToolUse | apply_patch, Edit, Write | Reminds Codex after edits. |
The codex_cli provider
Worth knowing about even if you skip the plugin. It routes page generation through your Codex subscription instead of a metered API key:
repowise init --provider codex_cli --codex --yesRepowise treats codex_cli/* cost as $0.00, because subscription billing
happens outside its API pricing. --reasoning minimal maps to Codex
model_reasoning_effort="low"; low, medium, high and xhigh pass
through when the selected model advertises them. off and none are not
supported by this provider.
AGENTS.md
repowise init --codex generates a managed AGENTS.md by default, the
Codex counterpart to the generated CLAUDE.md. repowise update refreshes
it when editor_files.agents_md is enabled or --agents is passed. The
repowise section sits between managed markers and your own content outside
those markers is preserved.
repowise init --no-agents # skip it
repowise init --agents # force it
repowise update --agents # refresh on updateWhich to install
Install the plugin. The slash commands and skills are the difference between having the tools available and actually having them used at the right moment, and it is a two-line install.
Run repowise init --codex first, since that is the part that wires MCP
and hooks into the project and needs no clone. Add the plugin on top if you
want the skills as well.
There is no plugin, but nothing is lost: point your client at
repowise mcp over stdio and you get the same tools. See
Set up with your agent.
Set up with your agent
Hand this page to Claude Code, Cursor, Codex, or any coding agent and it can install repowise, index the repo, and wire up MCP on its own. Includes copy-pasteable prompts, the Claude Code plugin, slash commands, skills, and machine-readable docs endpoints.
VS Code extension
The Repowise extension brings the local index into VS Code (editor-native health signals, refactoring CodeLens, branch risk, in-editor dashboards) and registers the Repowise MCP server so the same index serves both you and your AI agent.