mcpField
R
rhdh-release-status

rhdh-release-status

github.com/redhat-developerProductivity1948 installsUpdated 1d ago
Repository

About rhdh-release-status

rhdh-release-status is a read-only skill for reporting release progress from Jira, with counts linked to their searches and read timestamps. It routes issue-level questions to CLI workflows and directs feature or PI readiness analysis to a separate reference.

Key features

  1. 01Report release status from Jira issues
  2. 02Link counts to Jira searches and timestamps
  3. 03Route questions to release CLI subcommands
  4. 04Direct feature and PI readiness analysis
  5. 05Distinguish status reporting from adjacent tasks

Use cases

  1. 01Check issue counts for a release
  2. 02Prepare release status updates with traceable figures
  3. 03Identify unanswered scopes when Rich Filter is unavailable

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/redhat-developer/rhdh-skills --skill rhdh-release-status

After installing, type/rhdh-release-statusin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/
openai.yaml
references/
config.md
feature-readiness.md
rich-filter-coverage.md
scripts/
_jira.py
_support.py
jql-release.md
jql.py
release.py
rich_filter.py
slack_templates.py
slack-templates.md
workflows/
release-status.md

Details

From the project README

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.
  • Whether a named team can fit the rhdh-X.Y-candidate Features through Code Freeze is /rhdh-release-capacity-plan. This skill reports status, not fit.
  • A Slack freeze announcement is /rhdh-release-announce.
  • The SoS check-in report for team leads is /rhdh-release-sos.
  • 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.
  • Creating, aligning, or deleting project fix versions across RHIDP, RHDHPLAN, and RHDHBUGS is /rhdh-release-fixversions. This skill only queries issues by fix version.

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.

Comments

Markdown supported