RHDH Skill

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 redhat-developer/rhdh-skill — works with 50+ coding agents.

Why This Exists

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.

What's Inside

Plugin Development

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, and wiring.
  • 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.yaml wiring config.

Extensions Catalog

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.

Local Testing

Test 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-setup customization system.

Jira

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 acli for 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.

Orchestration

• rhdh — Entry point and router. Detects your environment, runs doctor checks, maintains a cross-session worklog, and routes to the right skill. Start here if you're not sure what you need.

Meta

• skill-maker — Create new skills or consolidate existing ones following the Agent Skills open standard. Interviews you about scope and edge cases before drafting.

Getting Started

Install the skills, then just talk to your agent. Mention what you're working on — onboarding a plugin, triaging PRs, creating a new backend module, checking Jira issues — and the right skill activates automatically.

If your agent doesn't pick up the right skill, or you want to start from the top, the rhdh orchestrator skill runs environment checks and routes you:

Tell my agent: "I need to onboard a new plugin to the Extensions Catalog"

Not everything needs every tool. Each skill checks for its own prerequisites and tells you what's missing.

Installation

Skills CLI (any agent)

npx skills add redhat-developer/rhdh-skill

Supports 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-code

Claude Code Plugin Marketplace

claude plugin marketplace add redhat-developer/rhdh-skill
claude plugin install --scope project rhdh

Local Checkout (development)

npx skills add ./path/to/rhdh-skill

Note: Always install in project scope. The skills reference repository-specific paths.

Development

uv sync --extra dev                  # Install dev dependencies
git config core.hooksPath .githooks  # Enable pre-commit hooks (one-time)
uv run pytest                        # Run tests

The 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.

License

Apache-2.0 — see LICENSE.