sd0x-dev-flow plugin

A Claude Code plugin that limits the agent with rules and hooks and hands independent code review to Codex CLI in a review loop.

  • 194 ★ on the repository
  • Last commit
  • MIT
Plugin

Broad access

Why this level

  • Hooks intervene in edits and commits, and skills plus the adapter run commands and call Codex CLI on your machine.
  • Review sends project code to Codex CLI under your login.
All reasons and checks

sd0xdev/sd0x-harness

Install

Manual install

/plugin marketplace add sd0xdev/sd0x-harness

The first Quick Start command. Then `/plugin install sd0x-dev-flow@sd0xdev-marketplace` and `/project-setup`.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Hooks intervene in edits and commits, and skills plus the adapter run commands and call Codex CLI on your machine.
  • Review sends project code to Codex CLI under your login.

This is third-party code. Review the repository files before installing.

What it does

sd0x-dev-flow adds a control layer to Claude Code: a small rule core loads at launch, and detailed procedures load when their situation arises. The bundle holds 102 skills, 16 agents, 16 rules and 7 hooks. Hooks print reminders about project state and survive context compaction. Code review runs through `codex exec`: Codex CLI inspects the changes independently, and the loop repeats until findings are closed. `/project-setup` detects the framework, package manager, database and scripts, then installs the fitting part of the rules and hooks. For Codex CLI, Cursor, Windsurf and Aider only skills are distributed.

Who it is for. Claude Code developers who want verifiable definitions of done: review by a second model, hooks before edits and commits, one rule set per project.

Good fit when

  • A large feature is about to be committed and needs a second model to recheck it before push.
  • An agent edits sensitive paths and a guard hook should run before every write.
  • A team wants one rule and skill set across all repositories.
  • A new project is connected to the harness with a single `/project-setup` command.
  • Skills are needed in Codex CLI or Cursor without the full plugin.

Not a fit when

  • The task is small and 102 skills with hooks add only noise.
  • Codex CLI is not installed and signing in is not possible.
  • You need an MCP server: the plugin calls Codex via `codex exec`, not `codex mcp-server`.

Example request

Set up the project with `/project-setup`, then run an independent Codex review of my changes before the commit.

Limitations

The full control layer needs Claude Code 2.1 or newer and Node.js 18. Hooks need `jq`: without it the sensitive-path guard and auto-formatting silently turn off. The review loop requires Codex CLI 0.149.0 or newer, signed in. The `codex-exec.js` adapter installs with a separate command or on the first review. Other agents get skills only, and Claude Code rules and hooks do not work there. The project is large, and 102 skills are hard to learn in a single day.

How to disable. Run `/plugin uninstall sd0x-dev-flow@sd0xdev-marketplace` and remove the marketplace. Delete rules and hooks installed into the project by hand.

FAQ

How do I install sd0x-dev-flow in Claude Code?

Run `/plugin marketplace add sd0xdev/sd0x-harness`, then `/plugin install sd0x-dev-flow@sd0xdev-marketplace`. After that, run `/project-setup` in the target repository.

Does it work in Cursor and Codex CLI?

Partly. `npx skills add sd0xdev/sd0x-harness` installs 102 skills, while rules and hooks stay Claude Code only. Codex CLI also has `$codex-setup init`.

What does project-setup do?

`/project-setup` detects the framework, package manager, database, entrypoints and scripts and installs part of the rules and hooks. The `--lite` flag changes CLAUDE.md only.

Is a Codex MCP server required?

No. Review runs through `codex exec` and the `codex-exec.js` adapter, and `codex mcp-server` registration is no longer used.

Why is jq required?

The `pre-edit-guard` and `post-edit-format` hooks parse their input with `jq`. Without it both exit with no action, so path protection and auto-formatting do not work.

Discussion

No questions or reviews yet.

Plugins
Needs a VPN

A ready-made Claude Code setup: agents, slash commands, skills, safety hooks, rules and MCP connections in one install

PluginBroad access878Repository stars

A plugin that turns Claude Code into a 16 agent team: documentation first planning, TDD and 9 pre-merge quality gates.

PluginBroad access53Repository stars
Needs a VPN

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

PluginBroad access731Repository stars

Hooks and skills make Claude Code plan before coding, test before shipping and escalate when it is not confident.

PluginExtended access53Repository stars

Shared Claude Code settings for a team: hooks against dangerous commands, a check before finishing and skills from spec to review

WorkflowBroad access92Repository stars

A Claude Code skill that drives Codex over JSON-RPC: tasks, code reviews, parallel research and messaging between two agents.

SkillExtended access99Repository stars

README in short

The version 4 and later concept: the model chooses its path while the harness fixes contracts and verifiable state. The docs describe the shift from scripted choreography to reminders carrying facts about changes.

README badge

Report a problem