How do I install the Rhdh Release Status skill?

Run npx skillmds@latest add redhat-developer/rhdh-release-status in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rhdh Release Status safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rhdh Release Status?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rhdh Release Status free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rhdh Release Status?

redhat-developer (@redhat-developer) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rhdh Release Status by redhat-developer

Name: Rhdh Release Status
Author: redhat-developer

Rhdh Release Status

Reports what is still open against an RHDH release from Jira RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP: issue counts by type, blocker bugs, CVEs, Engineering EPICs, per-team breakdowns, release-note lifecycle, Post Code Freeze scope, and any query in the RHIDP Operational Rich Filter export. Also reports readiness at the Feature and Program Increment level: PI funnel, feature status matrix, stretch features, epic roll-up, cross-team dependency map, per-Feature coherence, and risk assessment. Use for "release status for 1.10", "what's blocking 1.10.3", "are we ready to ship 1.10", or "PI funnel for 2.1".

redhat-developer d153a01 14 files · 119.3 KB Updated Sep 17, 2026

File contents

RHDH release status

Answer "how is this release doing" with numbers that carry a Jira link and a timestamp. Read-only: this skill never edits Jira and never posts anything.

Route

Load workflows/release-status.md. It maps each question to the scripts/release.py subcommand that answers it, and carries the two scope rules the CLI output does not explain on its own.

For readiness at the Feature and Program Increment level rather than the issue level — "are we ready to ship", PI funnel, dependency map, per-Feature coherence — load references/feature-readiness.md instead. It runs quick mode for ceremony prep and deep mode for full coherence analysis. Both are read-only.

Rich Filter ownership

This skill owns the Rich Filter configuration prose. references/config.md holds the spreadsheet IDs, the discovery rule, and the RHDH_RICH_FILTER_PATH override; references/rich-filter-coverage.md records which release behaviours come from the export and which JQL stays local and why. Another skill that hits an unavailable Rich Filter template names /rhdh-release-status rather than restating the setup.

Boundary with the neighbouring skills

Milestone dates — Feature Freeze, Code Freeze, GA — are /rhdh-release-schedule.
A Slack freeze announcement is /rhdh-release-announce.
The team roster, leads, and Cloud IDs are /rhdh-release-teams. This skill counts issues per team; it does not publish the roster.
Reading a single issue, a board, or a sprint is /rhdh-jira-api. Any Jira write is /rhdh-jira-update.

Completion

Complete when every number in the answer names the subcommand or JQL that produced it, states when it was read, and carries the Jira search link behind it. A count the CLI reported as truncated is reported as a floor, not a total. A field Jira could not supply is listed as unverified — never carried over from an earlier release or inferred from a neighbouring count. When the Rich Filter was unavailable, say which scopes went unanswered instead of substituting a hand-written query.

---name: rhdh-release-statusdescription: Reports what is still open against an RHDH release from Jira RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP: issue counts by type, blocker bugs, CVEs, Engineering EPICs, per-team breakdowns, release-note lifecycle, Post Code Freeze scope, and any query in the RHIDP Operational Rich Filter export. Also reports readiness at the Feature and Program Increment level: PI funnel, feature status matrix, stretch features, epic roll-up, cross-team dependency map, per-Feature coherence, and risk assessment. Use for "release status for 1.10", "what's blocking 1.10.3", "are we ready to ship 1.10", or "PI funnel for 2.1".---# RHDH release statusAnswer "how is this release doing" with numbers that carry a Jira link and atimestamp. Read-only: this skill never edits Jira and never posts anything.## RouteLoad `workflows/release-status.md`. It maps each question to the`scripts/release.py` subcommand that answers it, and carries the two scope rulesthe CLI output does not explain on its own.For readiness at the Feature and Program Increment level rather than the issuelevel — "are we ready to ship", PI funnel, dependency map, per-Feature coherence— load `references/feature-readiness.md` instead. It runs quick mode for ceremonyprep and deep mode for full coherence analysis. Both are read-only.## Rich Filter ownershipThis skill owns the Rich Filter configuration prose. `references/config.md` holdsthe spreadsheet IDs, the discovery rule, and the `RHDH_RICH_FILTER_PATH`override; `references/rich-filter-coverage.md` records which release behaviourscome from the export and which JQL stays local and why. Another skill that hitsan unavailable Rich Filter template names `/rhdh-release-status` rather thanrestating the setup.## Boundary with the neighbouring skills- Milestone dates — Feature Freeze, Code Freeze, GA — are `/rhdh-release-schedule`.- A Slack freeze announcement is `/rhdh-release-announce`.- The team roster, leads, and Cloud IDs are `/rhdh-release-teams`. This skill counts issues per team; it does not publish the roster.- Reading a single issue, a board, or a sprint is `/rhdh-jira-api`. Any Jira write is `/rhdh-jira-update`.## CompletionComplete when every number in the answer names the subcommand or JQL thatproduced it, states when it was read, and carries the Jira search link behind it.A count theCLI reported as truncated is reported as a floor, not a total. A field Jira couldnot supply is listed as unverified — never carried over from an earlier releaseor inferred from a neighbouring count. When the Rich Filter was unavailable, saywhich scopes went unanswered instead of substituting a hand-written query.

Frequently asked questions