be-review

Runs four code reviewers serially on a branch, each editing and committing in turn.

957|79|Updated May 9, 2021
One-click install
npx skills add https://github.com/srid/emanote --skill be-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: be-review
Source: https://github.com/srid/emanote/tree/main/.agents/skills/be-review
Command: npx skills add https://github.com/srid/emanote --skill be-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multiple AI code reviewers on the same branch risks conflicting edits, torn worktree state, and PR comments that reference commits never pushed. This Skill orchestrates a serial review gauntlet so each reviewer works on a clean, settled tree and comments only land after the push.

Core Features & Use Cases

  • Serial review gauntlet: Runs /lens-debate, /codex-debate, /simplify, and code-police one after another, each as the sole editor committing its own fixes on the live branch.
  • Push-then-comment safety: Suppresses per-step self-commenting, pushes once after all steps finish, and only then posts the deferred lens, codex, and police PR comments so no comment references a local-only SHA.
  • Robust orchestration: Resolves the merge-base once, pins the target repo path for cross-repo runs, retries codex on reviewer-error, and reconciles incomplete applies or commits before moving on.
  • Use Case: From a /be workflow on a feature branch, run the full review gauntlet so four reviewers debate, fix, simplify, and police the diff, then push and post consolidated PR comments automatically.

Quick Start

Ask the agent to run the review gauntlet on the current branch against the default base, optionally limiting tracks with --tracks lens,codex,simplify,police.

Frequently Asked Questions about be-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multiple AI code reviewers on the same branch?

Run them serially so each reviewer is the sole editor while it runs. This Skill executes lens-debate, codex-debate, simplify, and code-police one after another, with each step committing its fixes before the next begins.

How do I run the review gauntlet on a pull request?

Invoke the be-review skill from /be section 4 or ask to run the review gauntlet. It checks for a non-empty diff, resolves the merge-base once, runs the selected tracks, pushes new commits, and posts the deferred PR comments.

Why run code reviewers serially instead of in parallel?

Parallel reviewers writing the same worktree see torn, half-edited state. Serial execution means each step starts from a committed, settled tree, eliminating snapshot machinery and separate apply passes.

Can I run the gauntlet on a different repository than the current directory?

Yes. Pin repoPath to the target repo's absolute path and it is threaded into every step. The debate scripts defensively parse stringified args so cross-repo runs resolve the target repo's base instead of the cwd.

What happens when the codex review step fails with reviewer-error?

A reviewer-error is treated as an infrastructure hiccup, not a debate outcome. The step is retried up to three times with the same arguments; only if all attempts fail does the gauntlet report the error and skip the codex comment.

When are PR comments posted during the review gauntlet?

Comments are posted only after the final push succeeds. Each step runs with self-commenting suppressed, and the lens, codex, and police comment bodies are published once the commits they reference exist on the remote.