skills.rest
tgmarinho
tgmarinhoCOMMUNITY
Explore all skills by this author →
Website𝕏@tgmarinhoGitHub

landing-report

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

Updated May 15, 2026
Search Tags:#git#release management#dashboard#pull requests#ship#version queue#conductor workspaces
One-click install
npx skills add https://github.com/tgmarinho/canetaco --skill landing-report-tgmarinho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: landing-report
Source: https://github.com/tgmarinho/canetaco/tree/main/.claude/skills/landing-report
Command: npx skills add https://github.com/tgmarinho/canetaco --skill landing-report-tgmarinho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple developers or AI workspaces ship changes in parallel, version numbers collide and it is hard to know which slot is safe to claim next. This Skill gives a snapshot of the ship queue so you avoid version conflicts before running /ship. ## Core Features & Use Cases - Version Queue Snapshot: Shows which VERSION slots are currently claimed by open PRs. - Workspace Awareness: Lists sibling Conductor workspaces with WIP work likely to ship soon. - Next Slot Prediction: Reports which version slot /ship would pick next, with no mutations to the repo. - Use Case: Before shipping a release branch, run the report to confirm your target version is not already claimed by a teammate's open PR. ## Quick Start Ask the assistant to run the landing report to show which versions are claimed and which version comes next.

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 number to claim before shipping?▼

Run the landing report to see which VERSION slots are already claimed by open PRs and which slot /ship would pick next. It is read-only, so you can check freely without changing any state.

How to see open PRs and their claimed versions in one view?▼

The landing report aggregates open PRs and maps each to its claimed version slot, alongside sibling Conductor workspaces with WIP work. This gives a single queue view instead of checking PRs one by one.

Does the landing report modify my repository or PRs?▼

No. The skill is explicitly read-only and only produces a snapshot of the queue. It performs no mutations, commits, or PR changes, making it safe to run at any time including in plan mode.

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

Yes. The report is workspace-aware and inspects sibling Conductor workspaces to surface WIP work likely to ship soon, helping you anticipate version claims before those workspaces open PRs.

When should I run the landing report in the ship workflow?▼

Run it before invoking /ship, especially when several branches or agents are landing changes in parallel. It prevents version collisions by showing the next available slot and current queue state.

Related Skills

Explore More Software Engineering Skills→
TumeloRamaphosaTumeloRamaphosa

landing-report

Generate a read-only queue snapshot of claimed version slots and sibling workspace WIP.

Community
Basic
abdulazeezojabdulazeezoj

landing-report

Displays which version slots are claimed by open PRs and workspaces.

Community
Advanced
MissTullyMissTully

landing-report

Visualize the workspace version queue with PR slot claims and next ship slot.

Community
Intermediate
lepahclepahc
1

release

Automate versioned releases by bumping versions, tagging commits, and generating GitHub releases.

Official
Advanced