How do I install the Lythoskill Red Green Release skill?

Run npx skillmds@latest add lythos-labs/lythoskill-red-green-release-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Lythoskill Red Green Release skill do?

User-acceptance-driven release workflow using heredoc patch files. Each iteration produces a timestamped pr- - .sh that self-archives after execution. No tag without explicit user LGTM. Supports rollback via archived backups. It is listed under Productivity on SkillMD.

Is Lythoskill Red Green Release safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lythoskill Red Green Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lythoskill Red Green Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lythoskill Red Green Release?

lythos-labs (@lythos-labs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lythoskill Red Green Release by lythos-labs

Name: Lythoskill Red Green Release
Author: lythos-labs

Lythoskill Red Green Release

User-acceptance-driven release workflow using heredoc patch files. Each iteration produces a timestamped pr-<timestamp>-<desc>.sh that self-archives after execution. No tag without explicit user LGTM. Supports rollback via archived backups.

lythos-labs Updated Sep 22, 2026

File contents

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

User acceptance drives releases — "LGTM" / "对了" ("that's right") / "就是这样" ("exactly") → then and only then commit + tag.
Atomic patches — Each iteration = one pr-<timestamp>-<desc>.sh with heredoc content replacement.
Self-archiving — Patch copies itself to archived-patches/ and deletes itself after execution.
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>-<desc>.sh containing backup + heredoc replacement + self-archive logic. Show to user for review. User says "apply it" → proceed. Phase 3 — Apply & Test: Execute patch (bash pr-*.sh). Restart service. User tests. If issues → back to Phase 2 with a new patch. Iterate until green. Phase 4 — Accept & Tag: User says LGTM →

git add -A
git commit -m "<summary>"
git tag -a <tag> -m "<summary>"

Patch File Format

Naming

pr-<timestamp>-<description>.sh

Forbidden words in description: final, done, fix, ok. These words encourage skipping the red-green test cycle by implying pre-verified success.

Template

#!/bin/bash
# PR: <timestamp>-<description>
# 1. Create archive directory
mkdir -p archived-patches
# 2. Backup current files (for rollback)
cp src/target.ts "archived-patches/target.ts.$(date +%Y%m%d).bak"
# 3. Apply changes (declarative full-file replacement via heredoc)
cat > src/target.ts << 'PATCH_EOF'
// Full replacement content here — exact file state after patch
PATCH_EOF
# 4. Self-archive: copy patch to archive, then delete from root
cp "$0" "archived-patches/$(basename "$0")"
rm "$0"

⚠️ Heredoc delimiter (PATCH_EOF) must be quoted in the cat command to prevent variable expansion. See references/archive-format.md for multi-file patches and escaping rules.

Supporting References

Read these only when the specific topic arises:

When you need to…	Read
See complete heredoc syntax, multi-file patches, and escaping rules	references/archive-format.md
Understand the 4-phase workflow in detail	references/phase-details.md
See conversation examples of red-green iterations	references/conversation-examples.md

---name: lythoskill-red-green-release-2description: User-acceptance-driven release workflow using heredoc patch files. Each iteration produces a timestamped pr-<timestamp>-<desc>.sh that self-archives after execution. No tag without explicit user LGTM. Supports rollback via archived backups.---# Red-Green Release Workflow> No tag without LGTM. Every change is a self-archiving patch. Every state is rollback-able.## Typical ScenariosThis 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 Principles1. **User acceptance drives releases** — "LGTM" / "对了" ("that's right") / "就是这样" ("exactly") → 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>-<desc>.sh` containingbackup + heredoc replacement + self-archive logic. Show to user for review.User says "apply it" → proceed.**Phase 3 — Apply & Test**: Execute patch (`bash pr-*.sh`). Restart service.User tests. If issues → back to Phase 2 with a new patch. Iterate until green.**Phase 4 — Accept & Tag**: User says LGTM →```bashgit add -Agit commit -m "<summary>"git tag -a <tag> -m "<summary>"```## Patch File Format### Naming```pr-<timestamp>-<description>.sh```**Forbidden words in description**: `final`, `done`, `fix`, `ok`. These wordsencourage skipping the red-green test cycle by implying pre-verified success.### Template```bash#!/bin/bash# PR: <timestamp>-<description># 1. Create archive directorymkdir -p archived-patches# 2. Backup current files (for rollback)cp src/target.ts "archived-patches/target.ts.$(date +%Y%m%d).bak"# 3. Apply changes (declarative full-file replacement via heredoc)cat > src/target.ts << 'PATCH_EOF'// Full replacement content here — exact file state after patchPATCH_EOF# 4. Self-archive: copy patch to archive, then delete from rootcp "$0" "archived-patches/$(basename "$0")"rm "$0"```> ⚠️ Heredoc delimiter (`PATCH_EOF`) must be quoted in the `cat` command to prevent variable expansion. See [references/archive-format.md](./references/archive-format.md) for multi-file patches and escaping rules.## Supporting ReferencesRead these **only when the specific topic arises**:| When you need to… | Read ||--------------------|------|| See complete heredoc syntax, multi-file patches, and escaping rules | [references/archive-format.md](./references/archive-format.md) || Understand the 4-phase workflow in detail | [references/phase-details.md](./references/phase-details.md) || See conversation examples of red-green iterations | [references/conversation-examples.md](./references/conversation-examples.md) |

Frequently asked questions