Works with
Packaged from the source skill for Claude, Codex and 4 more.
Prove that a regression test is coupled to a defect by observing failure, success and failure after removing the fix.
Workflow and deliverables
Identify a concrete bug and focused test, preserve the initial failure, apply a minimal fix, then temporarily remove it and observe the same failure again. A bundled evidence checker helps record the loop before broader validation and final restoration.
Limits and prerequisites
Some defects cannot be instantiated directly; structural or model tests must be labeled with their limits. Reverting requires an isolated, reversible workflow so unrelated work is preserved.
What is inside the skill
Section headings from the original SKILL.md (about 1,530 words of instructions). Read the full text in the source repository before installing.
- Overview
- Workflow
- Proactive Triggers
- Output Format
- Picking the target
- The loop
- 1. Verify the cause. Do not infer it.
- 2. Write the test. Watch it fail.
- 3. Fix it.
- 4. Revert the fix. Confirm red. ← the whole point
- 5. Run everything.
- When you cannot get a true red
- Reporting
- Anti-patterns
- One-line version
- Attribution and License
- More in this skill
Bundled files
README.mdscripts/README.mdscripts/red_green_evidence.pyLICENSE
Example prompts
- Review this bug fix and collect red-green-red evidence showing the new assertion fails when the fix is removed.
- Design a focused regression test for a pagination edge case and distinguish observed failure from inferred behavior.
How to install Red Green Proof
Claude Packaged
- Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
- For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
- For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
- Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
Codex Packaged
- Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
- Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
- Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
- AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
GPT Packaged
- Download the GPT package from the skill page.
- Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
- Upload the bundled reference files as knowledge so the GPT can consult them.
- Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
Gemini Packaged
- Download the Gemini package from the skill page.
- For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
- Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
- Test a matching task and verify the referenced tools and files are available.
Cursor Packaged
- Download the Cursor package from the skill page.
- Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
- Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
- Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
OpenCode Packaged
- Download the OpenCode package from the skill page.
- Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
- Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
- Start OpenCode in the project and test a matching task with the model and permissions you use.
Permissions & security
Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method
Red Green Proof FAQ
What does the Red Green Proof skill do?
Prove that a regression test is coupled to a defect by observing failure, success and failure after removing the fix.
Which AI agents can use Red Green Proof?
Packages for Claude, Codex and 4 more are built from the same source instructions.
How do I install Red Green Proof in Claude?
Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
Who made Red Green Proof and what is the license?
Red Green Proof is published by Alireza Rezvani under the MIT license. The source is https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/red-green-proof. The catalog keeps the original attribution.
What permissions does Red Green Proof need?
Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.