landing-report

## 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 ```bash eval "$(~/.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/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 5-10 parallel Conductor workspaces, it helps to see — at a glance — which version numbers are claimed, by whom, and what slot your next `/ship` would land in. This skill is a read-only call into the same `~/.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. ```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" ``` --- ...