landing-report

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

2|1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/vnmoorthy/Skylog --skill landing-report-vnmoorthy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/vnmoorthy/Skylog/tree/main/.claude/skills/gstack/landing-report
Command: npx skills add https://github.com/vnmoorthy/Skylog --skill landing-report-vnmoorthy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only dashboard for workspace-aware ship that shows which VERSION slots are claimed by open PRs, which sibling Conductor workspaces have WIP that might ship soon, and what slot/ship would be picked next. No mutations; you can see the current state without changing anything.

Core Features & Use Cases

  • Read-only queue dashboard showing version slot ownership by PRs and WIP status.
  • Identify the next slot/ship to claim for planning releases.
  • Quick sanity check of workspace activity across Conductor workspaces to inform decisions.

Quick Start

Ask for the landing report to display the current queue snapshot.

Frequently Asked Questions about landing-report

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

FAQPage Schema
How do I check which version slots are claimed by open PRs across Conductor workspaces?

You can check version slots claimed by open PRs by viewing a read-only dashboard that reads current PR activity and workspace state to display a deterministic snapshot of the version queue.

How does a read-only version queue dashboard work for release planning?

A read-only version queue dashboard works by scanning workspace WIP status and open PRs, presenting the current queue snapshot and identifying the next slot to claim without mutating any state.

Can I preview workspace WIP status without mutating Conductor state?

Yes, you can preview workspace WIP status without mutating state because the dashboard operates strictly in read-only mode to present a deterministic snapshot of upcoming work and version slot ownership.

What is the best way to identify the next version slot to claim for a release?

The best way to identify the next version slot to claim is to review a queue snapshot that maps open PRs to VERSION slots and highlights which sibling workspaces have WIP ready to ship soon.

What are the limitations of using a read-only workspace queue dashboard?

The main limitation of a read-only workspace queue dashboard is that it cannot mutate state; it provides a deterministic snapshot for planning and sanity checks but does not claim slots or execute releases.

Do I need gstack to view the version queue across workspaces?

To view the version queue across workspaces, you need an environment with accessible Conductor workspaces and open PR activity data, allowing the dashboard to read current state and present the queue snapshot.