Esta página se muestra en inglés. Una traducción al español está en curso.
SkillsApr 28, 2026·2 min de lectura

/go — Verify + Simplify + PR in One Command

Open-source slash command that chains verify-app + code-simplifier + open-PR in sequence. Inspired by Boris Cherny's /go shortcut.

Introducción

/go is the "ship it" composite. Boris Cherny calls it out as the slash command he hits most when a feature is done: it runs the verify-app subagent (E2E tests), then code-simplifier (cleanup pass), then opens a PR — fail-fast at each gate.

The point is to make the finish-and-ship sequence one keystroke. If verify-app finds failures, you stop and fix. If simplifier introduces a behavior change (it shouldn't), you catch it at PR review.

Works with: Claude Code 1.x. Requires verify-app subagent + code-simplifier (Anthropic official) + GitHub CLI.


How /go Works

Save to .claude/commands/go.md:

---
description: Verify, simplify, and ship — fail-fast composite slash command
---

Execute the ship sequence. Stop at the first failure.

1. **Verify** — Invoke the `verify-app` subagent on the changes since branch divergence (`git diff main...HEAD`). If verify-app reports any FAIL, stop here and surface the failure summary.

2. **Simplify** — If verify-app passed, invoke the `code-simplifier` subagent on the same set of files. It must preserve behavior (no public-API changes). After simplification, automatically re-run verify-app once more to catch any accidental regression.

3. **Ship** — If both passes are clean, execute `/commit-push-pr` with no argument (let it auto-generate the title from the diff).

Output a one-line stage summary at the end: VERIFY ✅ | SIMPLIFY ✅ | PR <url>. If any stage fails, output VERIFY ❌ at <test> and stop — do not proceed to simplify or PR.

## Boundaries

- Never skip a stage even if I ask. The whole point of /go is the gate sequence.
- Never push if verify-app's second run (after simplify) regresses.
- If verify-app subagent is not installed, escalate: "Install verify-app first — see TokRepo."

Example session

You:    "/go"
Claude: -> verify-app: 7 E2E tests run, 7 passed ✅
        -> code-simplifier: refactored 4 files (removed 3 temp vars, inlined 2 helpers) ✅
        -> verify-app (re-run): 7 passed ✅
        -> /commit-push-pr: PR #483 opened
        -> Summary: VERIFY ✅ | SIMPLIFY ✅ | PR https://github.com/acme/api/pull/483

Failure case:

You:    "/go"
Claude: -> verify-app: 1 FAIL at tests/e2e/checkout.spec.ts:42
        -> Stopped. Summary: VERIFY ❌ at checkout.spec.ts:42

FAQ

Q: Why re-run verify-app after simplify? A: code-simplifier promises behavior preservation, but trust-but-verify. The second run is a 30-second insurance check.

Q: Can I skip simplify? A: Edit the command file to remove step 2. But that defeats the purpose — Boris's pattern is "verify + simplify + ship" precisely because simplification often catches dead-code issues that pass tests.

Q: What if I'm on main/master? A: /go calls /commit-push-pr which will refuse to push to main without confirmation.

Q: Is this Boris's actual /go command? A: No — community-written. Boris's private command file is not open-sourced.

Q: Do I need both subagents? A: Yes — verify-app (TokRepo) + code-simplifier (Anthropic official, also on TokRepo). Both must be installed first.


🙏

Fuente y agradecimientos

Inspired by Boris Cherny's /go slash command on howborisusesclaudecode.com.

Citations:

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados