landing-report

Display gstack version queue status with claimed PR slots and next ship slot.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork of tracking which version slots are claimed by open PRs, which sibling Conductor workspaces have WIP work ready to ship, and what slot the /ship command would allocate next, without requiring you to run mutation commands or manually cross-reference multiple data sources.

Core Features & Use Cases

  • Read-Only Version Queue Dashboard: Displays all claimed VERSION slots tied to open PRs in your repository.
  • Sibling Workspace WIP Detection: Surfaces work-in-progress changes from sibling Conductor workspaces that are likely to ship soon.
  • Next Slot Prediction: Shows exactly which version slot the /ship command would pick if run today.
  • Use Case: For engineering teams using gstack for release management, use this Skill to avoid claiming an already-allocated version slot for your PR, or to plan your next ship target without risking unintended repository changes.

Quick Start

Use the landing-report skill to view the current version queue, claimed PR 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 gstack version queue for open PRs without mutating repository state?

To check the gstack version queue without mutating repository state, use a read-only dashboard that surfaces claimed version slots for open PRs and WIP changes from sibling Conductor workspaces. This prevents allocation conflicts during PR planning.

What is the best way to track sibling Conductor workspaces with WIP work ready to ship?

Tracking sibling Conductor workspaces with WIP work ready to ship requires a read-only report that detects work-in-progress changes across workspaces. This identifies potential ship conflicts and shows exactly what slot the /ship command would allocate next.

How does next slot prediction work for gstack release management?

Next slot prediction for gstack release management works by analyzing the current version queue status and claimed PR slots. It surfaces exactly which version slot the /ship command would pick if run today, helping teams plan their next ship target without unintended repository changes.

Can I use this version queue dashboard to avoid claiming an already allocated version slot for my PR?

Yes, you can use this version queue dashboard to avoid claiming an already allocated version slot for your PR. It provides a no-side-effect view of all claimed version slots tied to open PRs, preventing allocation conflicts during ship planning.

Does this read-only release tracking report require any specific dependencies or environment setup?

This read-only release tracking report requires no specific dependencies or environment setup. It functions as a standalone no-side-effect dashboard that surfaces version slot allocation data directly for engineering teams coordinating ship operations.