Skip to content

RepoMagpie 0.3.0

Latest

Choose a tag to compare

@Varshavia Varshavia released this 13 Nov 17:31
· 4 commits to main since this release
45ddefb

RepoMagpie 0.3.0

RepoMagpie installs as a Claude Code plugin: the skill, the MCP server and the install hook in one step, with no repomagpie setup. This release also fixes the hook on older Claude Code versions, and brings three fixes from an outside contributor.

Install or upgrade

You need Node.js 22.12 or later.

npm install -g repomagpie
repomagpie --version
repomagpie setup

repomagpie --version prints 0.3.0. Your notes need no changes. Run repomagpie setup again. The installed skill's version changed, and if your Claude Code is older than 2.1.139, setup now writes a hook that runs there.

The Claude Code plugin

In Claude Code:

/plugin marketplace add Varshavia/RepoMagpie
/plugin install repomagpie@repomagpie

Claude Code fetches the repomagpie package from npm, at the version this repository's marketplace lists. The marketplace is added to this repository right after this release, listing 0.3.0.

  • It needs Node.js 22.12 or later on PATH. The plugin starts node by name for the hook and the MCP server. Run node --version where you start Claude Code.
  • The note tool is off by default. The plugin reads your notes. To let Claude save your Verdicts, turn on Note tool in /config and restart Claude Code. Claude then saves only your words and never replaces a Verdict. Claude Code doesn't ask before each save.
  • It doesn't add the repomagpie command. For repomagpie note, ui, discover, doctor and your other agents, install the npm package too.
  • repomagpie setup skips Claude Code while the plugin is on. If an earlier setup wrote the entries, the plan lists them and names repomagpie setup --remove --agents claude-code; setup never removes them on its own.
  • repomagpie doctor has a "Claude Code plugin" section. It shows where the plugin is on or off, which versions are installed, and whether Claude Code runs it. One to-do says when both the plugin and an earlier setup are there. A version Claude Code left in its cache after an uninstall is a cached copy, not installed.

The README lists everything RepoMagpie runs, sends and fetches, the same for the plugin and the npm install: the hook and the MCP server never use the network.

Fixes

  • The hook on Claude Code older than 2.1.139. setup always wrote the hook's exec form (command and args), which those versions don't have, so the hook could silently never run. setup now reads claude --version and writes the shell form below 2.1.139. doctor prints Claude Code's version and each entry's form, with a FAIL: line when an exec-form entry can't run.
  • The install detector skips more flag values. The values of npm's --before, --cpu, --os, --libc and --scope, and of several uv flags, were read as package names. uv add --no-binary requests and uv remove --no-binary requests still find requests.
  • The hook help points to repomagpie setup. repomagpie hook <agent> --help said RepoMagpie never edits a settings file. It now says setup writes the entry for you, and gives the snippet for writing it by hand.

From 0.3.0-beta.1

The plugin's "Note tool" switch was on by default in the beta, on the assumption that Claude Code would ask about it when the plugin is turned on and before each save. Claude Code 2.1.323 does neither, so it is now off by default. If you turned it on, it stays on; turn it off in /config if you want.

Thanks

Thanks to @bfs2021, RepoMagpie's first outside contributor, for the install detector's flag values (#114), the hook help (#116) and the uv add --no-binary fix (#117).

Every change is in the changelog.