rhdh

<cli_setup> Locate and set the CLI variable:

The CLI script is at scripts/rhdh relative 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>

These contain critical gotchas (jq escaping, JQL limitations, assignee format) that prevent common errors. </principle>

</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

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

1. •Create backend plugin — Bootstrap a new backend dynamic plugin
2. •Create frontend plugin — Bootstrap a new frontend dynamic plugin
3. •Export and package plugin — Export plugin and package as OCI/tgz/npm
4. •Configure frontend wiring — Set up mount points, routes, entity tabs

General Tasks

1. •Check environment — Run doctor, configure paths
2. •View/search activity — Review worklog, todos

Wait for response before proceeding. </intake>

Always check this first.

Overlay Repository Routes

To route: Read ../overlay/SKILL.md and follow its intake process.

Plugin Creation Routes

To route: Read the corresponding skill file in ../ and follow its workflow.

General Routes

<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 repo location
$RHDH config set local /path   # Set rhdh-local 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> GitHub CLI (PRs, CI, workflows): references/github-reference.md JIRA CLI (issues, JQL, comments): references/jira-reference.md </reference_index>

<skills_index>

Specialized Skills

Shared References

</skills_index>