skills.rest
abdulazeezoj
abdulazeezojCOMMUNITY
Explore all skills by this author →
Website𝕏@abdulazeezojGitHub

landing-report

Displays which version slots are claimed by open PRs and workspaces.

Updated Sep 13, 2026
Search Tags:#release management#dashboard#pull requests#ship#github cli#version queue#conductor workspaces
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill landing-report-abdulazeezoj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/gstack/landing-report
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill landing-report-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running multiple parallel Conductor workspaces, it is hard to know which VERSION numbers are already claimed by open PRs, which sibling workspaces have work likely to ship soon, and which slot the next /ship run would pick. This Skill answers that with a single read-only snapshot. ## Core Features & Use Cases - Version queue dashboard: Shows which VERSION slots are claimed by open PRs and by whom. - Workspace awareness: Surfaces sibling Conductor workspaces with WIP work likely to ship soon. - Next-slot prediction: Reports which slot /ship would claim next, using the same gstack-next-version utility /ship uses. - Read-only guarantee: No mutations, so it is safe to run any time, like gh pr list for VERSION numbers. - Use Case: Before starting a release, ask for a landing report to see open PR versions, pick an unclaimed version number, and avoid collisions with other in-flight branches. ## Quick Start Ask the assistant to run a landing report to show which version slots are claimed 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 numbers are claimed by open PRs?▼

Run the landing report, which lists every VERSION slot currently claimed by open PRs along with sibling Conductor workspaces carrying WIP work. It reads the same data /ship uses, so the queue you see matches what a real ship would encounter.

How do I know which version my next ship will claim?▼

The landing report calls the same gstack-next-version utility that /ship uses and reports the slot it would pick next. This lets you confirm the target version before actually shipping anything.

Does the landing report modify my repository or PRs?▼

No. The skill is strictly read-only: it only queries open PRs, workspace state, and the version utility, then renders a snapshot. Nothing is committed, pushed, or mutated, so it is safe to run at any time.

When should I run a landing report instead of gh pr list?▼

Use it when you manage several parallel Conductor workspaces and need version-claim context, not just PR titles. It adds workspace WIP detection and next-slot prediction on top of what a plain PR listing shows.

What happens if the gstack preamble tooling is missing or stale?▼

The skill enters a degraded mode: it treats the session as interactive, skips onboarding and telemetry steps, tells you to run ./setup or /gstack-upgrade, and still proceeds with the read-only report.

Related Skills

Explore More Software Engineering Skills→
cloudofgeorgecloudofgeorge

landing-report

Generate a read-only landing report of version slots and workspace status.

Community
Intermediate
kk20300113-pngkk20300113-png

landing-report

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

Community
Advanced
samjonestersamjonester
5

mozart-wtp-pr-review

Open a Mozart PR review in a dedicated WTP worktree from a PR number or branch name.

Community
Advanced
thisguymartinthisguymartin

pr

Create or update pull requests with semantic commits and structured descriptions.

Community
Intermediate