revshell

Gates code changes through a blocking subprocess reviewer before they land.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/quentinlemarie/revshell-coreview --skill revshell-quentinlemarie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: revshell
Source: https://github.com/quentinlemarie/revshell-coreview/tree/main/revshell
Command: npx skills add https://github.com/quentinlemarie/revshell-coreview --skill revshell-quentinlemarie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Code changes from an AI coding agent often land without independent review, letting bugs and convention violations slip through. revshell inserts a mandatory review gate inside the same session: the host agent implements a change, then drives a REVIEWER as a blocking subprocess that inspects the diff before it lands. ## Core Features & Use Cases - Shared review contract across backends: One identical contract (inlined diff, severity-tagged findings, parseable VERDICT line) works with Codex CLI, a Claude subagent, Qwen Code (local MLX or API), and DeepSeek Coder (local Ollama, findings-only). - Reviewer direct-edit mandate: The reviewer fixes every mechanically fixable finding itself and tags each edit in a REVIEWER EDITS block so the implementer can verify changes with git diff before landing. - Hardened concurrent drivers: Per-invocation IDs, stderr heartbeats, buffered output, and timeout escalation let multiple review rounds run concurrently without lock contention or stalled pipes. - Use Case: After implementing a feature on a temp branch, run the Codex review driver against the merge-base diff; the reviewer corrects issues in the working tree, returns a verdict, and only a 'ready to ship' verdict proceeds to curated commits and a single memory commit. ## Quick Start Ask the agent to review the current uncommitted changes with revshell using the Codex backend against the merge-base of the target branch.

Frequently Asked Questions about revshell

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

FAQPage Schema
How do I have Codex review my code changes before committing?

Run scripts/codex-review.sh with --plan, --phase code, --repo, and --base pointing at your merge-base ref. It inlines the full diff into the review prompt, blocks until Codex responds, and prints findings plus a parseable VERDICT line.

Which reviewer backends does revshell support?

Four backends share one review contract: Codex CLI, a Claude subagent, Qwen Code (local MLX or API), and DeepSeek Coder via local Ollama. Codex and Qwen can edit files directly; DeepSeek is text-only and returns findings without edits.

Can multiple revshell review rounds run concurrently?

Yes. Each invocation gets a unique ID, its own buffered output file, and its own process group, with no global lock. Heartbeats on stderr report elapsed time so concurrent healthy rounds are distinguishable from stalls.

Does revshell create commits during review rounds?

No. Review rounds never create commits; the working tree is the review artifact and the diff base is git merge-base. Only after a 'ready to ship' verdict are curated commits made, merged, and followed by one memory commit.

What happens when a review round times out?

The driver returns exit code 124 after the timeout, escalating from TERM to KILL on the reviewer's process group. You can re-run the round or tighten scope with a narrower --base or per-area passes for very large diffs.