Agent skills for the Red Hat Developer Hub team. Covers plugin development, overlay management, local testing, Jira workflows, and day-to-day RHDH engineering — so your agent knows the ecosystem instead of hallucinating through it.
Quick start:
npx skills add -g redhat-developer/rhdh-skill— works with 50+ coding agents.
RHDH spans a dozen repositories, four Jira projects, version-specific Backstage compatibility, overlay CI pipelines, and a copy-sync customization system for local testing. Without guidance, agents hallucinate version numbers, use the legacy backend system, construct OCI URLs by hand, and miss project-specific conventions that are impossible to learn from training data alone.
These skills encode the gotchas, workflows, and tribal knowledge so you don't re-explain them every session.
The rhdh skill is the primary entry point. It detects your environment (tools, repos, auth), runs doctor checks, and routes to the right sub-skill based on what you're doing — overlay management, plugin creation, local testing, Jira, CI, and so on. You don't need to remember which skill to invoke; just describe your task and rhdh figures it out.
Under the hood, rhdh maintains a config file (~/.config/rhdh-skill/config.json) that maps short keys to your local git checkouts. Once configured, any skill can locate the right repo without you specifying paths each time:
| Key | Repository | Key | Repository |
|---|---|---|---|
rhdh |
rhdh | overlay |
rhdh-plugin-export-overlays |
downstream |
rhdh (midstream) | export-utils |
rhdh-plugin-export-utils |
cli |
rhdh-cli | catalog |
rhdh-plugin-catalog |
plugins |
rhdh-plugins | operator |
rhdh-operator |
chart |
rhdh-chart | local |
rhdh-local |
factory |
rhdh-dynamic-plugin-factory | backstage |
backstage |
Run rhdh doctor at any time to check your environment — missing tools, unconfigured repos, and auth issues are flagged with fix instructions.
Build dynamic plugins from scratch — backend or frontend — and get them deployed.
- create-plugin — Full plugin lifecycle: scaffold, implement, export, package, and wire RHDH dynamic plugins. Sub-commands for
backend,frontend,export, andwiring.- backend — Backend plugins (APIs, scaffolder actions, catalog processors) using the new backend system.
- frontend — Frontend plugins (pages, entity cards, themes) with Scalprum federation.
- export — Export, package (OCI/tgz/npm), and push to a container registry.
- wiring — Analyze plugin source and generate
dynamic-plugins.yamlwiring config.
Migrate your plugins from the legacy Backstage frontend system to the New Frontend System (NFS).
- nfs-migration -- Analyzes your existing plugin, applies the right Blueprint patterns, updates exports, and verifies the result. Two approaches: alpha (default, NFS at
./alpha) or colocated (NFS + legacy both from root). Reference files cover every extension type, mount point mapping, operator config, gotchas, and verification.
Upgrade @backstage/* dependencies in your plugin to align with a target RHDH or Backstage release.
- backstage-upgrade -- Discovers current versions, determines the target using the RHDH→Backstage version matrix, runs
backstage-cli versions:bump, migrates moved packages, guides through breaking changes from upstream changelogs, and verifies the result. Composable — the NFS migration skill chains into it automatically when deps are outdated.
Manage plugins in the rhdh-plugin-export-overlays repository.
- overlay — Onboard new plugins, update versions, fix CI failures, triage and analyze PRs, trigger
/publish. Covers both plugin-owner and core-team workflows.
Update Konflux task digests and apply MIGRATION.md pipeline changes in rhdh-plugin-catalog or rhdh midstream.
- konflux-tekton-updates — Run
.tekton/updateDigests.sh --minor --no-push, apply build-definitions task migrations, update shared pipelines/templates and PLR generators. Repo-specific file lists: plugin-catalog, RHDH midstream.
npx skills add redhat-developer/rhdh-skill --skill konflux-tekton-updatesCheck version support status for platforms and integrations used by RHDH.
- lifecycle — Check version lifecycle and support status for OCP, AKS, EKS, GKE, RHDH releases, RHBK, Quay, PostgreSQL, and any Red Hat product via the Product Life Cycles API.
Manage Prow CI job configurations and trigger nightly E2E tests.
- prow — Manage Prow CI job configurations for RHDH in the openshift/release repository. List, generate, add, and remove OCP test entries and cluster pools. List K8s platform test entries (AKS, EKS, GKE). Analyze coverage gaps. Commission new release branches and decommission end-of-life ones.
- prow-trigger-nightly — Trigger RHDH nightly ProwJobs on demand via the OpenShift CI Gangway REST API. Supports both rhdh and rhdh-plugin-export-overlays repos with Gangway overrides for catalog index image, chart version, and Playwright version.
Bump UBI / RHEC base image tags, refresh RPM lockfiles, and align node headers / go.mod in rhdh, rhdh-operator, and rhdh-must-gather (see rhdh-repos).
- base-images-and-rpms — Weekly upstream maintenance:
updateBaseImages.sh,rpm-lockfile-prototype, node headers, and go.mod (main only). Use--analyzefor read-only Containerfile/Dockerfile scan before updating. Requiresskopeo login registry.redhat.io.
npx skills add redhat-developer/rhdh-skill --skill base-images-and-rpmsTest plugins in a local RHDH instance before deploying.
- rhdh-local — Enable/disable plugins, switch between customized and pristine configs, run health checks, backup/restore configurations via the
rhdh-local-setupcustomization system.
Track work across the four RHDH Jira projects.
- rhdh-jira — Search, create, view, edit, transition, link, assign, and refine issues across RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP. Uses
aclifor simple operations, GraphQL for bulk reads, and REST API as fallback. Sub-commands:- assign — Recommend assignees using team expertise profiling, sprint capacity analysis, and context proximity scoring. Supports deep mode (5-layer analysis via GraphQL) and quick mode (match from existing context). Assigns after user confirmation.
- refine — Check issues against RHDH workflow exit criteria, detect duplicates, verify parent/child hierarchy, flag unaddressed comments, identify stale issues, and validate sprint readiness.
- plan — Sprint planning prep: carryover report, velocity trend, per-member capacity, ready-for-planning queue, and sprint fill suggestions with expertise matching.
- sprint-report — Sprint review summary: committed vs completed, per-member breakdown, epic progress, demo checklist with naming conventions, and velocity trend.
- release — Release readiness: feature matrix, Program Increment funnel, epic roll-up, cross-team dependency map, blocker bugs, release notes readiness, and risk assessment.
- to-feature — Create a RHDHPLAN Feature from conversation context. Grills on scope, customer value, and acceptance criteria. Optionally chains into Epic decomposition.
- to-epic — Create an RHIDP Epic. Grills on delivery scope, dependencies, and acceptance criteria. Optionally chains into Story/Task decomposition.
- to-issue — Create a Story, Task, Bug, or Spike with automatic type inference. Grills on implementation details and story points.
- update-jira-status — Update an issue with session progress. Detects the related issue, adds a status comment, proposes transitions, and checks upward cascade to parent Epic/Feature.
- rhdh-pr-review — PR code review with inline comments (GitHub, GitLab planned) and live cluster testing for rhdh-operator PRs. Layered architecture: fetch → analyze → post.
- rhdh-test-plan-review — Reviews an RHDH test plan Jira ticket and suggests platform/integration version updates based on support lifecycle pages and RHDH release milestones
- agent-ready — Assess RHDH repositories against agentready criteria and address each gap. RHDH-aware: detects the repo from its remote URL, uses
rhdh-repos.mdcontext to pre-fillAGENTS.mdand skip inapplicable findings. Supports single-repo and batch modes (assess all RHDH repos in one pass).
- skill-maker — Create new skills or consolidate existing ones following the Agent Skills open standard. Interviews you about scope and edge cases before drafting.
-
Install globally (recommended —
rhdhmanages paths across multiple repos):npx skills add -g redhat-developer/rhdh-skill
-
Talk to your agent. Mention what you're working on and
rhdhtakes care of the rest — including first-time setup:You: "I need to onboard the aws-appsync plugin to the Extensions Catalog" Agent: runs rhdh doctor, detects missing config Agent: runs rhdh config init, finds your local repos Agent: routes to the overlay skill, starts the onboard workflowOn the first run,
rhdhauto-detects your local checkouts and creates~/.config/rhdh-skill/config.json. If a repo isn't found automatically, the agent will ask you for its path.
npx skills add -g redhat-developer/rhdh-skillGlobal install is the right default — rhdh manages paths across multiple repos via its config, so it doesn't need to live inside any single project.
For single-repo use (e.g., only the create-plugin skill inside one plugin repo):
npx skills add redhat-developer/rhdh-skillSupports Claude Code, Cursor, Codex, Pi, and 50+ more.
# List available skills without installing
npx skills add redhat-developer/rhdh-skill --list
# Install a specific skill only
npx skills add redhat-developer/rhdh-skill --skill create-plugin
# Target a specific agent
npx skills add redhat-developer/rhdh-skill -a claude-codenpx skills update rhdh-skillnpx skills add ./path/to/rhdh-skilluv sync --extra dev # Install dev dependencies
git config core.hooksPath .githooks # Enable pre-commit hooks (one-time)
uv run pytest # Run testsThe core.hooksPath setting points git at the checked-in .githooks/ directory. If pre-commit is installed, linting and tests run automatically on every commit. If not, commits proceed with a warning.
See AGENTS.md for contribution guidelines and architectural decisions.
Apache-2.0 — see LICENSE.