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.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
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.
<cli_setup>
Locate and set the CLI variable:
The CLI script is at scripts/rhdhrelative to this SKILL.md file (not the working directory).
When you read this file, note its path and derive the script location:
If SKILL.md is at /path/to/skills/rhdh/SKILL.md
Then the CLI is at /path/to/skills/rhdh/scripts/rhdh
RHDH="/path/to/skills/rhdh/scripts/rhdh"# Use the actual path
Get oriented (run first):
$RHDH
This shows environment status, discovered repos, and available tools.
</cli_setup>
<essential_principles>
Use `$RHDH log` and `$RHDH todo` to maintain context across sessions.
Log milestones with tags. Create todos when blocked on external input.
This enables resuming work without re-explaining context and builds an audit trail.
See the `` section for details.
**Before using GitHub CLI**, read the reference file:
- **GitHub:** `references/github-reference.md` — PR queries, CI analysis, `/publish` triggers
Contains critical gotchas (jq escaping, assignee format) that prevent common errors.
**Before any RHDH-related work**, consult `references/rhdh-repos.md` for a reference of all RHDH-related repositories, what each one is used for, and how they relate to each other.
Use this when navigating between projects or understanding the overall RHDH ecosystem.
Use `$RHDH config set` to set the path to the local checkout of the RHDH repositories.
## Step 1: Run CLI
### Doctor Route (Priority)
</essential_principles>
<context_scan>
Run on invocation to understand current state:
$RHDH
This checks:
Overlay repo location and status
rhdh-local availability
gh CLI authentication
Container runtime (podman/docker)
If repos not found: Run $RHDH config init to auto-detect or configure paths.
</context_scan>
$RHDH
If needs_setup: true: Stop and run $RHDH doctor to fix setup issues.
Step 2: Identify Task Type
What would you like to do?
Overlay Repository Tasks
For working with the rhdh-plugin-export-overlays repository
Onboard a new plugin — Add upstream plugin to Extensions Catalog
Update plugin version — Bump to newer upstream commit/tag
Fix build failure — Debug CI/publish issues
Triage overlay PRs — Prioritize open PRs by criticality
Analyze specific PR — Check assignment, compatibility, merge readiness
Plugin Creation Tasks
For creating new RHDH dynamic plugins from scratch
Create plugin — Bootstrap, export, package, or wire a dynamic plugin (backend or frontend)
Local Testing Tasks
For testing plugins in a local RHDH instance using rhdh-local-setup
Local testing — Enable/disable/test plugins in local RHDH
Review & Testing Tasks
For testing PR changes on a live RHDH cluster
Review operator PR — Deploy PR operator bundle on cluster and get review checklist
Test Plan Tasks
For rhdh test plan review in jira
Review Test Plan content — Reviews an RHDH test plan Jira ticket and suggests platform/integration version updates based on support lifecycle pages and RHDH release milestones
To route: Read ../backstage-upgrade/SKILL.md and follow its intake process.
General Routes
Response
Action
11, "doctor", "setup", "config"
Use CLI commands below
12, "log", "todo", "activity"
Use tracking commands below
<cli_commands>
Environment status (no args):
$RHDH
Shows overlay repo, rhdh-local, tools status, and next steps.
Full environment check:
$RHDH doctor
Configuration:
$RHDH config init # Create config with auto-detection$RHDH config show # Show resolved paths$RHDH config set overlay /path # Set rhdh-plugin-export-overlays location$RHDH config setlocal /path # Set rhdh-local location$RHDH config set rhdh /path # Set main rhdh repo location$RHDH config set downstream /path # Set rhdh-downstream location$RHDH config set cli /path # Set rhdh-cli location$RHDH config set plugins /path # Set rhdh-plugins location$RHDH config set operator /path # Set rhdh-operator location$RHDH config set chart /path # Set rhdh-chart location$RHDH config set catalog /path # Set rhdh-plugin-catalog location
Workspace operations:
$RHDH workspace list # List all plugin workspaces$RHDH workspace status <name> # Show workspace details
</cli_commands>
<tracking_system>
Activity Tracking (Recommended)
The CLI includes worklog and todo tracking to maintain context across sessions. Use is recommended but not required.
Why Track?
Cross-session memory — Pick up where you left off without re-explaining context
Audit trail — "When did we onboard X?" / "What happened with PR #123?"
Follow-up reminders — Don't lose track of blocked items waiting on external input
Worklog Commands
Append-only activity log stored in .rhdh/worklog.jsonl:
# Log activity with tags for searchability$RHDHlog add "Started onboard: aws-appsync" --tag onboard --tag aws-appsync
$RHDHlog add "PR #1234 merged" --tag aws-appsync --tag pr# View recent entries$RHDHlog show --limit 10
# Search past activity$RHDHlog search "aws-appsync"$RHDHlog search "onboard"
Todo Commands
Section-based markdown todos stored in .rhdh/TODO.md:
# Create todo when blocked$RHDH todo add "Check license with legal" --context "aws-appsync"$RHDH todo add "Follow up on stale PR #1234" --context "triage"# List and manage$RHDH todo list # All todos$RHDH todo list --pending # Only open items# Update progress$RHDH todo note <slug> "Sent email to legal@redhat.com"$RHDH todo done <slug>
# View raw file$RHDH todo show
When to Track
Log these milestones:
Starting/completing a workflow (onboard, update, triage)
PR actions (opened, published, merged)
Significant decisions or findings
Create todos for:
Blocked items waiting on external response (legal, upstream, team)
Post-merge follow-ups (verify in staging, remove workarounds)
Items that span multiple sessions
Writing Effective Todos
Todos must be self-contained—a new session should understand the task without re-investigating.
❌ Too vague
✅ Actionable
Fix #1875 version mismatch
Fix #1875 (lightspeed): bump 1.3.0→1.4.0 in workspace.yaml like #1903