# wendy-iterating

Runs a find-fix-ship loop: each change gets its own worktree, a subagent carries it to green CI, and the loop stops itself when nothing is left.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 62
- Author: wendylabsinc
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/wendylabsinc/claude-skills/tree/HEAD/wendy-iterating/SKILL.md
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/skills/wendy-iterating

## What it does

The skill handles the plumbing of the loop: keeping fixes apart in worktrees, handing them to a subagent, driving pull requests, spacing out checks and shutting down. It has no idea how your project is tested. That part comes from a companion skill such as `/wendy-cloud-testing`, which tells it what command to run, where runtime errors show up, what counts as clean, and which failures are already known. Without that companion the loop has nothing to measure.

Every change follows the same path. The skill reads the current branch and keeps it as the base. Then it adds a worktree under `$BASE/.worktrees/$BRANCH` on a branch named `fix/<short-description>`. A subagent gets the files and lines, the root cause and the fix, runs the targeted test inside that worktree and commits. Next come `gh pr create` and `gh pr checks --watch`; nothing moves on until the checks pass. Merging is `gh pr merge --squash --delete-branch`, after which the worktree is removed. Commits never go straight onto the current branch.

Some fixes should not be made inline. If the change runs past 30 lines, crosses subsystems, or the cause is still murky after 15 minutes of digging, or architecture has to shift, the skill points you to a Linear issue instead. The wait before the next check follows the outcome: 5 minutes when something was found and fixed, 10 when a bug was found but left alone, 30 when everything is clean. Three clean rounds in a row end the loop, and any bug resets that counter.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add wendylabsinc/claude-skills --skill wendy-iterating -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/wendy-iterating/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/wendy-iterating/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add wendylabsinc/claude-skills --skill wendy-iterating -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/wendy-iterating/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add wendylabsinc/claude-skills --skill wendy-iterating -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/wendy-iterating/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install wendylabsinc/claude-skills wendy-iterating
```

2. **Manually: put the files in place**
- File: `.github/skills/wendy-iterating/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add wendylabsinc/claude-skills --skill wendy-iterating -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/wendylabsinc/claude-skills --path wendy-iterating
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/wendy-iterating/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add wendylabsinc/claude-skills --skill wendy-iterating -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/wendylabsinc/claude-skills/tree/HEAD/wendy-iterating/SKILL.md

## When to use it
- run a continuous bug-finding and fixing loop
- push a feature until every test passes
- keep each fix in its own worktree away from the main checkout
- route every change through a pull request and wait for CI
- let the loop stop on its own once nothing is broken

## Example prompts
- Iterate on this feature with `/wendy-iterating`, and use `/wendy-cloud-testing` to decide how to test for bugs
- Start the fix loop with `no-auto-terminate` so it keeps running
- Run another iteration: tests, logs, then the skill's fix workflow

## Similar
- [setup-matt-pocock-skills](https://affpapa.org/en/nevibecode/skills/setup-matt-pocock-skills.md) — skill · 1052851 installs
- [ask-matt](https://affpapa.org/en/nevibecode/skills/ask-matt.md) — skill · 766587 installs
- [to-tickets](https://affpapa.org/en/nevibecode/skills/to-tickets.md) — skill · 711230 installs
- [writing-plans](https://affpapa.org/en/nevibecode/skills/writing-plans.md) — skill · 282859 installs
- [caveman-review](https://affpapa.org/en/nevibecode/skills/caveman-review.md) — skill · 411800 installs
- [caveman-compress](https://affpapa.org/en/nevibecode/skills/caveman-compress.md) — skill · 411500 installs

From the same set: [wendylabsinc/claude-skills](https://affpapa.org/en/nevibecode/by/wendylabsinc/claude-skills.md) — 7 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md