red-green-proof — Claude Code plugin: bug proof, install
The red-green-proof plugin turns a suspected bug into evidence with a focused test, a fix, and a rollback check. Use it when the cause still needs proof.
MIT ★ 1,596 updated 2026-10-29
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install red-green-proof@awesome-codex-pluginsWhat red-green-proof does
red-green-proof guides the agent through a focused debugging loop. It checks the suspected cause, runs a test that should fail, applies the smallest fix, then checks the result. The point is to connect the test to the actual defect rather than to a guess.
The agent then reverts the fix and runs the test again. It should fail once more, showing that the test depends on the change. That rollback is essential: without it, the test has not proved that it catches the bug. The plugin is installed through the Claude Code marketplace and uses the MIT license.
What it helps with
- prove the cause of a suspected bug
- create a focused reproducing test
- validate the smallest code fix
- check regression coverage after reverting a fix
Example prompts for the agent
- Use red-green-proof to investigate the suspected bug in
src/parser.jsand build a focused test. - Run the test before the fix, apply the smallest correction, then verify the test fails after the correction is reverted.
- Show that the test is tied to this bug rather than passing by accident.
How to install red-green-proof
Plugin marketplace
/plugin marketplace add hashgraph-online/awesome-codex-plugins/plugin install red-green-proof@awesome-codex-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about red-green-proof
How do I install red-green-proof in Claude Code?
Run these commands in order: /plugin marketplace add hashgraph-online/awesome-codex-plugins, then /plugin install red-green-proof@awesome-codex-plugins.
What does red-green-proof do?
It leads the agent through a proof loop for a suspected bug: confirm the cause, observe a focused test fail, apply a small fix, and verify failure after reverting it.
Why does the plugin revert the fix?
The rollback checks whether the test actually depends on the correction. A test that stays green after the revert has not established the bug.
Source text
red-green-proof · MIT
# Red-Green Proof Prove suspected bugs with a real red-green-red test loop: 1. Verify the cause. 2. Watch a focused test fail. 3. Apply the smallest fix. 4. Revert the fix and confirm the test goes red again. The skill is installed through the plugin marketplace and is distributed under the MIT license.
© RooAGI · MIT · hashgraph-online/awesome-codex-plugins