release-status

Diagnose the release-please pipeline and report why a release did or didn't fire — read-only. The skill gathers four independent signals via gh and git, prints a structured report, and surfaces the remediation for each. It writes nothing: no commits, no labels, no PR edits, no releases.

Relationship to /send-it

This is a sibling of send-it, not invoked by it. send-it is the pre-merge ship flow — it stops at In Review (opens the PR, transitions the Linear issue). release-status picks up after merge: it inspects the state of main, the release PR, and the tags to explain what the release machinery is doing. The two never call each other. This skill may reference send-it in prose (e.g. how /send-it composes a Conventional-Commit PR title from branch commits), but it never runs it. Version preview itself reads commits since the last tag (merge commits excluded) — the same per-commit signal release-please uses under multi-commit history (A-824) — not merged PR titles.