landing-report

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of tracking version slot allocation for teams using gstack for versioned shipping, eliminating the need to cross-check open PRs, sibling workspace WIP, and /ship command logic to avoid version conflicts.

Core Features & Use Cases

  • Read-Only Version Queue Dashboard: Shows exactly which VERSION slots are claimed by open PRs in your repository.
  • Sibling Workspace WIP Tracking: Surfaces work in progress from sibling Conductor workspaces likely to ship soon, so you can adjust your version claims proactively.
  • Next Ship Slot Prediction: Identifies the exact version slot the /ship command would allocate next, removing guesswork from PR landing planning.
  • Use Case: Use this when preparing to land a PR to ensure you claim an available version slot that won't conflict with in-flight or upcoming work from your team.

Quick Start

Request a landing report to see the current version queue, open PR claimed version slots, and the next available ship slot for your project.

Frequently Asked Questions about landing-report

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

FAQPage Schema
How do I check the version queue and next ship slot before landing a PR?

To check the version queue and next ship slot, request a landing report to view a read-only dashboard. It surfaces claimed VERSION slots from open PRs, WIP work from sibling Conductor workspaces, and the exact slot /ship would allocate next.

What is a landing report in gstack versioned shipping workflows?

A landing report is a read-only dashboard for workspace-aware shipping workflows. It displays claimed VERSION slots from open PRs, sibling Conductor workspace WIP likely to ship soon, and the next slot /ship would allocate to prevent version conflicts.

How do I track sibling Conductor workspace WIP that might conflict with my version slot?

You track sibling Conductor workspace WIP by requesting a landing report. This read-only dashboard surfaces work in progress from sibling workspaces likely to ship soon, allowing you to proactively adjust your version claims and avoid landing conflicts.

Does the landing report dashboard mutate my repository state when checking PR slots?

No, the landing report dashboard does not mutate repository state. It operates as a strictly read-only view that safely surfaces open PR claimed version slots, sibling workspace WIP, and next ship slot predictions without altering repository files.

Can I predict the exact version slot the /ship command will allocate next?

Yes, you can predict the exact version slot the /ship command will allocate next. The landing report dashboard identifies the specific next available ship slot, removing guesswork from PR landing planning and version allocation.