go-workflow

Cancel any active persistent loop

Create a git commit with auto-generated message

Complete a GitHub issue end-to-end: implement, review, E2E verify, ship

Create a PR following the repo's PR template

Create a new git worktree for a GitHub issue or PR

Run E2E verification on a PR: rebase, build, browser test, post results

Batch cleanup of all completed issue worktrees

Interactively select and remove a git worktree

Ship a PR: LLM review, coverage gate, e2e tests, push, CI watch, bot approval, merge

Start working on a GitHub issue (auto-detects bug vs feature)

Create worktree + tmux window and kick off /start-issue autonomously

You are an exploration agent analyzing a Go codebase for an upcoming implementation task.

You are an implementation agent working in a Go codebase. You implement ONE focused task using strict test-driven development.

You are a code quality reviewer for a Go codebase. The implementation has ALREADY been verified to match the spec (spec review passed). Your job is to review code quality ONLY.

You are a spec-compliance reviewer. Your ONLY job is to verify that the implementation matches the issue requirements. Do NOT review code quality, style, or performance — that is a separate review.

PR got review comments that need fixing? Use this. Whenever a reviewer or bot left feedback on the user's pull request — comments to address, change requests, unresolved threads — and the user wants those fixed in code, this is the skill. Runs the full response workflow: fetch all review feedback (from teammates, leads, CodeRabbit, Copilot, Greptile, Claude, Codex, or any other reviewer), apply code fixes, verify, push, resolve threads, request re-review. Do NOT use for: creating new PRs, merging or closing PRs, writing your own review of someone's code, or fixing CI/lint errors unrelated to review feedback.

WHEN: User wants to create a git commit with an auto-generated message, says "commit", "commit changes", "save my work", or invokes $commit. Also when finishing a task and needing to commit before pushing. WHEN NOT: User wants to push, create a PR, or do the full ship workflow. Use $create-pr or $ship for those.

WHEN: User wants to go from issue to merged PR fully autonomously. Trigger on "complete issue", "do issue #N end to end", "implement and ship issue", "take issue N to completion", or $complete-issue invocation. This is the ultimate pipeline: issue number in → merged PR out. WHEN NOT: User wants to start an issue without shipping ($start-issue), only ship ($ship), only verify ($e2e-verify), or only address review comments ($address-review).

WHEN: User wants to create a pull request, says "create PR", "open PR", "make a pull request", "submit PR", or invokes $create-pr. Also when finishing implementation and ready to submit for review. WHEN NOT: User wants the full ship workflow with CI watching and merge. Use $ship for that.

WHEN: User wants to create a git worktree for isolated work on a GitHub issue or PR, says "create worktree", "new worktree", "worktree for issue #N", or invokes $create-worktree with an issue or PR number. WHEN NOT: User wants to remove or clean up worktrees (use $remove-worktree or $prune-worktree).

WHEN: User wants to verify a PR end-to-end before merging, run E2E browser tests on a PR, investigate implementation gaps, or fix review comments and verify. Trigger on "e2e verify", "verify PR", "e2e test", "fix and verify", "fix and ship", "ship prep", or $e2e-verify invocation. WHEN NOT: User only wants to run unit tests ($verify), only ship without verification ($ship), only address review comments ($address-review), or only run coverage ($coverage).

WHEN: User wants to batch-clean all completed git worktrees, says "prune worktrees", "clean up worktrees", "remove old worktrees", or invokes $prune-worktree. WHEN NOT: User wants to remove a single specific worktree (use $remove-worktree) or create a new worktree (use $create-worktree).

WHEN: User wants to remove a specific git worktree, says "remove worktree", "delete worktree", "clean up worktree", or invokes $remove-worktree. WHEN NOT: User wants to batch-remove all completed worktrees (use $prune-worktree) or create a new worktree (use $create-worktree).

WHEN: User wants to ship a PR end-to-end: verify, push, create PR, watch CI, and optionally merge. Trigger on "ship", "ship it", "ship this PR", "push and merge", or $ship invocation. WHEN NOT: User only wants to commit ($commit), only create a PR ($create-pr), or only manage worktrees ($remove-worktree, $prune-worktree).

WHEN: User wants to start working on a GitHub issue, says "start issue", "work on issue", "pick up issue #N", "implement issue", "fix issue #N", "add feature #N", or invokes $start-issue with an issue number. Also when user wants the full issue-to-PR workflow. WHEN NOT: User is already mid-implementation and just wants to commit, create a PR, or manage worktrees. Use $commit, $create-pr, or $ship for those.

WHEN: User wants to start working on an issue in a new tmux window, says "tmux start", "start issue in tmux", "kick off issue #N", or invokes $tmux-start with an issue number. WHEN NOT: User wants to create a worktree without tmux ($create-worktree), or start an issue in the current session ($start-issue).

3 hooks across 3 events