rhdh-local
Test RHDH plugins locally using the rhdh-local-setup customization system. Covers enabling/disabling plugins, switching modes, running end-to-end plugin tests, starting/stopping RHDH (up/down), health checks, troubleshooting errors (504, startup failures), and backup/restore of configurations. Use when asked to "test plugin locally", "local RHDH setup", "start local Developer Hub", "rhdh-local-setup", "local development environment", "podman compose RHDH", or "run RHDH on my machine".
What this skill does
<essential_principles> <principle name="copy_sync_first"> All configuration edits go in `rhdh-customizations/`, never in `rhdh-local/` directly. After every edit, run `rhdh local apply` to sync copies. This is the fundamental invariant. </principle> <principle name="use_scripts"> Use `rhdh local up` / `rhdh local down` — never `podman compose restart/up/down` directly when Lightspeed or Orchestrator are enabled. These commands manage the local compose lifecycle directly through Python; do not bypass them with direct compose commands when shared-network services are enabled. See `references/troubleshooting.md` for network namespace details. </principle> <principle name="data_sources"> Plugin package definitions come from `rhdh-plugin-export-overlays` on GitHub. Always fetch the OCI reference from `spec.dynamicArtifact` in the package metadata — do NOT construct OCI URLs manually. </principle> </essential_principles> <intake> ## Step 1: Identify What You Want to Do What would you like to do with your local RHDH instance? 1. **Enable a plugin** — Add a plugin from the export-overlays catalog to your local RHDH 2. **Disable a plugin** — Disable or remove a plugin from your local RHDH 3. **Switch mode** — Switch between Customized (your config) and Pristine (RHDH defaults) 4. **Test a plugin** — Run end-to-end verification after enabling a plugin 5. **Check status** — See which plugins are currently enabled **Wait for response before proceeding.** </intake> <routing> | Response | Workflow | |----------|----------| | 1, "enable", "add plugin", "install plugin" | `workflows/enable-plugin.md` | | 2, "disable", "remove plugin", "turn off plugin" | `workflows/disable-plugin.md` | | 3, "switch", "pristine", "customized", "mode" | `workflows/switch-mode.md` | | 4, "test", "verify", "check plugin" | `workflows/test-plugin.md` | | 5, "status", "list plugins", "show plugins" | Read `rhdh-customizations/configs/dynamic-plugins/dynamic-plugins.override.yaml` and list entries | | "start", "up", "start rhdh" | Run `rhdh local up` (add `--lightspeed`, `--orchestrator`, or `--both` as needed) | | "stop", "down", "stop rhdh" | Run `rhdh local down` | | "health", "check health", "is rhdh running" | Run `rhdh local health` | | "backup", "save config", "archive" | Run `rhdh local backup` | | "restore", "restore backup" | Run `rhdh local restore <archive>` (dry-run by default) | | "env", "environment variables", "env vars", ".env" | Read `references/env-reference.md` | | "troubleshoot", "debug", "504", "error", "not working" | Read `references/troubleshooting.md` | </routing> <reference_index> **Customization system (copy-sync, file mapping, edit rules):** `references/customization-system.md` **Environment variables (.env reference):** `references/env-reference.md` **Troubleshooting & comparative testing:** `references/troubleshooting.md` **Container lifecycle, startup scripts, network namespace:** `references/troubleshooting.md` — restart patterns, 504 debugging, network namespace rules **Dynamic plugin YAML format, OCI references:** `../overlay/references/rhdh-local.md` section `<dynamic_plugins_config>` (if unavailable, see `rhdh-plugin-export-overlays` repo README for YAML format) </reference_index> <skills_index> | Skill | Purpose | Path | |-------|---------|------| | overlay | Onboard/update plugins in rhdh-plugin-export-overlays | `../overlay/SKILL.md` | | rhdh | Orchestrator — routes to all skills, runs CLI checks | `../rhdh/SKILL.md` | </skills_index>
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.