lythoskill-red-green-releaselisted

# Red-Green Release Workflow > No tag without LGTM. Every change is a self-archiving patch. Every state is rollback-able. ## Typical Scenarios This skill shines when the agent **does not have direct filesystem or git access** to the user's project. Typical setups: - **Web chat + Repomix**: User pastes a Repomix dump of their codebase into a web chat. The agent proposes changes as `pr-*.sh` heredoc patches. The user copies the patch locally and runs `bash pr-*.sh`. - **Distributed / async review**: Patches are posted in issues, emailed, or shared via web UI for a human to review and apply manually. - **No git on target**: Environments (e.g., bare-metal servers, deployed configs) where `git revert` is unavailable — `.bak` files provide rollback. In these scenarios the agent cannot `git commit`, `git diff`, or write files directly. The heredoc patch is the **only viable delivery format**. ## Core Principles 1. **User acceptance drives releases** — "LGTM" / "对了" / "就是这样" → then and only then commit + tag. 2. **Atomic patches** — Each iteration = one `pr-<timestamp>-<desc>.sh` with heredoc content replacement. 3. **Self-archiving** — Patch copies itself to `archived-patches/` and deletes itself after execution. 4. **Rollback-ready** — Every patch backs up originals before modifying. Rollback = restore backup. ## Workflow (4 Phases) **Phase 1 — Plan**: Understand requirement, describe approach, user confirms design. **Phase 2 — Create Patch (dry-run)**: Write `pr-<timestamp>-<