AI column

Coding@donghyeok99Staff

tstack: agent skills that take a change all the way to merge

A medplum PR fixed 157 doc links and shipped with one line: reviewed with sol-loop, approved

Someone says "full send" and leaves; commits land on a branch, sol-loop approves, pr-wait watches the checks go green, and the branch merges into main.
Someone says "full send" and leaves; commits land on a branch, sol-loop approves, pr-wait watches the checks go green, and the branch merges into main.
Who
Theo Browne (t3dotgg, CEO of Ping.gg) published the skills he uses every day, cleaned up for anyone.
When
Published October 24, 2026; no releases, you take it from main. Last pushed October 28.
Where
Runs in Claude Code and Codex. Uses T3 Code features when they are there and falls back to native tools when not.

What was hard

You could hand an agent a fix, but once the PR was open the job came back to you. Had CI finished, what did the review bot flag, had main moved on. Step away, and the agent sat at "waiting for checks" until you came back.

What it does about it

Say "full send" and the agent owns the work from where it is to a merged PR. The whole skill is written for nobody watching: it won't merge without proof it observed itself, it gets a review from a model by another provider, and it keeps its turn open with pr-wait while checks run. When it is truly stuck, it asks through the harness's question tool so the thread shows it is waiting.

What people made with it

GitHub@aanishs2026-10-28

A PR that turned 157 relative links across 49 doc pages into absolute paths and added a CI check for them, approved in one sol-loop round.

Reviewed with sol-loop: 1 round with gpt-6.1-sol. Sol verdict: approved
likes 0 · comments 3 (2026-10-29 as of)GitHub ↗
GitHub@mmmattG2026-10-27

A fix for an iPhone Bible reader that froze when touched mid-scroll. Its description ends with a council review table where GPT-6.1-Sol gave 9/10.

Touching the iPhone reader while it was still gliding could freeze scrolling permanently.
likes 1 · comments 2 (2026-10-29 as of)GitHub ↗
GitHub@jakebodea2026-10-28

A PR that moved per-person name and color editing up above Style on Mac and Windows, with test results and a Mac preview attached as proof.

Reviewed with sol-loop: 2 rounds with gpt-6.1-sol. Sol verdict: approved.
likes 0 · comments 1 (2026-10-29 as of)GitHub ↗

How it runs inside

  1. 1

    You → full-send

    "full send"The phrase grants merging, --force-with-lease on its own branch, and running tests without asking first.skills/full-send/SKILL.md
  2. 2

    full-send → Claude Code / Codex

    Smallest change + proof it sawReproduce the failure, fix it, watch the same repro pass, or run the repo's CI checks and take screenshots.skills/full-send/SKILL.md
  3. 3

    Claude Code / Codex → GPT Sol (sol-loop)

    The diff and a "Review only" briefOne Sol reviewer, three rounds by default, replies VERDICT: APPROVE or CHANGES with blocker, should and nit.skills/sol-loop/SKILL.md
  4. 4

    Claude Code / Codex → Merged PR

    A description that leads with the problemfile-pr opens the PR problem-first, not as a change inventory, with a Reviewed with sol-loop line.skills/file-pr/SKILL.md
  5. 5

    pr-wait → Claude Code / Codex

    One line per real eventFailed checks, new reviews, BEHIND or DIRTY each print a line; it exits 0 when ready and 1 when you must act.skills/babysit-pr/scripts/pr-wait
  6. 6

    Claude Code / Codex → Merged PR

    Merge gate passes, then mergeWith proof, green checks, bot findings handled and an up-to-date branch, it merges and reports link and decisions.skills/full-send/SKILL.md

What goes in, what comes out

"full send"Proof, review, PR and merge, then a report with the PR link and each decision
"council"A table of scores and rounds from three providers' models in the PR description
"take over"Someone else's PR finished, with the original authors' credit kept

Is it for you

Good for

  • Handing off a small fix and walking away
  • Repos with review bots like Greptile or Macroscope whose findings you'd rather not triage by hand
  • Cross-checking one PR with models from different providers
  • Finishing a stalled PR without losing its author's credit

Not for

  • Needs an authenticated GitHub CLI (gh), and python3 for pr-wait.
  • council and sol-loop run subagents on other providers' models; outside T3 Code you need a harness that can.
  • pr-wait imports fcntl, so as the code stands it does not start on Windows.
  • pr-wait's default, ready, waits for a Greptile or Macroscope review; repos with neither need --until green.

Reviewed by Devalley’s editor before publishing. How the column is made

Sign in to post, comment and like.Sign in

Report

Reason

Read the community rules