landing-report

Display current version slot allocations claimed by open PRs.

Updated May 6, 2026
One-click install
npx skills add https://github.com/stayconnectquick/gstack --skill landing-report-stayconnectquick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/stayconnectquick/gstack/tree/main/landing-report
Command: npx skills add https://github.com/stayconnectquick/gstack --skill landing-report-stayconnectquick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only snapshot of the current version slot allocations, showing which slots are claimed by open PRs to support release planning without mutating code.

Core Features & Use Cases

  • Read-only snapshot of version queues across workspace-aware ships and PRs to inform planning decisions.
  • Reveals which sibling Conductor workspaces have work-in-progress likely to ship soon, and which slot/ship would be claimed next.
  • Enables quick verification of release readiness without making mutations.

Quick Start

View the current queue snapshot by running the landing-report skill to display the latest state.

Frequently Asked Questions about landing-report

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

FAQPage Schema
How do I view which version slots are currently claimed by open PRs?

To view version slot allocations claimed by open PRs, run the landing-report skill to generate a read-only snapshot of the current repository state and release queue without making any mutations.

What is the best way to track work-in-progress across sibling Conductor workspaces?

Tracking work-in-progress across sibling Conductor workspaces is done by generating a workspace-aware snapshot that reveals which environments have open PRs likely to ship soon and which slot would be claimed next.

Does the version queue snapshot modify my repository state during ship planning?

The version queue snapshot does not modify your repository state during ship planning because the surface is strictly read-only and deterministic, loading context to display slot allocations without executing any mutations.

Can I use landing-report to see which ship slot would be claimed next in a workspace-aware environment?

You can use landing-report in a workspace-aware environment to see which ship slot would be claimed next, as it identifies current version slot allocations and reveals the queue position of open PRs across sibling Conductor workspaces.