skills.rest
raghavbadhwar
raghavbadhwarCOMMUNITY
Explore all skills by this author →
GitHub

landing-report

Displays a read-only dashboard of version slots claimed by open PRs and queued workspaces.

Updated Aug 9, 2026
Search Tags:#git#release management#dashboard#pull requests#conductor#ship#version queue
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill landing-report-raghavbadhwar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/raghavbadhwar/rstack/tree/main/landing-report
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill landing-report-raghavbadhwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple pull requests and Conductor workspaces compete for the next release version, it is hard to know which VERSION slots are already claimed and which slot /ship would pick next. This Skill gives a read-only snapshot of the version queue so you can plan releases without mutating anything. ## Core Features & Use Cases - Version Queue Snapshot: Shows which VERSION slots are currently claimed by open PRs. - Workspace Awareness: Surfaces sibling Conductor workspaces with WIP work likely to ship soon. - Next-Slot Prediction: Reports which slot /ship would claim next, with zero mutations. - Use Case: Before starting a release, ask for a landing report to see open PR versions, confirm no conflicts with other workspaces, and decide which version number to claim. ## Quick Start Ask the agent to run the landing report to show which versions are claimed by open PRs and which version comes next.

Frequently Asked Questions about landing-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I see which version slots are claimed by open PRs?▼

Invoke the landing report to get a snapshot of VERSION slots currently claimed by open pull requests. It also shows sibling Conductor workspaces with WIP work and which slot /ship would pick next, without changing anything.

What version should I claim next before shipping?▼

Run the landing report before /ship. It predicts the next available version slot based on open PRs and queued workspace work, so you avoid version collisions across parallel release branches.

Does the landing report modify my repository or PRs?▼

No. The landing report is strictly read-only. It only inspects open PRs, workspace state, and version claims to render a dashboard, and it performs no mutations on branches, PRs, or files.

Can I use the landing report outside a Conductor workspace setup?▼

Yes, but its workspace-awareness features are most useful with Conductor. Without sibling workspaces, it still reports open PR version claims and the next slot /ship would select in a standard git repository.

Why does the landing report show a different next version than I expected?▼

The next-slot prediction accounts for versions already claimed by open PRs and WIP workspaces, not just the latest merged release. A claimed-but-unmerged slot shifts the prediction upward.

Related Skills

Explore More Software Engineering Skills→
TumeloRamaphosaTumeloRamaphosa

landing-report

Generate a read-only queue snapshot of claimed version slots and sibling workspace WIP.

Community
Basic
kk20300113-pngkk20300113-png

landing-report

Display a read-only version queue dashboard for shipping workflows.

Community
Advanced
BedaBeda-GrowthBedaBeda-Growth

ci-verify

Queue open PRs into a testing branch and run tiered verification gates.

Official
Advanced
tgmarinhotgmarinho

landing-report

Displays a read-only dashboard of version slots claimed by open PRs and queued workspaces.

Community
Advanced