landing-report

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

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill landing-report-aicodepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/agent/skills/gstack/landing-report
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill landing-report-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple contributors and Conductor workspaces ship changes in parallel, it is hard to know which VERSION slots are already claimed by open PRs and which slot you should pick next. This Skill gives a read-only snapshot of the shipping queue so you avoid version collisions before running /ship. ## Core Features & Use Cases - Version queue visibility: 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 which slot /ship would pick next, with no mutations performed. - Use Case: Before shipping a change, ask for a landing report to confirm your target version slot is free and to see what else is queued to land. ## Quick Start Ask the assistant to run the landing report to show what is currently in the ship queue and which version slot to claim next.

Frequently Asked Questions about landing-report

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

FAQPage Schema
How do I see which version slots are claimed by open PRs?

Run the landing report skill, which scans open PRs and lists the VERSION slots they currently claim. It also shows sibling Conductor workspaces with WIP work likely to ship soon.

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

The landing report shows which slot /ship would pick next based on the current queue. Use it before shipping to avoid version collisions with other in-flight PRs.

Does the landing report modify my repository or PRs?

No, the landing report is strictly read-only. It only produces a snapshot of the queue state and performs no mutations on branches, PRs, or workspace state.

Can I use the landing report outside a Conductor workspace setup?

Yes, it works in any git repository with gstack installed, but the workspace-awareness features are most useful when multiple Conductor workspaces ship in parallel.

Why does the landing report show no queued work?

An empty report means no open PRs currently claim VERSION slots and no sibling workspaces have WIP work detected. Verify you are on the correct branch and that open PRs exist in the remote repository.