redhat-developer

Populate JTBD navigation map files with actual include directives from Jira tickets or category/job/topic names. Use when mapping content for a JTBD job, populating nav files, or connecting existing modules to the JTBD structure.

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.

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

Manages RHDH releases — dates, status tracking, team coordination, freeze announcements, blocker bugs, CVEs, and release notes. Trigger on "release dates", "release status", "feature freeze", "code freeze", "blocker bugs", "CVEs", "release notes", "team breakdown", or any RHDH release management question.

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.

Updates base images with updateBaseImages.sh and regenerates rpms.lock.yaml with rpm-lockfile-prototype in redhat-developer/rhdh, rhdh-must-gather, and rhdh-operator. Use --analyze for read-only Containerfile/Dockerfile scan (current vs latest tags, UBI skew). Use for weekly upstream maintenance, UBI/RHEL base image bumps, RPM lockfile refresh, base-images-and-rpms, main, release-*, or analyzing base images before updating.

Handles all RHDH-related work — "RHDH", "Red Hat Developer Hub", or "Developer Hub". Primary entry point for plugin development, overlay management, environment setup, repo navigation, version compatibility, CI/CD, configuration, debugging, and general RHDH ecosystem knowledge. Routes to specialized sub-skills as needed. Use when asked about RHDH version compatibility, RHDH CI pipeline, RHDH configuration, which RHDH repo to use, RHDH release status, RHDH debugging, or any Developer Hub question.

Migrate Backstage frontend plugins from the legacy system to the New Frontend System (NFS). Use when asked to "migrate to NFS", "new frontend system", "convert plugin to NFS", "createFrontendPlugin", "PageBlueprint", "ApiBlueprint", "SubPageBlueprint", "alpha to GA", "legacy to NFS", "frontend migration", "extension blueprints", "migrate frontend plugin", "NFS support", "graduate alpha", or mentions migrating a Backstage plugin to the new frontend system for RHDH.

Upgrade @backstage/* dependencies in a plugin or app to a target version. Use when asked to "upgrade backstage", "bump backstage", "update @backstage", "align backstage deps", "backstage version bump", "upgrade dependencies", "backstage-cli versions:bump", "update to latest backstage", "fix version mismatch", "backstage version alignment", "upgrade before migration", or any request to update Backstage package versions in a project.

Assesses a git repository's readiness for use by AI coding agents using the agentready CLI, then walks through and addresses each gap. RHDH-aware: detects RHDH repositories and uses rhdh-repos.md context to pre-fill AGENTS.md and skip inapplicable findings. Use when asked to "assess agent readiness", "run agentready", "check how agent-ready this repo is", "make this repo agent-ready", "improve agent readiness score", "assess all RHDH repos", "batch agent readiness", or "onboard this repo for agents".

Review pull requests: code-level analysis with inline comments, and live cluster testing for rhdh-operator PRs. Supports GitHub (GitLab planned). Use when asked to review a PR, review code, post review comments, test PR changes on a cluster, deploy PR images for testing, or do a full PR review. Also use when given a PR URL or number and asked for feedback, or when user mentions "review this PR", "PR review", "code review", or "test this PR on my cluster".

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.

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.

Navigate to the correct workspace in the rhdh-plugins monorepo, install dependencies, and scope all commands (test, build, lint) to the target workspace. Prevents workspace-wide operations that exceed sandbox timeouts.

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

Fullsend harness validation, drift checking, sandbox debugging, and fullsend setup. Use when asked to validate fullsend config, check for drift against upstream scaffold, diff or compare customized harness/env files against upstream, debug a sandbox run, inspect a fullsend agent run, or look at a specific run by ID or issue number. Also use when asked why a fullsend run failed, what changed in the harness, or how to set up env vars for the sandbox. Also use when asked to trigger a fullsend agent, post a slash command on an issue, watch or monitor a fullsend run, comment on an issue, or manage labels. Also use when asked to run sandbox diagnostics, debug the sandbox environment, check if yarn/corepack/openspec work, or build a custom fullsend agent. Also use when asked what fullsend agents are, how they work, how to use them, what agents are available, how to get started with fullsend, or how the local deployment is configured. Also use when asked to browse, view, or search fullsend runs in AgentsView, downloa