Menu
Update Muggle AI to latest version. Use when user types muggle upgrade or asks to update Muggle Test tools.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | muggle-upgrade |
| model | haiku |
| description | Update Muggle AI to latest version. Use when user types muggle upgrade or asks to update Muggle Test tools. |
Telemetry first step: see
_shared/telemetry-emit.md. UseskillName: "muggle-upgrade".
Update all Muggle AI components to the latest published version. This means both the @muggleai/works CLI on npm and the Electron runner the CLI manages.
Run /muggle:muggle-status checks to capture current versions.
Capture CLI versions:
muggle --versionnpm view @muggleai/works versionnpm ls -g @muggleai/works --depth=0 (falls back to pnpm ls -g @muggleai/works if not found)If installed CLI < latest on npm, upgrade the CLI itself before touching Electron:
npm install -g @muggleai/works@latestpnpm add -g @muggleai/works@latestRun muggle upgrade to pull the Electron runner version that the (now-latest) CLI expects.
muggle upgrade only manages the Electron runner — it does NOT upgrade the CLI npm package. That is why step 3 must run first.Reload plugins — the npm install (step 3) triggers a postinstall script that updates the plugin cache at ~/.claude/plugins/cache/, but Claude Code only picks up new skills/agents/hooks after a reload. Tell the user:
Run
/reload-pluginsto load the updated skills, agents, and hooks.
Wait for the user to confirm they've reloaded before proceeding.
Run /muggle:muggle-status again to confirm everything is healthy after upgrade.
Show a before/after table for CLI, Electron runner, MCP server, and Auth. Call out any version that did not change so the user understands what shipped vs what was already current.
If any component upgraded, always end with the /reload-plugins reminder — even if the user doesn't need new features right away, stale cached skills can cause confusing behavior.
If the upgrade fails at any step, report the error and suggest running /muggle:muggle-repair.
Use when the user wants a pull request's incoming review feedback handled for them — it watches one PR's review thread and, each time a reviewer submits new comments, dispatches the work to address them. Engage on PR-review-follow-up intent: "watch my PR and address review comments as they come in", "keep an eye on PR #123 and respond to reviewer feedback", "babysit my PR's review thread", "I'm stepping away — handle my PR's reviews while I'm gone". This is PR-review-specific automation — prefer it over the generic loop skill. It only watches and dispatches; the actual edits and replies are muggle-do. Not for posting test results to a PR (use muggle-pr-visual-walkthrough).
Take a feature request, spec, design, bug, or ticket and carry it autonomously to an opened pull request — write the code, test it, raise the PR. Use whenever the user wants something built, implemented, added, or fixed with a PR opened, raised, or put up at the end — "implement rate limiting and raise a PR", "build the CSV export and put up a PR", "take this Jira ticket and run with it, ping me when the PR is up", "fix this bug and open a pr", or "muggle do …". Also handles the internal `address-reviews` directive the muggle-pr-followup watcher dispatches when new reviews land. Not for testing or validating existing changes (use muggle-test), nor watching a PR's incoming reviews (use muggle-pr-followup).
View, set, or reset Muggle AI preferences that control testing behavior. Use when user asks to see preferences, change a setting, configure Muggle Test defaults, or manage muggle config. Triggers on: 'muggle preferences', 'show muggle settings', 'change muggle preference', 'set autoLogin to always', 'muggle config', 'reset muggle preferences', 'show my muggle settings', 'configure muggle', 'muggle setup'.
Run a real-browser end-to-end (E2E) acceptance test against localhost to verify a feature works correctly — signup flows, checkout, form validation, UI interactions, or any user-facing behavior. Launches a browser that executes test steps and captures screenshots. Use this skill whenever the user asks to test, validate, or verify their web app, UI changes, user flows, or frontend behavior on localhost or a dev server — even if they don't mention 'muggle' or 'E2E' explicitly.
Cut @muggleai/works release: AskUserQuestion (major/minor/patch), sync master, stop if nothing ships, semver baseline + Electron from GitHub, confirm plan, bump package.json + sync:versions, full local verify, chore(release) PR, merge via gh, dispatch publish-works-to-npm.yml—no local npm publish.
Use when the user wants to flag that a generated Muggle Test action script — or one specific step in it — did the wrong thing, so Muggle can analyze and regenerate affected scripts. Covers any report that a script or step is wrong, broken, or misbehaving (clicked the wrong element, step N did not work, broken at the submit step), whether from a recent local/remote run or a pasted Muggle dashboard run/script URL. Also lists, views, or deletes previously submitted feedback. Triggers on /muggle-feedback, give feedback on this run, the test was wrong, flag this run.