Run any Skill in Manus with one click

rhdh-release

Stars15

Forks28

UpdatedJuly 10, 2026 at 14:25

Manages RHDH releases — dates, status tracking, team coordination, freeze announcements, blocker bugs, CVEs, and release notes. Trigger on "release dates", "release status", "feature freeze", "code freeze", "blocker bugs", "CVEs", "release notes", "team breakdown", or any RHDH release management question.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

redhat-developer

redhat-developer/rhdh-skill

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

25 files

SKILL.md

readonly

name	rhdh-release
description	Manages RHDH releases — dates, status tracking, team coordination, freeze announcements, blocker bugs, CVEs, and release notes. Trigger on "release dates", "release status", "feature freeze", "code freeze", "blocker bugs", "CVEs", "release notes", "team breakdown", or any RHDH release management question.
compatibility	acli on PATH. Python 3 + gog CLI for Google Sheets/Docs.

<essential_principles>

Use `"Team[Team]" = "{{CLOUD_ID}}"` in JQL to filter by team. Cloud IDs are in the RHDH Team Mapping spreadsheet (column "Cloud ID"). Use the `open_issues_by_team`, `feature_freeze_issues_by_team`, or `code_freeze_issues_by_team` JQL templates. This is fast and does not require `parse_issues.py --enrich`. Include Jira search links for traceability in all outputs. Build links by URL-encoding the JQL: `https://issues.redhat.com/issues/?jql=`. Always wrap Slack messages in triple-backtick code blocks (` ```slack `) for easy copy-paste. Tell the user they can copy-paste this directly into Slack. When analyzing release health, check these risk indicators: 1. Blocker bugs near freeze dates — query with `priority = Blocker` 2. High open issue count per team — use team breakdown to identify overloaded teams 3. Missing release notes — query issues with empty Release Note Type 4. Critical CVEs — query vulnerabilities with CVE in summary 5. EPICs not in Dev Complete — check epic status

Always provide: specific issue counts with Jira links, team-level breakdown if applicable, actionable recommendations (retriage, escalate, extend timeline), and impact assessment.

For team coordination: 1. Retrieve team info from Google Sheets to get leads and Slack handles 2. Include team leads' Slack handles in all team communications 3. Provide Jira links scoped to each team's issues 4. Highlight teams at risk (high open counts, blockers) 5. Suggest follow-up actions per team Never read `.jira-token` into context. Always use shell substitution: `"$(cat "$TOKEN_FILE")"`.

</essential_principles>

RHDH Release Management

What would you like to do?

Release Information

Release dates — Current release dates and key milestones
Future release dates — Upcoming release dates from schedule spreadsheet
Release status — Active release status by issue type
Teams — Teams and leads directory

Release Tracking

Team breakdown — Issues by engineering team for a release
Blocker bugs — Open blocker bugs for a release
EPICs — Engineering EPICs not yet complete
CVEs — CVE/vulnerability list for a release
Release notes — Outstanding release notes (missing Release Note Type)

Announcements

Feature Freeze update — Generate Feature Freeze status update for Slack
Feature Freeze announcement — Generate Feature Freeze milestone announcement
Code Freeze update — Generate Code Freeze status update for Slack
Code Freeze announcement — Generate Code Freeze milestone announcement

Wait for response before proceeding.

Preferred: Run the release CLI first (python scripts/release.py --json <command>). If the CLI fails, fall back to the workflow's manual steps.

Response	CLI Command	Workflow (fallback)
1, "release dates", "key dates", "freeze dates", "milestone dates"	`python scripts/release.py --json dates`	`workflows/release-dates.md`
2, "future releases", "upcoming releases", "release roadmap", "future dates"	`python scripts/release.py --json future-dates VERSION`	`workflows/future-release-dates.md`
3, "release status", "active releases", "release health", "release overview"	`python scripts/release.py --json status VERSION`	`workflows/release-status.md`
4, "teams", "team leads", "team list", "team contacts", "team directory"	`python scripts/release.py --json teams`	`workflows/teams-and-leads.md`
5, "team breakdown", "issues by team", "team workload", "team counts"	`python scripts/release.py --json team-breakdown VERSION`	`workflows/issues-by-team.md`
6, "blocker bugs", "blockers", "critical issues", "blocking issues"	`python scripts/release.py --json blockers VERSION`	`workflows/blocker-bugs.md`
7, "epics", "engineering epics", "open epics", "active epics"	`python scripts/release.py --json epics VERSION`	`workflows/engineering-epics.md`
8, "cves", "vulnerabilities", "security issues", "security bugs"	`python scripts/release.py --json cves VERSION`	`workflows/cves.md`
9, "release notes", "missing release notes", "release note gaps"	`python scripts/release.py --json notes VERSION`	`workflows/release-notes.md`
10, "feature freeze update", "feature freeze status", "feature freeze progress"	`python scripts/release.py --json slack feature-freeze-update VERSION`	`workflows/announce-feature-freeze-update.md`
11, "feature freeze announcement", "announce feature freeze", "feature freeze reached"	`python scripts/release.py --json slack feature-freeze VERSION`	`workflows/announce-feature-freeze.md`
12, "code freeze update", "code freeze status", "code freeze progress"	`python scripts/release.py --json slack code-freeze-update VERSION`	`workflows/announce-code-freeze-update.md`
13, "code freeze announcement", "announce code freeze", "code freeze reached"	`python scripts/release.py --json slack code-freeze VERSION`	`workflows/announce-code-freeze.md`

<reference_index>

Reference	Purpose	Load when
`references/jql-release.md`	13 release-specific JQL templates	Any Jira query for release data
`references/slack-templates.md`	4 Slack announcement templates	Generating freeze announcements
`references/config.md`	GDrive IDs, project keys, dashboards, gog setup	Looking up config values or links
`gog docs cat 13OkypJ3u_7Jq6kEhKhjEFwHQ12oPFDKXVzFjYW4XLdk`	Release process (live Google Doc)	Release process questions, onboarding
`../../rhdh-jira/references/auth.md`	Jira auth setup	Jira prerequisite fails
`../../rhdh-jira/references/acli-commands.md`	acli command reference	Building acli commands

</reference_index>

Run before any workflow:

Requirement	Check	Fix
Jira CLI	`acli jira workitem search --jql "project=RHIDP" --count` succeeds	Load `../../rhdh-jira/SKILL.md` Prerequisites
gog CLI (for Google Sheets/Docs)	`gog sheets metadata 1vQXfvID72qwqvLb17eyGOvnZXrZG7NBzTGv6RP9wvyM --json` succeeds	Install gog and run `gog auth add <email>`

More from this repository

same repository

rhdh-jira

redhat-developer/rhdh-skill

Interacts with RHDH Jira projects (RHIDP, RHDHPLAN, RHDHBUGS, RHDHSUPP) using acli, GraphQL, and REST API. Covers the full Jira lifecycle: create issues, assign, refine, plan sprints, report, track releases, and update status. Trigger on Jira keys (RHIDP-1234), "create a feature/epic/story/task/bug", "who should take this", "refine this", "plan the sprint", "sprint report", "release status", "update jira", or any sprint ceremony prep.

2026-07-1015

base-images-and-rpms

redhat-developer/rhdh-skill

Updates base images with updateBaseImages.sh and regenerates rpms.lock.yaml with rpm-lockfile-prototype in redhat-developer/rhdh, rhdh-must-gather, and rhdh-operator. Use --analyze for read-only Containerfile/Dockerfile scan (current vs latest tags, UBI skew). Use for weekly upstream maintenance, UBI/RHEL base image bumps, RPM lockfile refresh, base-images-and-rpms, main, release-*, or analyzing base images before updating.

2026-07-0715

rhdh

redhat-developer/rhdh-skill

Handles all RHDH-related work — "RHDH", "Red Hat Developer Hub", or "Developer Hub". Primary entry point for plugin development, overlay management, environment setup, repo navigation, version compatibility, CI/CD, configuration, debugging, and general RHDH ecosystem knowledge. Routes to specialized sub-skills as needed. Use when asked about RHDH version compatibility, RHDH CI pipeline, RHDH configuration, which RHDH repo to use, RHDH release status, RHDH debugging, or any Developer Hub question.

2026-07-0715

nfs-migration

redhat-developer/rhdh-skill

Migrate Backstage frontend plugins from the legacy system to the New Frontend System (NFS). Use when asked to "migrate to NFS", "new frontend system", "convert plugin to NFS", "createFrontendPlugin", "PageBlueprint", "ApiBlueprint", "SubPageBlueprint", "alpha to GA", "legacy to NFS", "frontend migration", "extension blueprints", "migrate frontend plugin", "NFS support", "graduate alpha", or mentions migrating a Backstage plugin to the new frontend system for RHDH.

2026-06-3015

backstage-upgrade

redhat-developer/rhdh-skill

Upgrade @backstage/* dependencies in a plugin or app to a target version. Use when asked to "upgrade backstage", "bump backstage", "update @backstage", "align backstage deps", "backstage version bump", "upgrade dependencies", "backstage-cli versions:bump", "update to latest backstage", "fix version mismatch", "backstage version alignment", "upgrade before migration", or any request to update Backstage package versions in a project.

2026-06-2615

agent-ready

redhat-developer/rhdh-skill

Assesses a git repository's readiness for use by AI coding agents using the agentready CLI, then walks through and addresses each gap. RHDH-aware: detects RHDH repositories and uses rhdh-repos.md context to pre-fill AGENTS.md and skip inapplicable findings. Use when asked to "assess agent readiness", "run agentready", "check how agent-ready this repo is", "make this repo agent-ready", "improve agent readiness score", "assess all RHDH repos", "batch agent readiness", or "onboard this repo for agents".

2026-06-1815