skills.rest
sanjanb
sanjanbCOMMUNITY
Explore all skills by this author →
GitHub

landing-report

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

1|Updated Jul 23, 2026
Search Tags:#git#dashboard#pull requests#release coordination#gstack#version queue#conductor workspaces
One-click install
npx skills add https://github.com/sanjanb/my-agent-harness --skill landing-report-sanjanb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/landing-report
Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill landing-report-sanjanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple developers or AI agents ship versioned releases from parallel Conductor workspaces, it is hard to know which VERSION slots are already claimed by open PRs and which slot the next /ship run will pick. This Skill answers that question instantly without mutating anything. ## Core Features & Use Cases - Version Queue Snapshot: Shows which VERSION slots are currently claimed by open pull requests. - Workspace Awareness: Surfaces sibling Conductor workspaces with WIP work likely to ship soon. - Next-Slot Prediction: Reports which slot /ship would claim next, so you can plan releases without collisions. - Use Case: Before running /ship on a feature branch, ask for a landing report to confirm your target version is not already taken by a teammate's open PR. ## Quick Start Ask the agent to show the landing report for the current repository to see open PR versions and the next available version slot.

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 slot my next ship will claim?▼

Invoke the landing report skill, which reads open PR versions and sibling workspace state to report exactly which VERSION slot /ship would pick next. It performs no mutations, so it is safe to run at any time.

How to see open PR versions across Conductor workspaces?▼

Run the landing report to get a snapshot of all VERSION slots claimed by open PRs plus sibling Conductor workspaces holding WIP work likely to ship soon. This gives a single queue view across parallel workspaces.

Does the landing report modify my repository or PRs?▼

No, the landing report is strictly read-only. It only inspects git branch state, open PRs, and workspace metadata to render a queue dashboard, and never commits, pushes, or edits files.

Can I run the landing report in a headless or CI session?▼

Yes, the skill detects the session kind via its preamble and adapts behavior. In headless sessions it skips interactive prompts and renders the queue snapshot directly as prose output.

Why does the landing report show an unexpected next version?▼

The next slot is computed from currently open PRs and active sibling workspaces, so a newly opened PR or a teammate's WIP workspace can shift the prediction. Re-run the report after PRs merge or close to get an updated slot.

Related Skills

Explore More Software Engineering Skills→
tayiorbeiitayiorbeii

gstack-landing-report

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

Community
Intermediate
kk20300113-pngkk20300113-png

landing-report

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

Community
Advanced
YunosukeYoshinoYunosukeYoshino

pr

Verify quality gates and artifacts before generating a PR summary and Codex review request.

Community
Intermediate
muhammadhamad1104muhammadhamad1104

landing-report

Generate a read-only snapshot of version control queues and open pull requests in a gstack workspace.

Community
Advanced