From go-workflow
Runs E2E verification on a GitHub PR by rebasing, building, running browser tests, and posting results. Supports verify, fix, investigate, and ship modes.
How this command is triggered — by the user, by Claude, or both
Slash command
/go-workflow:e2e-verify [PR-number] [verify|fix-and-verify|investigate|ship-prep|ship|fix-and-ship]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# E2E Verify **If `$ARGUMENTS` is empty or not provided:** Display usage information: **Usage:** `/e2e-verify [PR-number] [mode]` **Modes:** | Mode | When to use | Flow | |------|-------------|------| | `verify` (default) | Code looks solid, just needs E2E | Rebase → build → E2E test → post results | | `fix-and-verify` | Review feedback needs addressing | Address review → rebase → build → E2E → post → add `run-full-ci` label | | `investigate` | Not sure the implementation is right | Rebase → read issue → review gaps → E2E → report findings | | `ship-prep` | Confident, want to prep for ...
If $ARGUMENTS is empty or not provided:
Display usage information:
Usage: /e2e-verify [PR-number] [mode]
Modes:
| Mode | When to use | Flow |
|---|---|---|
verify (default) | Code looks solid, just needs E2E | Rebase → build → E2E test → post results |
fix-and-verify | Review feedback needs addressing | Address review → rebase → build → E2E → post → add run-full-ci label |
investigate | Not sure the implementation is right | Rebase → read issue → review gaps → E2E → report findings |
ship-prep | Confident, want to prep for /ship | Rebase → build → E2E → post → add run-full-ci label |
ship | Ready end-to-end (no review to address) | Rebase → build → E2E → post → /go-workflow:ship |
fix-and-ship | Take PR to completion (most common) | Address review → rebase → build → E2E → post → label → watch CI → /go-workflow:ship |
Examples:
/e2e-verify — verify current branch's PR/e2e-verify 42 — verify PR #42/e2e-verify fix-and-ship — fix review comments and ship/e2e-verify 42 investigate — investigate PR #42Ask the user: "What PR would you like to verify? (or provide a PR number and mode)"
If $ARGUMENTS is provided:
First, resolve the PR number and validate it exists before creating loop state:
PR_NUM=""
for arg in $ARGUMENTS; do
case "$arg" in
verify|fix-and-verify|investigate|ship-prep|ship|fix-and-ship) ;;
*) if [ -z "$PR_NUM" ] && echo "$arg" | grep -qE '^[0-9]+$'; then PR_NUM="$arg"; fi ;;
esac
done
PR_NUM="${PR_NUM:-$(gh pr view --json number --jq '.number' 2>/dev/null)}"
if [ -z "$PR_NUM" ]; then
echo "Error: No PR found for current branch and no PR number provided."
echo "Usage: /e2e-verify [PR-number] [mode]"
exit 1
fi
gh pr view "$PR_NUM" --json number >/dev/null 2>&1 || { echo "Error: PR #$PR_NUM does not exist"; exit 1; }
echo "Verified PR #$PR_NUM exists"
!if [ ! -x "${CLAUDE_PLUGIN_ROOT}/scripts/setup-loop.sh" ]; then echo "ERROR: Plugin cache stale. Run /gopher-ai-refresh"; exit 1; else PR_NUM=""; for arg in $ARGUMENTS; do case "$arg" in verify|fix-and-verify|investigate|ship-prep|ship|fix-and-ship) ;; *) if [ -z "$PR_NUM" ] && echo "$arg" | grep -qE "^[0-9]+$"; then PR_NUM="$arg"; fi ;; esac; done; PR_NUM="${PR_NUM:-$(gh pr view --json number --jq '.number' 2>/dev/null)}"; if [ -z "$PR_NUM" ]; then echo "No PR found — skipping loop init"; exit 1; fi; "${CLAUDE_PLUGIN_ROOT}/scripts/setup-loop.sh" "e2e-verify-${PR_NUM}" "VERIFIED" 30; fi
Read ${CLAUDE_PLUGIN_ROOT}/skills/e2e-verify/SKILL.md and follow all steps with the parsed PR number and mode from $ARGUMENTS.
npx claudepluginhub gopherguides/gopher-ai --plugin go-workflow/verify-prVerifies a pull request's frontend changes via automated browser testing. Analyzes changed routes, tests features sequentially in one session, and generates a Markdown report with screenshots.
/shipExecutes full PR workflow from commit to production: pre-flight checks, PR creation, CI/review monitoring, merge, deployment, and validation with quality gates.
/polishIteratively drives a pull request to meet all 6 green conditions (CI passing, no merge conflicts, CodeRabbit approval, resolved comments, etc.) via fix-and-verify loops. Does not merge.
/shepherdShepherds pull requests through CI checks and code reviews to merge readiness. Iteratively assesses stack, fixes issues, resubmits, and requests approval.
/create-prCreates GitHub pull requests after user-selected validation (feature: security/quality/tests; bugfix/refactor: targeted checks; quick: direct), with incremental status updates.
/git-workflowOrchestrates git workflow from code review and quality gates through commit, push, and PR creation to target branch. Supports flags: --skip-tests, --draft-pr, --no-push, --squash, --conventional, --trunk-based.