redhat-developer

Finds orphaned .adoc and image files not referenced by any include or image directive. Use when cleaning up unused files or after restructuring content.

Validates directory naming conventions for titles, assemblies, and modules. Use when restructuring content or adding new directories.

Runs Vale DITA compliance checks using .vale-dita-only.ini. Use when validating AsciiDoc DITA standards compliance.

Validates assembly files follow the modular docs template structure. Use when creating or restructuring assemblies.

Validates modular docs metadata, prefix conventions, and list formatting in .adoc files. Use when creating or editing modules.

Validates modules follow Red Hat modular docs templates. Use when creating new modules or fixing template compliance.

Validates all mandatory modular doc elements are present per content type. Use when modules are missing required sections.

Validates assembly scope limits for nested assemblies and total includes. Use when assemblies grow too large.

Workflow to backport Backstage changes into RHDH by syncing a downstream maintenance branch and generating yarn patches.

Workflow to backport Backstage changes into RHDH by syncing a downstream maintenance branch and generating yarn patches.

Deploy RHDH to an OpenShift cluster using local-run.sh for E2E test execution, with autonomous error recovery for deployment failures

Analyze a failing E2E test, determine root cause, and fix it using Playwright Test Agents and RHDH project conventions

Parse a Prow CI job URL or Jira ticket to extract E2E test failure details including test name, spec file, release branch, platform, and error messages

Run a specific failing E2E test against a deployed RHDH instance to confirm the failure and determine if it is consistent or flaky

Create a PR for an E2E test fix, trigger Qodo agentic review, address review comments, and monitor CI results

Verify an E2E test fix by running the test multiple times and checking code quality

Bumps Konflux Tekton task digests with .tekton/updateDigests.sh --minor --no-push, applies konflux-ci/build-definitions MIGRATION.md pipeline fixes, and regenerates PipelineRuns. Use for rhdh-plugin-catalog, RHDH midstream (4-rhdh), Konflux task minor bumps, prefetch-dependencies-oci-ta, build-image-index, or updateDigests.sh.

Check version lifecycle and support status for platforms and integrations used by RHDH. Covers OCP, AKS, EKS, GKE, RHDH releases, RHBK, Quay, PostgreSQL, and any Red Hat product via the Product Life Cycles API. Use when asking about version support, EOL dates, GA dates, support phases, or planning version upgrades. Also use for "is X still supported", "what versions should we test", or "when does X reach EOL".

Manage Prow CI job configurations for RHDH in the openshift/release repository. List, generate, add, and remove OCP test entries and cluster pools. List K8s platform test entries (AKS, EKS, GKE). Analyze OCP version coverage gaps. Decommission end-of-life release branches. Use when working with RHDH CI config, Prow jobs, cluster pools, or openshift/release CI management.

Trigger RHDH nightly ProwJobs on demand via the OpenShift CI Gangway REST API. Supports both rhdh and rhdh-plugin-export-overlays repos. Use when the user wants to trigger, run, kick off, or start a nightly CI job, run an on-demand E2E nightly test, list available nightly jobs, or trigger an overlay nightly. Also use when the user mentions Gangway, "nightly job", "periodic-ci", RC verification, testing a custom image, running CI against a fork, or checking available image tags on quay.io.

Interacts with RHDH Jira projects (RHIDP, RHDHPLAN, RHDHBUGS, RHDHSUPP) using acli, GraphQL, and REST API. Covers the full Jira lifecycle: create issues, assign, refine, plan sprints, report, track releases, and update status. Trigger on Jira keys (RHIDP-1234), "create a feature/epic/story/task/bug", "who should take this", "refine this", "plan the sprint", "sprint report", "release status", "update jira", or any sprint ceremony prep.

Full lifecycle for RHDH dynamic plugins — scaffold, implement, export, package, and configure. Use when asked to "create RHDH plugin", "bootstrap dynamic plugin", "create backend plugin", "create frontend plugin", "export dynamic plugin", "package plugin as OCI", "generate frontend wiring", "create plugin container image", "configure mount points", "create dynamic route", "add entity card", "scaffold RHDH plugin", "publish plugin to registry", "create tgz archive", or mentions creating, exporting, packaging, or wiring a Backstage plugin for Red Hat Developer Hub. Also use when asked to "build a plugin from scratch", "dynamic plugin tutorial", "RHDH plugin from scratch", or "build Backstage plugin for RHDH". Covers backend plugins (APIs, scaffolder actions, processors), frontend plugins (pages, cards, themes), export/packaging (OCI, tgz, npm), and frontend wiring configuration (mount points, routes, entity tabs, themes).

Manages the rhdh-plugin-export-overlays repository — onboards plugins to the Extensions Catalog, updates plugin versions, fixes overlay build failures, triages and analyzes PRs, triggers publishes, and manages plugin workspaces. Use when working with overlays, importing plugins, debugging CI, checking PRs, bumping versions, or mentions "Extensions Catalog", "overlay build failed", "plugin registry", "overlay PR", "overlay doctor", "plugin import", "add plugin to catalog", "onboard plugin", or "plugin workspace".

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

Guide for development practices in the Abbenay project. Covers decision logging, version management, build architecture, and package structure. Use when making architectural choices, adding features, or modifying the build system.

Hard gate for code quality before pushing or creating a pull request. MUST be followed before every push, every PR, and every PR update. No exceptions.

Guide for handling pull request reviews, including automated (Copilot) and human reviewer feedback. Use when responding to PR comments, resolving review threads, or updating PRs after review.

Guide for writing and modifying GitHub Actions workflows in this repository. Use when creating CI/CD pipelines, adding workflow jobs, modifying build steps, or debugging CI failures. Enforces the project's lean CI philosophy.

This skill should be used when the user asks to "deploy a test instance", "create a test deployment", "deploy RHDH", "spin up a test instance", "deploy with helm", "deploy with operator", "set up a test environment", "create a PR deployment", "use /test deploy", "enable a plugin", "disable a plugin", "add a plugin", "configure a plugin", "list available plugins", "show plugins", "install plugin", "remove plugin", "configure dynamic plugins", "add dynamic plugin", or mentions deploying an RHDH instance or enabling, disabling, or configuring dynamic plugins.

Architecture Decision Record assistant for rhdh-adr repository