skills.rest
acme-skunkworks
acme-skunkworksOFFICIAL
Explore all skills by this author →
GitHub

release-status

Diagnose GitHub release pipeline issues using gh CLI and git.

Updated Jul 10, 2026
Search Tags:#versioning#github#release pipeline#release monitoring#release diagnosis
One-click install
npx skills add https://github.com/acme-skunkworks/changelog-core --skill release-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-status
Source: https://github.com/acme-skunkworks/changelog-core/tree/main/.agents/skills/release-status
Command: npx skills add https://github.com/acme-skunkworks/changelog-core --skill release-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, and includes scripts (resource) components.

What problem does it solve?

This Skill helps diagnose and monitor the health of the release pipeline, identifying issues such as release stalls, version mismatches, and incomplete PRs.

Core Features & Use Cases

  • Release Pipeline Diagnostics: Analyze the release pipeline for potential issues such as stale PRs and version mismatches.
  • Version Preview: Predict the next version based on merged PRs.
  • Release PR Status: Check the status of the open release PR and its required checks.
  • Use Case: When a release doesn't trigger as expected, use this Skill to identify if there's a stale PR, version mismatch, or other issues blocking the release.

Quick Start

Run the release-status skill to check the health of your release pipeline.

Frequently Asked Questions about release-status

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

FAQPage Schema
Why is my GitHub release pipeline stalled and not triggering?▼

Release pipeline stalls are often caused by stale PRs, version mismatches, or incomplete PRs. Diagnosing these release issues involves analyzing repository data to identify blocked checks and pipeline health.

How do I check the status of an open release PR and its required checks on GitHub?▼

To check a release PR status, analyze the open pull request and its required checks within your GitHub repository. This diagnosis operates read-only to identify incomplete PRs blocking the pipeline.

Can I predict the next release version based on merged PRs?▼

Yes, you can preview the next version by analyzing merged PRs in the repository. This feature evaluates merged pull requests to forecast the upcoming release version.

Do I need the gh CLI and git installed to monitor release pipeline health?▼

Yes, monitoring release pipeline health requires both the gh CLI and git. These dependencies provide the necessary read-only access to retrieve repository data for diagnosing release stalls and version mismatches.

Will diagnosing release issues modify my GitHub repository?▼

No, diagnosing release issues operates on a read-only basis and does not modify the repository. It strictly analyzes repository data to identify release stalls, version mismatches, and incomplete PRs.

Related Skills

Explore More Software Engineering Skills→
faccomichelefaccomichele

github-read-access

Inspect GitHub repository data, issues, pull requests, releases, and CI runs via gh CLI.

Community
Intermediate
utensilsutensils
134

source-command-release

Merge release PRs after explicit user confirmation with GitHub Actions.

Official
Advanced
psmonpsmon
8

agent-zero-build

Automate AgentZero Lite releases by syncing work, bumping versions, and pushing annotated tags.

Community
Advanced
AshleyHollisAshleyHollis

ci-validation-gates

Enforces semantic versioning and validates npm tokens in CI/CD pipelines.

Community
Advanced