Superpowers was already one of GitHub’s most prominent developer tools. With v5.1.0, Jesse Vincent did something counterintuitive: instead of adding features, he cleaned house.
What is Superpowers (quick context)
If you read our previous coverage, you already know the concept: Superpowers is a set of composable skill markdown files that automatically load into your code agent. It enforces a mandatory Design → Plan → Implement → Review workflow — the agent can’t skip steps. It works with Claude Code, Cursor, Codex CLI, Gemini CLI, GitHub Copilot CLI, and OpenCode.
The number that proves this isn’t hype: 189,000 stars on GitHub and over 15,600 forks.
What actually changed in v5.1.0
The release came out on May 4, 2026. Three concrete changes:
1. Git worktrees rewritten from scratch
Claude Code and Codex now have native first-class support for git worktrees, and v5.1.0 takes advantage of it. The finishing-a-development-branch skill now only cleans up worktrees within .worktrees/ — the ones Superpowers itself created. Everything outside that path stays untouched. This closes a real group of bugs: worktrees being cleaned in the wrong order (#999), the agent running git worktree remove from the wrong directory (#238), and incorrect cleanup when the branch had no merge target (#940). If Superpowers ever touched worktrees it shouldn’t have, this is the fix.
2. Legacy slash commands removed
/brainstorm, /execute-plan, and /write-plan are gone. They were deprecated stubs — literally just telling you to call the corresponding skill directly. Now you call superpowers:brainstorming, superpowers:executing-plans, and superpowers:writing-plans without the middleman. Less confusion, smaller footprint.
3. The code reviewer subagent is now just a subagent
This change matters architecturally. Superpowers used to include a named agent (superpowers:code-reviewer) — the only named agent in the entire plugin. It was eliminated. The reviewer logic now lives as a self-contained Task-dispatch template within skills/requesting-code-review/code-reviewer.md. All other subagents in the repo already worked this way; now they’re consistent. The practical effect: one less platform-specific dependency, and the review logic is easier to inspect and modify.
One detail worth knowing: the AI-slop problem
The v5.1.0 release notes include something that isn’t a code change, but says a lot about the project’s health. The maintainers audited the last 100 closed PRs and found a rejection rate of 94% — driven almost entirely by AI-generated contributions that didn’t read the PR template, opened duplicates, or submitted changes that only made sense for a specific fork.
They now added two sections to CLAUDE.md (symlinked to AGENTS.md) that speak directly to AI agents trying to contribute. It’s a project that builds tools for AI agents, dealing with AI agents trying to contribute to it. Worth knowing.
Do you need to reinstall?
If you already have Superpowers installed via the Claude Code marketplace, skills update automatically when you log in — you don’t need to do anything. If you installed manually or via Codex, check the updated installation instructions in the README. The sync-to-codex-plugin script that syncs Superpowers with OpenAI’s Codex plugin marketplace is new in this release and works without depending on specific paths or users.
Installation
# Claude Code
/plugin install superpowers@claude-plugins-official
# Cursor
/add-plugin superpowers
# Gemini CLI
gemini extensions install https://github.com/obra/superpowers
For Codex and OpenCode, follow the updated instructions in the repo README.
The bottom line
v5.1.0 isn’t a feature release. It’s the kind of release a mature open source project makes when it has enough confidence in its core to simplify rather than expand: cleaner worktree handling, fewer abstractions, smaller platform-specific surface area. The methodology didn’t change — Design before Plan, Plan before Code, Code before Merge — but the machinery is tighter.
With 189K stars, Superpowers is clearly doing something right. Whether that something is right for your workflow is a separate question — and one the community is still debating.
Are you already using Superpowers in your projects? What workflow did you end up adopting? Let us know in the comments.