agentleFS
sd0xdevsd0xdev/sd0x-dev-flow/skills/codex-review-branch/SKILL.md

codex-review-branch

Skill192 starsChanged 36 days agoMITView on GitHub

Fully automated review of an entire feature branch using Codex exec

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Document review (use /codex-review-doc)

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Codex Review Branch

Thin entry-point skill — routes to the parent skill for full workflow.

Parent Skill

This is the Branch variant of codex-code-review. Full workflow, prompt templates, and review logic are defined in the parent skill.

See @skills/codex-code-review/SKILL.md

Variant

PropertyValue
ScopeFull branch (all commits since base)
Pre-checksNone
Prompt template@skills/codex-code-review/references/codex-prompt-branch.md
ReviewersCodex alone. --dual adds a secondary reviewer — off unless the flag is passed
Tierthorough (this is the depth variant — P0/P1/P2 block, round cap 30)

Flags

FlagDefaultEffect
--dualoffAdds a second reviewer in parallel (see parent skill Step 3). The merge happens in conversation — no state write, no mode field, and the next invocation starts single again unless the flag is passed again. A second opinion that can block this review's gate. Use for releases, security-sensitive changes, and public API surfaces.

--dual is the only code-review entry point where two reviewers run. /codex-review-fast and /codex-review-doc are single-reviewer by design and offer no such flag: the cost of the second opinion is only worth paying where the change warrants it, and this is that variant. /plan-review --dual is the plan-mode counterpart — same opt-in shape, same default of off, a different loop.

Trigger

  • Keywords: branch review, full branch, review branch, codex-review-branch

When NOT to Use

  • Quick diff-only review (use /codex-review-fast)
  • Full review with lint + build (use /codex-review)
  • Document review (use /codex-review-doc)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.