skills.rest
zhu637882-stack
zhu637882-stackCOMMUNITY
Explore all skills by this author →
GitHub

landing-report

Read PRs and Conductor workspaces to present the version-queue state.

1|Updated Apr 6, 2026
Search Tags:#dashboard#workspace#pr#wip#landing-report#version-queue
One-click install
npx skills add https://github.com/zhu637882-stack/jiaoyi --skill landing-report-zhu637882-stack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/zhu637882-stack/jiaoyi/tree/main/qoder-config-backup/skills/gstack-landing-report
Command: npx skills add https://github.com/zhu637882-stack/jiaoyi --skill landing-report-zhu637882-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a read-only, workspace-aware snapshot of version slot allocations, showing which slots are currently claimed by open PRs and which Conductor workspaces have WIP that might ship soon, enabling quick assessment without altering state.

Core Features & Use Cases

  • Read-only Version Queue: surfaces slot occupancy and next-shipment candidates across related workspaces.
  • Cross-workspace visibility: correlates PRs, WIP, and slot availability to support release planning.
  • Use Case: when asked for the landing report, “what’s in the queue,” or “which version do I claim next,” you get a current, non-mutating snapshot.

Quick Start

Run the landing-report command in a workspace with open PRs to view the current version queue.

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 status for open pull requests and workspaces?▼

To check the version queue status, you can run a landing report to view a read-only snapshot of slot occupancy across open pull requests and sibling workspaces without altering repository state.

What is a landing report and how does it show claimed version slots?▼

A landing report is a read-only snapshot that identifies which version slots are currently claimed by open pull requests and which Conductor workspaces have upcoming work in progress.

How do I find out which version slot to claim next for my release?▼

You can find the next version slot to claim by running a landing report, which correlates pull requests, work in progress, and slot availability to display the next shipment candidate.

Can I view the workspace WIP queue without modifying repository state?▼

Yes, you can view the workspace WIP queue without modifying repository state because the landing report operates read-only and relies entirely on repository metadata and workspace context.

Does the version queue snapshot work with Conductor workspaces and open pull requests?▼

The version queue snapshot works by reading Conductor workspaces and open pull requests to surface cross-workspace visibility, correlating WIP and slot availability to support release planning.

What are the limitations of using a read-only version queue snapshot for release planning?▼

The limitation of a read-only version queue snapshot is that it only displays current queue state and does not mutate repository state, meaning it cannot reserve slots or advance the shipment process.

Related Skills

Explore More Software Engineering Skills→
miko06miko06

landing-report

Generate a static snapshot of open pull requests and version queue status.

Community
Advanced
wodehwodeh

landing-report

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

Community
Intermediate
vnmoorthyvnmoorthy
2

landing-report

Display a read-only dashboard of VERSION slots claimed by open PRs and upcoming WIP.

Community
Intermediate
robertzengcnrobertzengcn

landing-report

Track claimed version slots from pull requests and Conductor workspaces.

Community
Advanced