Skills and agents for Claude Code that review merge requests, audit dependencies and handle everyday Git work.
Install only the plugins you need, or let /mwd:setup pick them with you.
Install · Plugins · Skills · Agents · Guides · Troubleshooting · Development
You need Claude Code. Each plugin also calls a few command-line tools, listed under Plugins. No MCP servers are needed.
This step is the same on every system. In a Claude Code session, run:
/plugin marketplace add mrwake-dev/claude-skills
/plugin install mwd@mrwake-dev
/reload-plugins
/mwd:setup
The first command registers this repo as a plugin source called mrwake-dev. The second installs mwd,
which holds only /mwd:setup. Setup asks which plugins you want, installs them, and checks the tools they
need. Run it again any time to add or remove plugins.
To skip setup, install a plugin directly, for example /plugin install mwd-review@mrwake-dev.
Every command and agent starts with its plugin's name: you run /mwd-review:code-review-interactive, and
the planner agent is mwd-agents:planner.
Claude Code downloads plugins over SSH when you have a GitHub SSH key, and over HTTPS otherwise. Installs and updates started inside a session don't switch to HTTPS on their own, so on a machine without a key, set this variable before you add the plugins:
# macOS and Linux: add it to your shell profile
export CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1# Windows: applies to terminals you open afterwards
setx CLAUDE_CODE_PLUGIN_PREFER_HTTPS 1Install only the tools your plugins need. /mwd:setup lists the ones that are missing.
git is usually installed already. Install the rest with Homebrew:
brew install gh glab jqOn Linux without Homebrew, take git and jq from your distribution, and gh from GitHub's own package
repository, as its Linux install guide
describes. GitLab supports glab on Linux only through Homebrew, so the commands below use community
packages for it.
Debian and Ubuntu, with glab from its community snap (on Debian, install
snapd first, or take a .deb from glab's releases):
sudo apt update && sudo apt install git jq -y
(type -p wget >/dev/null || (sudo apt update && sudo apt install wget -y)) \
&& sudo mkdir -p -m 755 /etc/apt/keyrings \
&& out=$(mktemp) && wget -nv -O$out https://cli.github.com/packages/githubcli-archive-keyring.gpg \
&& cat $out | sudo tee /etc/apt/keyrings/githubcli-archive-keyring.gpg > /dev/null \
&& sudo chmod go+r /etc/apt/keyrings/githubcli-archive-keyring.gpg \
&& sudo mkdir -p -m 755 /etc/apt/sources.list.d \
&& echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.list > /dev/null \
&& sudo apt update \
&& sudo apt install gh -y
sudo snap install glabFedora, where glab is a community package in the distribution's own repositories. These are the DNF5
commands; run dnf --version, and if it reports DNF4, use the DNF4 commands from GitHub's guide instead:
sudo dnf install git jq glab
sudo dnf install dnf5-plugins
sudo dnf config-manager addrepo --from-repofile=https://cli.github.com/packages/rpm/gh-cli.repo
sudo dnf install ghFor node, keep the one your version manager (such as nvm) already provides, or download it from
nodejs.org.
Log in to GitHub and GitLab once:
gh auth login # github.com
glab auth login # your GitLab instanceInstall Git for Windows first, whatever plugins you use. With it, Claude Code runs shell commands in Git Bash. Without it, Claude Code falls back to PowerShell, and the bash scripts these skills run won't work.
Install the rest with winget, in PowerShell:
winget install --id Git.Git -e
winget install --id GitHub.cli -e
winget install --id GLab.GLab -e
winget install --id jqlang.jq -e
winget install --id OpenJS.NodeJS.LTS -eSkip the last line if you already manage Node.js with nvm-windows. Then open a new terminal, so it finds the new commands, and log in once:
gh auth login
glab auth loginIf Claude Code can't find Git Bash, tell it where bash.exe is in
%USERPROFILE%\.claude\settings.json:
{
"env": {
"CLAUDE_CODE_GIT_BASH_PATH": "C:\\Program Files\\Git\\bin\\bash.exe"
}
}| Plugin | What it adds | Tools it needs |
|---|---|---|
mwd |
/mwd:setup, which installs the other plugins |
none |
mwd-review |
Interactive code review, report pages and six review agents | git, jq, gh and/or glab |
mwd-git |
Resolving review comments, updating merge requests, rebasing | git, jq, gh and/or glab |
mwd-security |
Dependabot fixes, Node.js and Java security audits | gh, jq, node |
mwd-cloudflare |
Preparing a website for Cloudflare Workers | node |
mwd-docs |
Trimming JSDoc comments, checking Markdown | git |
mwd-agents |
Seven general agents: explorer, simplifier, diff verifier, plan critic, planner, dead-code cleaner, test-gap finder | none |
gh covers GitHub and glab covers GitLab, so install the one for the platform you use, or both.
Run a skill by typing its command in a Claude Code session. Only /mwd-review:create-artifact can also
start on its own, when you ask Claude for a page or a dashboard. The guides cover each skill's options in
full.
| Command | What it does |
|---|---|
/mwd:setup |
Installs the plugins you pick, removes the ones you untick, and checks the tools they need. |
/mwd-review:code-review-interactive |
Reviews a merge request or pull request by its URL, or your branch with local, and posts the findings you approve as comments. Guide |
/mwd-review:create-artifact |
Turns what the session holds, such as a dashboard or a comparison, into a dark page at a private claude.ai link. Add bg=navy, oled, warm or a hex color for another background. |
/mwd-git:resolve-mr-comments |
Checks a merge request's review comments against the code and applies the fixes you pick, without committing. Guide |
/mwd-git:update-mr |
Writes the title and description of your branch's merge request from the diff and the session, and asks before posting. Guide |
/mwd-git:agent-rebase |
Rebases your branch onto its target, resolves simple conflicts and checks the build. It pushes only when you ask. Guide |
/mwd-security:fix-dependabot-alerts |
Upgrades the packages behind the Dependabot alerts you pick and runs the project's checks, without committing. Guide |
/mwd-security:node-security-audit |
Checks a Node.js project for vulnerable, outdated and deprecated packages and version conflicts, then writes a prioritized upgrade plan. |
/mwd-security:java-security-check |
Reviews a Java project for security problems and explains how to fix each one. |
/mwd-cloudflare:prepare-to-cf-workers |
Sets a website up for Cloudflare Workers, tests it locally and deploys once you confirm. Add a name for the Worker, or it takes the one in package.json. |
/mwd-docs:shorter-jsdocs |
Shortens or removes the JSDoc comments your branch touched. Add --committed or --uncommitted to check only one kind of change, or paths to narrow it down. |
/mwd-docs:markdown-check |
Checks a Markdown file's grammar and readability. Add the file's path, and its language if it isn't English. |
Claude Code can hand work to these agents. Ask for one by name, for example "use mwd-agents:planner", or let Claude pick.
| Agent | What it does |
|---|---|
mwd-agents:code-explorer |
Traces how an existing feature works across the codebase before you build on it. It only reads code. |
mwd-agents:code-simplifier |
Makes code clearer and more consistent without changing what it does. |
mwd-agents:diff-verifier |
Checks a finished change against your request: what it misses, what it changes beyond the request and what it left stale. It never edits files. |
mwd-agents:plan-critic |
Checks a plan against your request, the project's rules and the code before any code is written. It only reads code. |
mwd-agents:planner |
Turns a feature, an architecture change or a refactor into a step-by-step plan. |
mwd-agents:refactor-cleaner |
Finds unused code with knip, depcheck and ts-prune, and removes it. |
mwd-agents:test-gap |
Finds the behaviors a change adds or alters that no test covers. It writes those tests when you ask, touching test files only. |
mwd-review:* |
Six reviewers, one per area: correctness, security, docs, language, device and platform scripts. The code review skill starts them on large changes; you don't call them yourself. |
Every command starts with its plugin's name, so it's /mwd-review:code-review-interactive, not
/code-review-interactive. If the command is still missing, check that its plugin is installed and
enabled:
claude plugin listIf the plugin isn't listed, install it with /mwd:setup or claude plugin install <plugin>@mrwake-dev.
If it's listed but disabled, run claude plugin enable <plugin>@mrwake-dev. Then start a new session, or
run /reload-plugins in the current one.
The old symlinks from before the plugins are still in ~/.claude, so Claude Code loads each skill once
from them and once from a plugin. Check with ls -ld ~/.claude/skills ~/.claude/agents: an arrow
(->) means it's still a link. Replace the links as described in step 1 of
From the symlink setup.
Without Git Bash, Claude Code runs commands in PowerShell, where the skills' bash scripts don't work.
Install Git for Windows (winget install --id Git.Git -e) and restart Claude Code. If that doesn't help,
point Claude Code at bash.exe with CLAUDE_CODE_GIT_BASH_PATH, as shown in Windows.
gh or glab isn't logged in, or is logged in to a different server. Check both:
gh auth status
glab auth statusLog in with gh auth login or glab auth login. For a self-hosted GitLab, name the server:
glab auth login --hostname gitlab.example.com.
On a machine without a GitHub SSH key, installs started inside a session and plugin updates don't switch
to HTTPS on their own. Set CLAUDE_CODE_PLUGIN_PREFER_HTTPS=1, as shown in
Add the plugins, open a new terminal, and try again.
To remove one plugin and keep the rest, run /mwd:setup and untick it, or:
claude plugin uninstall mwd-review@mrwake-devTo remove everything, run this instead. It removes the marketplace and uninstalls every plugin from it:
claude plugin marketplace remove mrwake-devBoth commands work the same on macOS, Linux and Windows. The command-line tools from the install steps
stay installed; remove them with brew or winget if nothing else uses them.
Version 1 put every skill and agent into one plugin, mwd. From version 2, mwd holds only
/mwd:setup, and the skills and agents live in the plugins listed under Plugins. Update the
marketplace, reload, and run setup to pick the plugins you want:
/plugin marketplace update mrwake-dev
/reload-plugins
/mwd:setup
Every name changes:
| Version 1 | Version 2 |
|---|---|
/mwd:mwd-code-review-interactive |
/mwd-review:code-review-interactive |
/mwd:mwd-update-mr |
/mwd-git:update-mr |
mwd:planner agent |
mwd-agents:planner |
Update anything that still uses an old name, such as your CLAUDE.md, another skill's subagent_type
or a shell alias.
Older versions of this README told you to clone the repo and symlink its skills/ and agents/ folders
into ~/.claude. The plugins replace both, so once you've moved over you can delete the clone.
If you edit the skills, keep the clone: do step 1, add your clone as described in Working on the skills instead of step 2, and finish with step 4.
-
Replace the symlinks with real folders. First check that each one is a link to your clone (it shows an arrow,
->):ls -ld ~/.claude/skills ~/.claude/agents ~/.claude/commands rm ~/.claude/skills ~/.claude/agents mkdir ~/.claude/skills ~/.claude/agents
Without a trailing slash,
rmremoves only the link and leaves your clone alone. If~/.claude/commandsalso links to the clone, remove it the same way. The repo has nocommands/folder anymore, so that link points at nothing.On Windows, check the links in PowerShell and remove each one with
rmdir. It deletes a link, but refuses to delete a real folder that still has files in it:Get-Item "$env:USERPROFILE\.claude\skills", "$env:USERPROFILE\.claude\agents" | Select-Object FullName, LinkType, Target cmd /c rmdir "%USERPROFILE%\.claude\skills" cmd /c rmdir "%USERPROFILE%\.claude\agents" mkdir "$env:USERPROFILE\.claude\skills", "$env:USERPROFILE\.claude\agents"
If
LinkTypeis empty, that folder is a copy rather than a link. Rename it instead, and move back anything you still need. -
Add the plugins from GitHub, as described in Add the plugins, and pick the ones you want in
/mwd:setup. -
Delete the clone. Nothing loads from it anymore:
rm -rf ~/Documents/develop/mrwake-dev/claude-skills # wherever you cloned it
In PowerShell, run
Remove-Item -Recurse -Force <path-to-your-clone>. -
Switch to the new names. Start a new session, or run
/reload-plugins, and check thatclaude plugin listshows the plugins you picked as enabled. Every name now has its plugin's prefix:Before After /mwd-code-review-interactive/mwd-review:code-review-interactiveplanneragentmwd-agents:plannerUpdate anything that still uses an old name, such as your
CLAUDE.md, another skill'ssubagent_typeor a shell alias.
To undo the switch, run claude plugin marketplace remove mrwake-dev, which also uninstalls the plugins.
Then clone the repo again, move out anything you put in ~/.claude/skills and ~/.claude/agents,
delete both folders, and link the clone's skill and agent folders into ~/.claude.
Each plugin is a folder under plugins/, with its skills in skills/<name>/SKILL.md and its agents in
agents/<name>.md. To edit them, clone this repo and add your clone instead of GitHub:
/plugin marketplace add <path-to-your-clone>
Claude Code then reads every plugin straight from your clone, so /reload-plugins picks up an edit
without waiting for a release. Pick "All six plugins" in /mwd:setup to have everything installed.
The contributing guide covers naming, the frontmatter fields, the rules every skill follows, and the commit format the release notes depend on.
All plugins share one version number, set in each plugins/*/.claude-plugin/plugin.json. You get a new
version only when a release raises it; commits pushed to main between releases don't reach installed
copies. A plugin added from a local clone is the exception: it always uses the files on disk. Each
version's changes are listed on the Releases page.
Automatic updates are off until you turn them on. Open /plugin, go to Marketplaces, select
mrwake-dev and choose Enable auto-update. To update by hand instead, run:
/plugin marketplace update mrwake-dev
Run the Release workflow on main and choose patch, minor or major, either from the repo's
Actions tab or with:
gh workflow run release.yml -f bump=patchThe workflow raises the version in every plugin's plugin.json, commits them as release: X.Y.Z, tags
the commit X.Y.Z and pushes both. It stops first if the plugins don't all have the same version. It then
starts the Changelog workflow, which publishes a GitHub release. The release notes list the commits
since the previous tag, grouped by type: feat, fix, docs and so on.
You can also push an X.Y.Z tag yourself. Changelog publishes a release for it only if
plugins/mwd/.claude-plugin/plugin.json at that tag already has the same version, because installed
copies would never get it otherwise.