skills.rest
tayiorbeii
tayiorbeiiCOMMUNITY
Explore all skills by this author →
GitHub

gstack-landing-report

Displays a read-only dashboard of version slots claimed by open PRs and queued workspaces.

Updated Jun 24, 2026
Search Tags:#git workflow#dashboard#pull requests#ship#release coordination#version queue#conductor workspaces
One-click install
npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill gstack-landing-report-tayiorbeii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-landing-report
Source: https://github.com/tayiorbeii/paperclip-factory-kit-hermes/tree/main/skills/paperclip/gstack-landing-report
Command: npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill gstack-landing-report-tayiorbeii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple branches and Conductor workspaces compete to ship, it is hard to know which VERSION slots are already claimed by open PRs and which version number is safe to claim next. This Skill gives a read-only snapshot of the ship queue so you avoid version collisions before running /ship. ## Core Features & Use Cases - Version Queue Dashboard: Shows which VERSION slots are currently claimed by open PRs. - Workspace Awareness: Surfaces sibling Conductor workspaces with WIP work likely to ship soon. - Next-Slot Prediction: Reports what slot /ship would pick next, with no mutations to the repo. - Use Case: Before shipping a release, ask for a landing report to confirm your target version is unclaimed and see which teammates' PRs are ahead of you in the queue. ## Quick Start Ask the assistant to run the landing report and show which version slots are claimed by open PRs and which version I should claim next.

Frequently Asked Questions about gstack-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?▼

Run the landing report to get a snapshot of every VERSION slot currently claimed by open PRs. It also shows which sibling workspaces have work in progress likely to ship soon, so you can pick an unclaimed version.

How do I know which version number to claim next before shipping?▼

The landing report computes what slot the /ship command would pick next based on the current queue. Use that output to claim a version that does not collide with open PRs or pending workspace work.

Does the landing report modify my repository or git state?▼

No, the landing report is strictly read-only. It only inspects open PRs, workspace state, and version slots to produce a snapshot, and it performs no mutations, commits, or pushes.

Can I use the landing report with multiple Conductor workspaces?▼

Yes, the report is workspace-aware. It scans sibling Conductor workspaces for WIP branches likely to ship soon and includes them in the queue view alongside open PRs.

When should I run a landing report instead of just shipping?▼

Run it before invoking /ship whenever multiple contributors or workspaces ship concurrently. It prevents version collisions by showing claimed slots and the next available version before you commit to a release.

Related Skills

Explore More Software Engineering Skills→
robertzengcnrobertzengcn

landing-report

Track claimed version slots from pull requests and Conductor workspaces.

Community
Advanced
kk20300113-pngkk20300113-png

landing-report

Display a read-only version queue dashboard for shipping workflows.

Community
Advanced
SpecForgeAISpecForgeAI

sp_verification

Run verification commands and evaluate outputs before completion claims.

Official
Intermediate
alexaundrealexaundre

yeet

Stage, commit, push, and open a GitHub pull request via the GitHub CLI.

Community
Intermediate