landing-report

Query local session state and git branches to report version slots and open pull requests.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/yocxy2/gstack3 --skill landing-report-yocxy2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/yocxy2/gstack3/tree/main/landing-report
Command: npx skills add https://github.com/yocxy2/gstack3 --skill landing-report-yocxy2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the lack of visibility into the engineering release pipeline by providing a centralized, read-only dashboard of active PRs, version slots, and upcoming ship readiness.

Core Features & Use Cases

  • Version Queue Monitoring: Instantly see which version slots are claimed by open PRs and which workspaces have work in progress.
  • Ship Readiness: Identify exactly what the /ship command will pick next based on current workspace state.
  • Use Case: Use this before starting a new task to ensure you aren't stepping on another developer's claimed version slot or to check the status of the current release queue.

Quick Start

Invoke the landing-report skill to display the current version queue and workspace status.

Frequently Asked Questions about landing-report

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

FAQPage Schema
How do I view the current version queue and open pull requests in a gstack environment?

To view the version queue and open pull requests, you can use a read-only dashboard that queries local session state and git branch information. This provides real-time visibility into ship readiness and workspace activity without mutating any pipeline state.

What is the best way to check ship readiness before starting a new engineering task?

Checking ship readiness involves monitoring version slots claimed by open PRs and work in progress. A non-mutating dashboard identifies exactly what the ship command will pick next based on current workspace state, preventing developers from stepping on claimed slots.

Does the ship dashboard modify my local git branches or release pipeline state?

The ship dashboard does not modify local git branches or release pipeline state. It operates as a strictly read-only monitoring tool by querying local session state and git branch data to report on version slots and workspace activity.

How does version queue monitoring work for local engineering workspaces?

Version queue monitoring works by querying local session state and git branch information to instantly see which version slots are claimed by open PRs. It displays read-only workspace status to help track the release pipeline and upcoming ship readiness.

When do I need to monitor version slots and workspace activity?

You need to monitor version slots and workspace activity before starting a new task to ensure you are not stepping on another developer's claimed version slot. It provides visibility into the engineering release pipeline and current queue status.

Can I use this dashboard to see what the ship command will pick next?

You can use this read-only dashboard to identify exactly what the ship command will pick next. It queries local session state and git branch information to report ship readiness based on the current workspace environment.