landing-report

Monitor version queues and active pull request status across Conductor workspaces.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/smarmen86/claude-code-kit --skill landing-report-smarmen86
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/smarmen86/claude-code-kit/tree/main/skills/landing-report
Command: npx skills add https://github.com/smarmen86/claude-code-kit --skill landing-report-smarmen86

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a clear, read-only snapshot of your project's version queue, helping you understand which PRs are active and what version is next in line for deployment.

Core Features & Use Cases

  • Queue Monitoring: Instantly see which version slots are claimed by open PRs.
  • Workspace Awareness: Identify sibling Conductor workspaces with work-in-progress that is likely to ship soon.
  • Deployment Planning: Determine exactly which version slot the ship command will target next without making any accidental mutations.

Quick Start

Ask the agent to show the landing report to see the current status of your version queue and open pull requests.

Frequently Asked Questions about landing-report

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

FAQPage Schema
How do I monitor active pull requests and version queues for deployment planning?

You can check the status of your version queue and open pull requests by asking the agent to display the landing report. This provides a read-only snapshot of active PRs and claimed version slots without making any accidental mutations.

How do I see which version slot the ship command will target next?

To see which version slot the ship command will target next, request a read-only deployment planning dashboard. It surfaces the exact upcoming ship targets by aggregating branch data across your project workspaces.

Can I track work-in-progress across multiple Conductor workspaces?

You can track work-in-progress across multiple Conductor workspaces using a coordination dashboard. It identifies sibling workspaces with WIP status that is likely to ship soon, preventing accidental version slot collisions.

Do I need the gstack binary toolkit to check pull request status?

You need git and access to the gstack binary toolkit to check pull request status comprehensively. The toolkit is required to aggregate session and branch data across multiple Conductor workspaces into a single dashboard view.

What is the best way to view upcoming deployment targets without accidentally mutating git branches?

The best way to view upcoming deployment targets without accidental mutations is a read-only version queue dashboard. It displays active pull request status and ship targets while strictly preventing changes to your branch state.