timurgaleev/vibestack / skills/landing-report
landing-report
VerifiedRead-only snapshot of the VERSION slots open PRs claim on the base branch and the slot /ship would pick next.
If this session was compacted, the copy of this skill in context may be cut off.
Read ${CLAUDE_SKILL_DIR}/SKILL.md from disk and resume at the step you are on.
When to invoke
Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next".
Preamble
eval "$("${VIBESTACK_HOME:-$HOME/.vibestack}/bin/vibe-slug" 2>/dev/null)" 2>/dev/null || SLUG="unknown"
_LEARN_FILE="${VIBESTACK_HOME:-$HOME/.vibestack}/projects/${SLUG:-unknown}/learnings.jsonl"
if [ -f "$_LEARN_FILE" ]; then
_LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ')
echo "LEARNINGS: $_LEARN_COUNT entries loaded"
if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then
"${VIBESTACK_HOME:-$HOME/.vibestack}/bin/vibe-learnings-search" --limit 5 2>/dev/null || true
fi
else
echo "LEARNINGS: none yet"
fi
{{include lib/snippets/session-host.md}}
{{include lib/snippets/working-protocols.md}}
{{include lib/snippets/state-protocols.md}}
Why this skill exists
When you're running several branches in parallel, it helps to see — at a
glance — which version numbers are claimed, by which PR, and what slot your next
/ship would land in. This skill is a read-only call into the same
"${VIBESTACK_HOME:-$HOME/.vibestack}/bin/vibe-next-version" utility /ship uses, but with nothing mutating.
Think of it as gh pr list for VERSION numbers.
Step 1: Detect platform and base branch
Same detection as other vibestack skills.
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"
Each block runs in a fresh shell. Later blocks start with BASE_BRANCH='<BASE_BRANCH>'
and BASE_VERSION='<BASE_VERSION>': replace each placeholder with the value printed
under that label.
Step 2: Read current state
BASE_BRANCH='<BASE_BRANCH>'
CURRENT_VERSION=$(tr -d '[:space:]' 2>/dev/null < VERSION)
[ -n "$CURRENT_VERSION" ] || CURRENT_VERSION=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:]')
[ -n "$BASE_VERSION" ] || BASE_VERSION=$CURRENT_VERSION
echo "BASE_VERSION: $BASE_VERSION"
echo "branch HEAD VERSION: $CURRENT_VERSION"
Step 3: Query the queue
Call the util once per bump level so the user sees what they'd claim for
patch/minor/major. Versions are MAJOR.MINOR.PATCH with an optional fourth
MICRO part; the pick keeps the base version's shape.
BASE_BRANCH='<BASE_BRANCH>'
BASE_VERSION='<BASE_VERSION>'
LANDING_DIR=$(mktemp -d "${TMPDIR:-/tmp}/landing-XXXXXX")
echo "LANDING_DIR: $LANDING_DIR"
for LEVEL in patch minor major; do
"${VIBESTACK_HOME:-$HOME/.vibestack}/bin/vibe-next-version" \
--base "$BASE_BRANCH" \
--bump "$LEVEL" \
--current-version "$BASE_VERSION" \
> "$LANDING_DIR/$LEVEL.json" 2>/dev/null || echo '{"offline":true,"complete":false,"reason":"vibe-next-version failed","claimed":[],"warnings":[]}' > "$LANDING_DIR/$LEVEL.json"
done
Step 4: Render the dashboard
Read <LANDING_DIR>/patch.json, <LANDING_DIR>/minor.json and
<LANDING_DIR>/major.json, replacing <LANDING_DIR> with the path Step 3 printed
on the LANDING_DIR: line. Build a single table output. Use the patch-level JSON
as canonical for the queue (it is identical across bump levels; only .version
differs).
vibe-next-version emits exactly these fields — render only what they contain:
.host—github|gitlab|git(no PR host answered; claims are the VERSION at each fetched branch head) |unknown.base— the base branch the queue was filtered to.offline—truewhen no PR host was reachable (also with"host":"git").reason— one-line explanation of the pick (or of the offline fallback).claimed— array of{pr, branch, version, url}: open PRs against.basewhose headVERSIONis ahead of the base version. Read from each PR's headVERSIONfile, not its title..warnings— PRs whose headVERSIONcould not be read or is malformed.complete—trueonly when every open PR'sVERSIONwas read;falsewhen the PR list was truncated or any read failed.version— the slot/shipwould claim at this bump level
Sibling worktree detection is not supported: .active_siblings is always an
empty list. Do not render a sibling section, and do not infer siblings from
git worktree list or anywhere else. A PR number, branch or version that is
not in .claimed does not exist — never fill a row in from memory or a guess.
Render in this exact format:
╔══════════════════════════════════════════════════════════════════╗
║ VIBESTACK LANDING REPORT ║
╠══════════════════════════════════════════════════════════════════╣
║ Repo: <owner/repo> ║
║ Base: <.base> @ v<base-version> ║
║ Host: <.host> ║
║ Status: ONLINE (or: ONLINE — queue may be incomplete) ║
╚══════════════════════════════════════════════════════════════════╝
Open PRs claiming versions on <.base>:
#<pr> <branch> → v<version>
#<pr> <branch> → v<version> ⚠ collision with #<pr>
Warnings:
<one line per entry in .warnings; omit the section when empty>
If you ran /ship right now, you'd claim:
patch bump: v<patch .version> (<patch .reason>)
minor bump: v<minor .version> (<minor .reason>)
major bump: v<major .version> (<major .reason>)
When .complete is false, the Status line reads ONLINE — queue may be incomplete and
Step 5 gives suggestion 2: a slot that looks free may already be claimed by a PR the read
missed. When .complete is true, the output is unchanged.
A collision is two entries in .claimed with the same version, compared with any
trailing .0 parts dropped: 1.2.4 and 1.2.4.0 are one slot. When
.claimed is empty, print Open PRs claiming versions on <.base>: none.
When .host is git, render the full table with the Status line
OFFLINE — branch heads, not the PR queue and suggestion 2 in Step 5: a branch without
a PR still counts, and an unfetched head is a warning.
For any other offline output (.offline is true), print a shorter block:
╔══════════════════════════════════════════════════════════════════╗
║ VIBESTACK LANDING REPORT ║
╠══════════════════════════════════════════════════════════════════╣
║ Status: OFFLINE — queue-awareness unavailable ║
║ Reason: <.reason> ║
╚══════════════════════════════════════════════════════════════════╝
Fallback: local VERSION bumps still work, but collisions cannot be detected.
Step 5: Suggest next action
After rendering the table, suggest ONE of:
-
If there are collisions in the queue (two open PRs claim the same version): "⚠ 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."
-
If
.warningsis non-empty or.completeisfalse: "Some open PRs' VERSION could not be read (listed above), so the queue may be incomplete. Check those PRs before trusting the next slot." -
If everything looks clean: "Queue is clean. Next /ship will claim a slot without conflict."
Plan Mode
PLAN MODE EXCEPTION — ALWAYS RUN. This skill is entirely read-only: no file writes, no git mutations, no network state changes. Safe to run in plan mode.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |