RHDH Local
Own local execution and return evidence to the calling workflow. All commands
use this skill's standalone CLI; another skill does not need to be installed.
Capability gate
- Run
uv run scripts/rhdh-local --help.
- Locate
rhdh-local-setup through RHDH_LOCAL_SETUP_DIR or by walking from
the current directory. Run uv run scripts/rhdh-local --json status.
- If the setup is absent, state the required environment variable or checkout
layout and stop only the runtime branch.
- Never read secrets from
.env into conversation context. Ask only for
missing variable names and let the container runtime consume their values.
Route by outcome
| Outcome |
Load and follow |
| Enable a catalog or PR artifact |
workflows/enable-plugin.md |
| Disable a plugin |
workflows/disable-plugin.md |
| Switch pristine/customized mode |
workflows/switch-mode.md |
| Verify a plugin end to end |
workflows/test-plugin.md and references/dynamic-plugin-testing.md |
| Inspect status or enabled packages |
Run uv run scripts/rhdh-local --json status or uv run scripts/rhdh-local --json plugins list |
| Apply customizations |
Run uv run scripts/rhdh-local --json apply |
| Start or stop |
Run uv run scripts/rhdh-local --json up [flags] or uv run scripts/rhdh-local --json down |
| Check health |
Run uv run scripts/rhdh-local --json health |
| Back up or restore |
Run uv run scripts/rhdh-local --json backup or uv run scripts/rhdh-local restore <archive>; restore is a dry run until --force |
| Troubleshoot startup, networking, or 504s |
references/troubleshooting.md |
| Configure environment variables |
references/env-reference.md |
Invariants
- Edit only source files under
rhdh-customizations/. Run apply after every
edit so copies under rhdh-local/ stay synchronized.
- Use this CLI's
up and down commands when Lightspeed or Orchestrator is
enabled; they own the compose lifecycle and shared networks.
- Obtain package references from
spec.dynamicArtifact or from the reference the
caller supplied. Never construct OCI references from naming conventions.
- Preserve the
includes: block in dynamic plugin overrides. Put backend
packages before their frontend packages.
- A plugin test succeeds only with recorded installation, boot, health, and UI
results relevant to the request. Distinguish an expected credential error
from a load failure.
What a caller supplies
A caller invokes this skill by name and states, in conversation:
- each package reference to enable, with its plugin config or
none
- the environment variables the plugin needs, by name only
- the catalog test entities the plugin renders against
- which checks to run: installation, startup, health, UI
- whether to clean up afterwards
Use those references verbatim. Ask for a missing one rather than reconstructing
it from a naming convention.
What this skill reports
Report to the caller in conversation. Do not write into another skill's
directory.
- the subject tested, and the mode it ran in: customized or pristine
- one line per requested check — installation, startup, health, UI — each passed,
failed, or skipped with the reason it was skipped
- the packages actually enabled, with their exact references
- the log excerpts that back each result
- cleanup state: completed, retained, or not requested
Completion
Complete when the report names every source customization file changed, every
CLI command run, the health and UI evidence observed, the cleanup state, and one
outcome for every check the caller requested.
1---2name: rhdh-local3description: Operates a local Red Hat Developer Hub environment with the rhdh-local-setup customization system: enable or disable dynamic plugins, apply configuration, switch pristine and customized modes, start or stop containers, inspect health and logs, run plugin verification, and back up or restore customizations. Use for local RHDH, podman compose plugin testing, PR artifact verification, 504 or startup troubleshooting, and local Extensions Catalog checks.4---56# RHDH Local78Own local execution and return evidence to the calling workflow. All commands9use this skill's standalone CLI; another skill does not need to be installed.1011## Capability gate12131. Run `uv run scripts/rhdh-local --help`.142. Locate `rhdh-local-setup` through `RHDH_LOCAL_SETUP_DIR` or by walking from15 the current directory. Run `uv run scripts/rhdh-local --json status`.163. If the setup is absent, state the required environment variable or checkout17 layout and stop only the runtime branch.184. Never read secrets from `.env` into conversation context. Ask only for19 missing variable names and let the container runtime consume their values.2021## Route by outcome2223| Outcome | Load and follow |24|---|---|25| Enable a catalog or PR artifact | `workflows/enable-plugin.md` |26| Disable a plugin | `workflows/disable-plugin.md` |27| Switch pristine/customized mode | `workflows/switch-mode.md` |28| Verify a plugin end to end | `workflows/test-plugin.md` and `references/dynamic-plugin-testing.md` |29| Inspect status or enabled packages | Run `uv run scripts/rhdh-local --json status` or `uv run scripts/rhdh-local --json plugins list` |30| Apply customizations | Run `uv run scripts/rhdh-local --json apply` |31| Start or stop | Run `uv run scripts/rhdh-local --json up [flags]` or `uv run scripts/rhdh-local --json down` |32| Check health | Run `uv run scripts/rhdh-local --json health` |33| Back up or restore | Run `uv run scripts/rhdh-local --json backup` or `uv run scripts/rhdh-local restore <archive>`; restore is a dry run until `--force` |34| Troubleshoot startup, networking, or 504s | `references/troubleshooting.md` |35| Configure environment variables | `references/env-reference.md` |3637## Invariants3839- Edit only source files under `rhdh-customizations/`. Run `apply` after every40 edit so copies under `rhdh-local/` stay synchronized.41- Use this CLI's `up` and `down` commands when Lightspeed or Orchestrator is42 enabled; they own the compose lifecycle and shared networks.43- Obtain package references from `spec.dynamicArtifact` or from the reference the44 caller supplied. Never construct OCI references from naming conventions.45- Preserve the `includes:` block in dynamic plugin overrides. Put backend46 packages before their frontend packages.47- A plugin test succeeds only with recorded installation, boot, health, and UI48 results relevant to the request. Distinguish an expected credential error49 from a load failure.5051## What a caller supplies5253A caller invokes this skill by name and states, in conversation:5455- each package reference to enable, with its plugin config or `none`56- the environment variables the plugin needs, by name only57- the catalog test entities the plugin renders against58- which checks to run: installation, startup, health, UI59- whether to clean up afterwards6061Use those references verbatim. Ask for a missing one rather than reconstructing62it from a naming convention.6364## What this skill reports6566Report to the caller in conversation. Do not write into another skill's67directory.6869- the subject tested, and the mode it ran in: customized or pristine70- one line per requested check — installation, startup, health, UI — each passed,71 failed, or skipped with the reason it was skipped72- the packages actually enabled, with their exact references73- the log excerpts that back each result74- cleanup state: completed, retained, or not requested7576## Completion7778Complete when the report names every source customization file changed, every79CLI command run, the health and UI evidence observed, the cleanup state, and one80outcome for every check the caller requested.
redhat-developer