Optimus plugin
A plugin that readies a project for Claude Code: guidance, tests, review, TDD, refactoring and a resumable fix loop
- 75 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Skills change code, create commits and PRs, and `deep` does so in iterations without stopping at every step
- The session-start hook runs on every start and needs your approval in Codex
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/optimusDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Skills change code, create commits and PRs, and `deep` does so in iterations without stopping at every step
- The session-start hook runs on every start and needs your approval in Codex
This is third-party code. Review the repository files before installing.
What it does
The plugin reads your repository and `/optimus:init` creates project guidance, code rules and a test harness: a `CLAUDE.md` file and documents in `.claude/`, per package for monorepos. Every quality pass afterwards relies on those rules, with no generic advice. There are about twenty skills. `/optimus:code-review` checks local changes or a PR for bugs, vulnerabilities and rule violations, `/optimus:refactor` improves code against project rules, `/optimus:tdd` walks a task through Red-Green-Refactor cycles with commits per behavior and `/optimus:unit-test` finds coverage gaps. `/optimus:deep` repeats review, refactoring or a coverage pass and `/optimus:gauntlet` drives a goal through builder and critic iterations. Separate skills handle commits, PRs and MRs, isolated git worktrees, handing context to a fresh agent, Jira tasks and prompt preparation. For Codex the plugin is experimental, and `permissions`, `dream` and formatter installation work only in Claude Code.
Who it is for. Developers who run a project with Claude Code and want a shared set of rules, tests and quality passes in place of ad-hoc prompts.
Good fit when
- A new repository needs `CLAUDE.md`, code rules and test infrastructure quickly
- Before merging you want changes or a PR checked for bugs and project rule violations
- You want a task carried through TDD with a commit per behavior
- A long project cleanup should run as repeatable passes with a progress report
Not a fit when
- You need one narrow tool: the plugin brings about twenty skills and its own session-start hook
- The project is not under git or you have no Bash: Git and Bash are required to install and run
- You need Codex with no limits: support there is experimental
Example request
Run `/optimus:init` in this project, then `/optimus:code-review` on my local changesLimitations
Installation needs Git and Bash; on Windows install Git for Windows first. The session-start hook in Codex must be reviewed and approved by hand through `/hooks`, as installation alone grants no trust. Codex support is experimental, and `permissions`, `dream` and formatters work only in Claude Code. The author recorded checks as of 9 September 2026 and states they do not guarantee every workflow works. Results of `deep` and `gauntlet` are worth reviewing commit by commit, since they change code in iterations.
How to disable. In Claude Code run `/optimus:reset` to remove the generated setup, then `/plugin uninstall optimus@optimus-claude`. In Codex use the CLI plugin management.
FAQ
Which command comes first?
`/optimus:init` in a new session inside the project. It reads the code and creates the guidance, rules and test harness that the other skills build on.
How is deep different from a regular review?
`deep` repeats review, refactoring or coverage passes automatically, fixes findings, writes tests and saves progress so the loop can be resumed.
Does the plugin work in Codex?
Yes, as experimental: `codex plugin marketplace add oprogramadorreal/optimus-claude` and `codex plugin add optimus@optimus-claude`. Commands are invoked with `$optimus:` and some features are unavailable.
How do I remove what init created?
With `/optimus:reset`. It removes selected parts of init and permissions, and `permissions` alone removes only the branch and file safeguards.
Is Jira required?
Only for the `/optimus:jira` skill, which turns a Jira issue into a task with acceptance criteria. The other skills do not involve Jira.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin: 39 commands for PRs, review, commits and specs, nine expert roles and hooks, in eight language versions
A Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work
A marketplace of 23 plugins for Claude Code: git and pull requests, code review, TDD, specs and delegation to other models
A Claude Code plugin: Claude does the task, then a stop hook starts an independent Codex review and Claude fixes the findings in the same session
Claude Code plugin with 17 skills: task sizing, design review, TDD, fresh-context subagents and a PR after three human decisions.
Nick Tune's plugin marketplace for Claude Code: checks before a task is handed in, code review and TDD personas
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Optimus (this card) | no | 75 | ||
| Superpowers Lab | no | 438 | four experimental skills with no project init or rule-based review | |
| code-review-graph | no | not required | 32,733 | a local code-structure graph that serves the agent relevant context over MCP |
README in short
The README presents the plugin idea as work on project context, then shows a quick start for Claude Code and Codex and a table of skills. A Codex support matrix, tested versions and a troubleshooting section follow.