rhdh

$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

1. Onboard a new plugin — Add upstream plugin to Extensions Catalog
2. Update plugin version — Bump to newer upstream commit/tag
3. Fix build failure — Debug CI/publish issues
4. Triage overlay PRs — Prioritize open PRs by criticality
5. Analyze specific PR — Check assignment, compatibility, merge readiness

Plugin Creation Tasks

For creating new RHDH dynamic plugins from scratch

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

7. Local testing — Enable/disable/test plugins in local RHDH

Review & Testing Tasks

For testing PR changes on a live RHDH cluster

8. Review operator PR — Deploy PR operator bundle on cluster and get review checklist

Test Plan Tasks

For rhdh test plan review in jira

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

Testing Strategy Tasks

For deciding where a test belongs in the RHDH ecosystem

10. Test placement — Propose the right repo, test layer, location, and scaffolding for a change

Release Management Tasks

For RHDH release tracking, status, announcements

11. Release management — Release dates, status, team breakdown, freeze announcements, blocker bugs, CVEs, release notes

General Tasks

12. Check environment — Run doctor, configure paths
13. View/search activity — Review worklog, todos

Wait for response before proceeding.

<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 set local /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
$RHDH config set private-data /path  # Set rhdh-skill-private-data 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
$RHDH log add "Started onboard: aws-appsync" --tag onboard --tag aws-appsync
$RHDH log add "PR #1234 merged" --tag aws-appsync --tag pr

# View recent entries
$RHDH log show --limit 10

# Search past activity
$RHDH log search "aws-appsync"
$RHDH log 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.

Include: PR number, plugin name, specific action, and why it's needed.

</tracking_system>

<reference_index> RHDH Repos: references/rhdh-repos.md — repository map, ecosystem relationships, key paths GitHub CLI (PRs, CI, workflows): references/github-reference.md Version Matrix: references/versions.md — RHDH/Backstage version compatibility, create-app versions Slack Notifications: references/slack-notification.md — Slack ping templates, handle mapping, channel routing Private Data: references/private-data.md — private data repo setup and sync (Rich Filter exports) </reference_index>

<skills_index>

Specialized Skills

Shared References

</skills_index>