Red Green Mode
Autonomous test-fix loop: run an objective verifier (tests, type-check, lint, CI), fix what is red, re-run, and finish only when the verifier exit code is all green. Use when the user wants work driven to green without supervision, including long-run or parallel runs (红绿灯模式 / 跑到全绿 / 把 CI 修到全绿). Not for subjective work with no verifier or one-shot edits; use test-driven-development to write tests and systematic-debugging to root-cause one bug.
Install
npx skills add hidevinliu/red-green-mode --skill red-green-modegit clone --depth 1 https://github.com/hidevinliu/red-green-mode.git /tmp/red-green-mode
mkdir -p ~/.claude/skills
cp -r /tmp/red-green-mode/. ~/.claude/skills/red-green-modePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Red-Green Mode
## What this is / when to use it
An unattended **self-verification loop**: finish when the verifier is all green, stop and fix
whatever is red, then verify again.
> **The verifier's exit code decides right and wrong. The agent's opinion does not.**
- This mode governs **outer orchestration only** — when to stop, what counts as done, no cheating, always leave a way back.
- It does **not** teach you to diagnose a red (that's `systematic-debugging`) and does **not** write your tests (that's `test-driven-development`).
- Three preconditions, all required: ① an objective verifier that can tell right from wrong; ② a trustworthy referee (a red is genuinely red, a green can still catch bugs, a green is not tautological); ③ an unambiguous task. When ① is missing, **construct a red you can actually fix against** — do not just say "switch to TDD" and walk away.
- Money / people / contracts / SOPs / formulas → clear the business-rule discovery gate first. Task ships a PRD → clear the PRD-coverage gate before finishing ("tests green" ≠ "PRD delivered").
- **Single agent by default.** Long-run and task-parallel are optional outer modes; pass no flags and behaviour is unchanged.
- `VERSION-AND-STATE.md` is the single source of truth for state-file ownership, stop-condition layering and runtime degradation; release history is in `CHANGELOG.md`.
## Hard mechanisms (exit-code enforced — actually run these)Details
- Skill name
red-green-mode- Repository
- hidevinliu/red-green-mode
- License
- MIT
- Repo updated
- 5 October 2026
FAQ
What does the Red Green Mode skill do?
Autonomous test-fix loop: run an objective verifier (tests, type-check, lint, CI), fix what is red, re-run, and finish only when the verifier exit code is all green. Use when the user wants work driven to green without supervision, including long-run or parallel runs (红绿灯模式 / 跑到全绿 / 把 CI 修到全绿). Not for subjective work with no verifier or one-shot edits; use test-driven-development to write tests and systematic-debugging to root-cause one bug.
How do I install the Red Green Mode skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add hidevinliu/red-green-mode --skill red-green-mode. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Red Green Mode popular?
It lives in hidevinliu/red-green-mode, which has 11 GitHub stars and 1 forks.
Related skills
Serial Protocol Assistant
1110walnut/serial-protocol-tester-skill
Convert vendor serial communication specifications into validated, single-language serial_protocol.v1 JSON that drives a functional test console. Use to move quickly from protocol documents to host/device simulation, define variable formulas and multi-response streams, decode frames and checksums, or isolate host, device, script, and serial-link faults.
Does It Work
11TsakunovR/does-it-work
Проверка, что продукт реально работает, и защита его качества автотестами. Аудит работающего (в т.ч. навайбкоженного) приложения: найти баги, оценить готовность к проду, выдать баг-репорт с severity. Генерация тестовых фреймворков: API-тесты на Python (pytest + httpx + Pydantic + Allure) и Java (JUnit 5 + REST Assured), WEB/UI-тесты (Playwright, Selenium, Selenide, Page Object); конвертация OpenAPI/Postman/curl/HAR в тесты, негативные кейсы, контракты. Также стабилизация флакающих тестов и ревью качества тестов. Triggers: "проверь мой продукт/приложение", "найди баги", "навайбкодил", "можно ли
GPU Test
12xero00000/gpu-test
Identify GPUs, run bounded compute or model inference benchmarks, and compare saved before/after results on NVIDIA, AMD, Intel, or Apple systems using supported installed runtimes. Use for GPU performance and basic numerical checks; includes a separate explicit workflow for qualified Linux NVIDIA pre-driver unlock trials.
Aftermath
14moah0911/aftermath
Post-failure recovery when something already broke: test suite went green to red, same error repeats after a fix, build or dependency resolution fails, a test is flaky, a merge conflicts, a destructive command is blocked, a forward edit is frozen, user says "you broke it", or the fix touched files outside scope. Stop, revert cheap damage, diagnose honestly, return to last-known-good. Supports lite/full/ultra, opt-in checkpoint autoRevert. Use ONLY for recovery after failure, not for planning new work.
Trip Planner
10TianhaoWu66/trip-planner
Plan scenic multi-day domestic trips (China) end-to-end and deliver a detailed, verified travel guide as Markdown + PDF. Use when the user asks for a travel itinerary/攻略 (e.g. 帮我制定北疆旅游攻略, 做个云南行程, 计划一次川西自驾). Workflow: first confirm travel dates and the scenic-spot list (from the user or researched via 携程攻略 sights page + 小红书/马蜂窝), source long-haul transport from 12306 or airlines, plan inter-city routes with 高德地图, verify every ticket/reservation with a cited source (never fabricate), compare real hotel prices on Ctrip and Fliggy and verify restaurant ratings on Dianping (the customer must log in
QA Test Case Generation
12saleem-daqa/qa-test-case-generation
Use when generating manual QA test cases from requirements, BRDs, user stories, acceptance criteria, spreadsheets, live mockup/prototype URLs, uploaded mockups, screenshots, wireframes, or existing test case templates; especially when coverage, deduplication, traceability, validations, permissions, workflows, or edge cases matter.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.