landing-report

Display a read-only snapshot of VERSION slots claimed by open PRs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only queue dashboard for workspace-aware ship planning. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot.

Core Features & Use Cases

  • Read-only queue dashboard for workspace-aware ship planning across Conductor workspaces.
  • Shows which VERSION slots are claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot/ship would pick next.
  • Use when asked to "landing report", "what's in the queue", "show me open PR versions", or "which version do I claim next".

Quick Start

Ask me for the landing report to view the current version queue snapshot for your workspace and identify next shipping targets.

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 claimed by open PRs?

A landing report provides a read-only snapshot of the workspace version queue, showing exactly which VERSION slots are currently claimed by open PRs. This dashboard displays current slot occupancy without mutating any underlying repository data.

What is the best way to check sibling Conductor workspaces for WIP shipping activity?

Checking sibling Conductor workspaces for WIP shipping activity is done by generating a landing report. It displays a read-only queue dashboard showing which sibling workspaces have work in progress likely to ship soon and their occupied version slots.

How do I find out which version slot /ship would pick next for my workspace?

To find out which version slot /ship would pick next, run a landing report to snapshot the workspace version queue. The dashboard identifies the specific version slot that ship planning will target next based on current open PR occupancy.

Can I use a landing report to modify repository state during ship planning?

You cannot use a landing report to modify repository state during ship planning. It is a strictly read-only, non-mutating dashboard that snapshots the version queue and slot occupancy without applying any changes to the underlying data.

Does the queue dashboard support workspace-aware ship planning across multiple Conductor workspaces?

The queue dashboard fully supports workspace-aware ship planning across multiple Conductor workspaces. It reads repository state to present a snapshot of which sibling workspaces have WIP work likely to ship soon and their respective version slot claims.