--- name: landing-report description: Use when checking the release version queue: read-only dashboard of open PR version claims, sibling worktrees, and the next free version for /ship. --- # Landing Report ## What this does A read-only dashboard of the version numbers claimed by open PRs and sibling worktrees, plus the version your next ship would claim at each bump level (micro, patch, minor, major). Think of it as `gh pr list` for VERSION numbers. It changes nothing. Requires gstack's `bin/gstack-next-version` utility (installed at `~/.claude/skills/gstack/bin/`), plus `gh`, `git`, `bun`, and `jq`. ## When to use Triggers: "landing report", "version queue", "ship queue", "what version comes next", "show open PR versions". Useful when running several parallel workspaces and you want to see which versions are already claimed. ## How to run it This skill is entirely read-only: no file writes, no git mutations. ### Step 1: Detect base branch Use the current PR's base branch, else the repo default branch, else `main`. bash BASE_BRANCH=$(gh pr view --json baseRefName -q .baseRefName 2>/dev/null || \ gh repo view --json defaultBranchRef -q .defaultBranchRef.name 2>/dev/null || \ echo main) echo "Base branch: $BASE_BRANCH" ### Step 2: Read current state bash CURRENT_VERSION=$(cat VERSION 2>/dev/null | tr -d '[:space:]' || echo "0.0.0.0") git fetch origin "$BASE_BRANCH" --quiet 2>/dev/null || true BASE_VERSION=$(git show "origin/$BASE_BRANCH:VERSION" 2>/dev/null | tr -d '[:space:]' || echo "$CURRENT_VERSION") echo "origin/$BASE_BRANCH VERSION: $BASE_VERSION" echo "branch HEAD VERSION: $CURRENT_VERSION" ### Step 3: Query the queue Call the utility once per bump level so the user sees what each level would claim. bash for LEVEL in micro patch minor major; do bun --no-env-file --config=/dev/null run ~/.claude/skills/gstack/bin/gstack-next-version \ --base "$BASE_BRANCH" \ --bump "$LEVEL" \ --current-version "$BASE_VERSION" \ > "/tmp/landing-$LEVEL.json" 2>/dev/null || echo '{"offline":true}' > "/tmp/landing-$LEVEL.json" done ### Step 4: Render the dashboard Use the `patch` JSON as canonical for queue and siblings (identical across levels; only `.version` differs). Extract with `jq`: `.host` (github|gitlab|unknown), `.offline`, `.claimed` (array of {pr, branch, version, url}), `.siblings`, `.active_siblings`. Render in this format: GSTACK LANDING REPORT Repo: Base: @ v Host: Status: Open PRs claiming versions on : #1152 alpha-branch -> v1.7.0.0 #1153 beta-branch -> v1.7.0.0 WARNING: collision with #1152 #1151 gamma-branch -> v1.6.5.0 Sibling Conductor worktrees (): path branch VERSION last commit PR ../tokyo-v2 feat/dashboard v1.7.1.0 3h ago none * active ../melbourne feat/review v1.6.0.0 12d ago none ../osaka feat/payments v1.8.0.0 5h ago #1155 * active = VERSION ahead of base AND last commit < 24h AND no open PR. These are likely to ship soon. If you ran /ship right now, you'd claim: micro bump: v1.6.3.1 (queue-advance: none) patch bump: v1.7.1.0 (bumped past claimed 1.7.0.0) minor bump: v1.8.0.0 (bumped past claimed 1.7.0.0) major bump: v2.0.0.0 (no major collisions) (The numbers above are an example layout; fill with real data.) If offline or host unknown, print a shorter block: Status `OFFLINE - queue-awareness unavailable`, Reason ``, then "Fallback: local VERSION bumps still work, but collisions cannot be detected." ### Step 5: Suggest ONE next action 1. Collisions in the queue: "Two open PRs collide on v. Whoever merges second will either overwrite the first's CHANGELOG entry or land a duplicate. Consider asking one author to rerun /ship to pick up the next free slot." 2. An active sibling outranks the user's branch version: "Sibling worktree has v committed h ago and hasn't PR'd yet. If that work ships first, your branch will need to rebump at land time." 3. Otherwise: "Queue is clean. Next /ship will claim a slot without conflict." If sibling worktrees have commits weeks old, offer `bin/gstack-worktree-audit` (read-only audit). ## Output The rendered dashboard (or the offline block) followed by exactly one suggested next action. ## Credit Based on public content by garrytan, packaged by Orbit.

Gstack skill for read-only queue dashboard

What you’ll need

Gstack skill for read-only queue dashboard

What you’ll need