ask-rhdh
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseAsk RHDH
咨询RHDH
Turn an RHDH question into one precise model-skill invocation. This is a human entry point,
not a second discovery system: route by outcome and hand the request over intact.
将RHDH相关问题转化为精准的模型技能调用。这是人工入口，而非二次发现系统：根据结果进行路由，并完整传递请求。
Route the request
请求路由
Each row below is a model skill's own description, projected from the catalog by
. Do not hand-edit the table: run
after a skill is added, removed, or
redescribed, and to detect drift. Paraphrasing a skill here creates a
competing inventory, which is what this table used to be.
<!-- BEGIN GENERATED ROUTES: python scripts/render_routes.py --write -->
scripts/render_routes.pypython scripts/render_routes.py --write--check| When the request is | Model skill |
|---|---|
| Opens new work in RHDH Jira and decides what kind of work it is — Feature or Feature Request in RHDHPLAN, Epic, Story, Task, Spike or Vulnerability in RHIDP, Bug in RHDHBUGS, support conversation in RHDHSUPP — then interviews, drafts, and creates it with the right fields and parent link. Use for "file a ticket", "create a feature", "open an epic for this", "raise a bug", "log a spike", "we should track this in Jira", or turning an RHDHSUPP support case into an RHDHBUGS defect or an RHDHPLAN feature request. Picking the issue type is this skill's job, not the caller's. Editing or transitioning an issue that already exists, such as RHIDP-1234, is not creation. | |
Ties a GitHub pull request or GitLab merge request to an RHDH Jira issue in RHIDP, RHDHPLAN, RHDHBUGS, or RHDHSUPP: attach the Jira Web link titled | |
| Judges whether RHDH Jira work that already exists is ready to move forward — in RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP. Checks an issue, a JQL result, a sprint, or a backlog against the exit criteria for its status, then reports missing fields, hierarchy gaps, likely duplicates, unaddressed comments, stale work, and Feature Exploration readiness. Use for "is RHIDP-1234 ready", "refine this", "refine the backlog", "backlog hygiene", "what's missing on this epic", "run the Feature Exploration checklist", or "which of these are stale". Assesses existing work; it does not open new issues and does not build a sprint. | |
| Builds the planning package for an RHDH scrum team's next sprint from Jira RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP: carryover from the active sprint, three-sprint velocity, per-member capacity, the ready-for-planning queue, available capacity, suggested fill, critical customer bugs, and retro action items. Use for "plan the sprint", "sprint planning prep", "what's our capacity next sprint", "what can we commit to", or "what's carrying over". Works on a team and a sprint, not on one issue — a bare key such as RHIDP-1234 is not a sprint. Looks forward at the sprint that has not started; summarizing the one that just ended is a different job. | |
| Summarizes an RHDH sprint that has finished or is finishing, from Jira RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP: committed versus completed story points, scope added mid-sprint, per-member breakdown, epic progress, the demo checklist with RHDH file and slide naming, and the velocity trend. Use for "sprint report", "what did we complete this sprint", "sprint review prep", "how did the sprint go", or "which demos do we owe". Looks back at work already done; preparing the sprint that has not started yet is a different job, and a single issue such as RHIDP-1234 is not a sprint. | |
| Changes an RHDH Jira issue you already have a key for, in RHIDP, RHDHPLAN, RHDHBUGS, or RHDHSUPP: post a progress comment, transition status, add an issue link or a web link to a PR, close with a resolution and rationale, and pick and set the assignee from team roster, recent expertise, and sprint capacity. Use for "update jira", "update RHIDP-1234", "log my progress on this", "move this to Review", "close this out", "who should take this", or "assign RHIDP-1234". Edits existing work — it does not create issues, audit a backlog, or build a sprint. | |
| Moves the @backstage/* dependency versions of a Backstage plugin, workspace, or app forward to a chosen release, staying within what a Red Hat Developer Hub version ships: read backstage.json and package.json, pick the target from the RHDH compatibility matrix or an explicit version, run backstage-cli versions:bump and versions:migrate, work through the release changelogs for breaking changes, and re-verify with yarn tsc, yarn build, and yarn test. Use for "upgrade @backstage dependencies", "versions:bump", "which Backstage version does RHDH 1.8 ship", moved package namespaces, or a plugin whose dependencies are too old for the API it needs. | |
| 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. | |
| Manages the rhdh-plugin-export-overlays repository and Extensions Catalog: onboard plugins, update upstream versions, repair export or publish failures, inspect workspace health, triage the overlay PR backlog by label, staleness and merge readiness, and trigger /publish. Use for source.json, plugins-list.yaml, backstage.json, catalog metadata, overlay CI, plugin import, overlay PRs, or testing exact PR artifacts before merge. For code-level review of a pull request, use /rhdh-pr-review. To promote an rhdh-plugins release through overlays into rhdh-plugin-catalog, use /rhdh-plugin-midstream-propagate. | |
| Writes Backstage plugin source for Red Hat Developer Hub in rhdh-plugins or community-plugins: scaffold a backend dynamic plugin with createBackendPlugin or createBackendModule from @backstage/backend-plugin-api, scaffold a frontend dynamic plugin, and implement features against Backstage UI (@backstage/ui), MUI, Scalprum bundles, fetchApi, i18n, and the Backstage test utilities. Use for "scaffold a backend dynamic plugin", "create a frontend dynamic plugin", "implement this plugin feature", entity cards, scaffolder actions, catalog processors, backend extension points, renderInTestApp and TestApiProvider tests, dev app setup, and the local build gates yarn tsc:full and yarn build:api-reports:only. | |
| Reproduces, diagnoses, and fixes a defect in a Backstage plugin inside the rhdh-plugins or community-plugins repositories: resolve the report from a RHIDP, RHDHBUGS, RHDHPLAN or RHDHSUPP Jira key, a GitHub issue, or plain prose; locate the owning workspace; write a throwaway reproduction test that fails for the stated reason; record before and after Playwright video evidence for a UI defect; then apply the smallest fix and verify it. Use for "fix this plugin bug", "reproduce RHIDP-1234", a plugin that renders the wrong thing, or a regression that needs evidence before and after. | |
| Turns a Backstage plugin you are developing into a deployable Red Hat Developer Hub dynamic plugin artifact: run @red-hat-developer-hub/cli plugin export to produce dist-dynamic and dist-scalprum, choose shared, embedded and bundled dependencies, package as an OCI image, tgz archive or npm package, push to quay.io or another registry, and generate the SHA-512 or sha256 digest integrity values a deployment needs. Use for "export my plugin", "package the plugin as OCI", "push the plugin to a registry", --shared-package, --embed-package, plugin-manifest.json, or integrity hashes. For a failing export in the rhdh-plugin-export-overlays repository, use /rhdh-overlay instead. | |
| Propagates an rhdh-plugins workspace change through overlays and rhdh-plugin-catalog (midstream): changeset + npm publish, overlays source.json to the Version Packages SHA, then a surgical catalog MR (overlay-repo/, workspaces/, plugin_builds/, .tekton PLR tags like 2.0.0--0.0.3) without a full sync-midstream --force-clone. Use when promoting plugin versions, waiting on npm @red-hat-developer-hub packages, bumping overlays repo-ref, or midstream Hermeto/lock/PLR updates for one workspace. For an overlays workspace edit outside this promotion chain, use /rhdh-overlay. | |
| Converts a legacy Backstage frontend plugin used by Red Hat Developer Hub to the New Frontend System (NFS): replace createPlugin and createRoutableExtension with createFrontendPlugin, PageBlueprint, EntityContentBlueprint, AppDrawerContentBlueprint and createFrontendModule; map RHDH app-config.dynamic.yaml mount points onto extensions; add the ./alpha export to package.json without breaking legacy consumers; and verify the migrated dynamic plugin in a real RHDH instance. Use for "migrate my plugin to NFS", Blueprint migration, createFrontendPlugin, compatWrapper, alpha versus colocated exports, translations moved into a createFrontendModule with pluginId app, RHDH operator app.extensions and app.routes.bindings, and ENABLE_STANDARD_MODULE_FEDERATION testing. | |
| Generates the Red Hat Developer Hub dynamic-plugins.yaml configuration that makes an exported Backstage frontend plugin appear in RHDH: derive the Scalprum name from plugin-manifest.json or the package name, and write the pluginConfig.dynamicPlugins.frontend block with dynamicRoutes, menuItems, mountPoints, appIcons, apiFactories, routeBindings, entity tabs, cards, context menu items, and provider components. Use for "generate the wiring for this plugin", "which mount point does this card need", entity page customization, importName, or a plugin that installs but never renders. To apply the configuration to a running instance instead, use /rhdh-local. | |
| Publishes verified changes from rhdh-plugins or community-plugins: detect the repository and affected workspaces, run the repository build pipeline, create package changesets, stage generated files safely, create a signed-off commit and branch, push, open a GitHub pull request, upload optional bug-fix recordings, and link Jira or GitHub issues. Use for raise PR, create or open a plugin PR, push verified plugin changes, or publish a verified change another skill handed off. | |
| Reviews the code in a Red Hat Developer Hub pull request: fetch its diff, linked issues and CI status, analyze the changes, draft inline comments, post the review to GitHub, and for an rhdh-operator PR optionally deploy its CI-built bundle onto a live OpenShift cluster and verify the change there. Use for a GitHub PR URL or number, "review this PR", analysis-only review, inline comments, posting a review, testing operator PR images or bundles on a cluster, or a combined code and cluster review. For label and merge-readiness triage of the overlay PR backlog, use /rhdh-overlay. | |
| Advises where a permanent automated test for the Red Hat Developer Hub dynamic-plugin ecosystem should live: which repository (rhdh, rhdh-plugins, or rhdh-plugin-export-overlays), which layer (L1 unit, L2 startTestBackend integration, L3 React Testing Library component, L4a cluster-free Playwright, or L4b cluster e2e), which harness, and which neighbouring file to mirror. Use for "where should this test live", "which repo and layer for this test", "does this need a cluster", "is this e2e too expensive", or a review comment that a test sits at the wrong layer. Advice only — it recommends a placement and names a template; it writes no test and changes no file. | |
Analyzes and updates the | |
Bumps Konflux Tekton task bundle digests in | |
Lists, generates, and removes RHDH test entries and Hive ClusterPools in the openshift/release Prow ci-operator configuration. Covers OCP | |
Commissions or decommissions the openshift/release Prow configuration for a single RHDH release branch: the ci-operator config | |
Runs an RHDH nightly ProwJob on demand through the OpenShift CI Gangway REST API, for | |
Bumps Yarn Berry across the RHDH repos — rhdh-plugins, rhdh midstream, rhdh-plugin-export-overlays, rhdh-cli, and GitLab CEE rhidp/rhdh and rhdh-plugin-catalog — with | |
Builds the "RHDH CVE Management - <version>-plugins.csv" export by walking | |
| Reports vendor support phases and end-of-life dates for RHDH and the platforms it runs on: OpenShift, ARO, OSD, ROSA, AKS, EKS, GKE, PostgreSQL, Red Hat build of Keycloak, and Quay. Use for "is OCP 4.16 still supported", "when does PostgreSQL 15 go EOL", "which Kubernetes version should AKS be on", "which OCP versions does RHDH 1.10 support", or an RHBK or Quay lifecycle lookup. Product lifecycle only — RHDH milestone dates such as Code Freeze belong to rhdh-release-schedule. | |
| Drafts the Slack message for an RHDH Feature Freeze or Code Freeze — either the milestone announcement sent on the day or the status update sent ahead of it — filling team counts, blocker bugs, CVEs, release notes, feature demos, and Test Day figures from Jira RHIDP and RHDHPLAN. Use for "announce feature freeze", "draft the code freeze message for 1.10", "send the freeze update for 1.11", or "write the freeze post for the release channel". | |
| Gives the milestone dates for an RHDH version — Feature Freeze, Code Freeze, Docs Input Freeze, Docs Freeze, Go/No Go & Push, and GA announce — reading active releases from the RHDHPLAN release Feature in Jira and planned ones from the RHDH release schedule spreadsheet. Use for "when is code freeze for 1.11", "RHDH release dates", "GA date for 2.1", "what are the key dates for 1.10.3", or "has 1.10 passed feature freeze yet". | |
| Reports what is still open against an RHDH release from Jira RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP: issue counts by type, blocker bugs, CVEs, Engineering EPICs, per-team breakdowns, release-note lifecycle, Post Code Freeze scope, and any query in the RHIDP Operational Rich Filter export. Also reports readiness at the Feature and Program Increment level: PI funnel, feature status matrix, stretch features, epic roll-up, cross-team dependency map, per-Feature coherence, and risk assessment. Use for "release status for 1.10", "what's blocking 1.10.3", "are we ready to ship 1.10", or "PI funnel for 2.1". | |
Resolves the RHDH team roster from the RHDH Team Mapping spreadsheet — team name, category, team ID, leads, Slack handles, and the Jira Cloud ID used in | |
| Reviews the platform and integration version tables and the key-date table in an RHDH test-plan Jira issue against vendor lifecycle data and the release schedule, then applies the accepted edits. Covers OCP, ARO, OSD, ROSA, AKS, EKS, GKE, PostgreSQL, RHBK, and Quay rows. Use for "review the test plan for 1.11", "which platform versions should the 1.10 test plan list", "update the test plan dates", or a test-plan Jira URL or key such as RHIDP-1234. | |
| Names the breaking and notable changes between the early Backstage New Frontend System alpha and the current GA surface, for Red Hat Developer Hub plugins: NavItemBlueprint removed in favour of nav auto-discovery from PageBlueprint, config.schema replaced by top-level configSchema with direct zod/v4 imports, AppRootWrapperBlueprint Component renamed to component and moved to @backstage/plugin-app-react, defaultPath/defaultTitle/defaultGroup renamed, SubPageBlueprint added, useRouteRef returning undefined, and AppDrawerContentBlueprint taking element rather than loader. Use when NFS code that used to compile now fails, a Blueprint param produces a TypeScript error, or a plugin migrated against an older alpha needs bringing forward. | |
| Supplies the approval rule another RHDH skill applies when it is already about to change something outside the session: how to state each operation, what approval binds to, what to report afterwards, and how to keep credentials out of a plan preview. Cited by name from the skill doing the work. Not an entry point — it performs no forge, Jira, or repository action itself, and a request to open, comment, transition, push, or post belongs to the skill that owns that target. | |
Resolves the environment the other RHDH skills start from and hands back one JSON document: which RHDH repositories are checked out and where — rhdh, rhdh-operator, rhdh-plugins, rhdh-plugin-export-overlays, rhdh-plugin-catalog, rhdh-cli, rhdh-chart, rhdh-local, backstage and the rest — which tools are on PATH, and the target RHDH and Backstage versions with the source that produced them. Also owns the | |
| Reads GitHub and GitLab on behalf of the other RHDH skills: parse an issue, pull request, or merge request reference, fetch issue detail as JSON, resolve the plugin workspace an issue belongs to, read check or pipeline status and failed run logs, and read repository files through the API. Use for a GitHub or GitLab issue URL, a bare #number, a !number merge request, "which workspace is this issue in", a stale statusCheckRollup, "why did that check fail", gh, glab, or jq syntax for a forge read, and the exact payload behind a comment, label, assignee, approval, or /publish write. | |
Reads RHDH Jira and owns the mechanics every other RHDH Jira skill needs: | |
| Supplies the craft of writing good RHDH Jira work in RHIDP, RHDHPLAN, RHDHBUGS, and RHDHSUPP: the Feature, Epic, Story, Task, and Bug description templates with filled examples, the RHDH challenge matrix that stress-tests scope, sizing, acceptance criteria, and Epic independence, the T-shirt and Fibonacci sizing scales, keyword duplicate detection, and the tracer-bullet rules for breaking a Feature into Epics or an Epic into Stories. Use when drafting or judging the text and shape of an issue such as RHIDP-1234 — how big is this, is this AC testable, should this be one Epic or three, does this already exist. Prose and estimation craft only; it runs no Jira command. | |
| Assesses and improves a git repository's readiness for AI coding agents with the agentready tool, and reports the score, the certification level, the failing findings, and where the report was written. Covers one repository or every RHDH repository under a directory, and applies the fixes the report supports. Use for "assess agent readiness", "run agentready", "improve our agent readiness score", "prepare this repository for coding agents", or "assess all the RHDH repositories". | |
| Creates, audits, and consolidates Agent Skills that follow the Agent Skills open standard, and hands back a drafted or repaired skill with the review checklist for its branch applied. Use for "create a skill", "draft a SKILL.md", "package this expertise as a skill", "why does this skill never trigger", "audit this SKILL.md", "improve this skill", or merging overlapping skills into fewer deeper modules. Covers frontmatter, descriptions that trigger, progressive disclosure, completion criteria, and bundled scripts. | |
If the outcome is ambiguous, ask one question that separates the competing rows. Otherwise, state
the handoff in the conversation and invoke the selected model skill:
- Domain — the routing row that matched.
- Outcome — the observable result the user asked for.
- Inputs — the user's own wording, verbatim.
- Constraints and approvals — what the user has already ruled in or out.
The handoff stays in the conversation. The selected model skill owns everything the work produces.
State the request in the user's own words rather than translating it into filesystem paths or
implementation details.
以下每一行都是模型技能的描述，由从目录中生成。请勿手动编辑表格：添加、删除或重新描述技能后，运行，使用检测内容偏差。在此处改写技能描述会产生冲突的清单，这是该表格过去存在的问题。
<!-- BEGIN GENERATED ROUTES: python scripts/render_routes.py --write -->
scripts/render_routes.pypython scripts/render_routes.py --write--check| 当请求为 | 模型技能 |
|---|---|
| 在RHDH Jira中创建新工作项，并确定工作项类型——RHDHPLAN中的Feature或Feature Request、RHIDP中的Epic、Story、Task、Spike或Vulnerability、RHDHBUGS中的Bug、RHDHSUPP中的支持对话——随后通过问询、起草，创建包含正确字段和父链接的工作项。适用于“提交工单”、“创建功能”、“为此创建Epic”、“上报Bug”、“记录Spike”、“我们应该在Jira中跟踪这个”，或将RHDHSUPP支持案例转为RHDHBUGS缺陷或RHDHPLAN功能请求。选择问题类型是该技能的职责，而非调用者的任务。编辑或流转已存在的问题（如RHIDP-1234）不属于创建操作。 | |
将GitHub拉取请求或GitLab合并请求关联到RHIDP、RHDHPLAN、RHDHBUGS或RHDHSUPP中的RHDH Jira问题：添加标题为 | |
| 判断RHIDP、RHDHPLAN、RHDHBUGS和RHDHSUPP中已存在的RHDH Jira工作项是否可推进。检查单个问题、JQL查询结果、迭代或待办事项是否符合其状态的退出标准，然后报告缺失字段、层级缺口、疑似重复项、未处理评论、过期工作项以及Feature Exploration就绪情况。适用于“RHIDP-1234是否就绪”、“优化这个”、“优化待办事项”、“待办事项清理”、“这个Epic缺少什么”、“运行Feature Exploration检查清单”或“哪些工作项已过期”。仅评估现有工作，不创建新问题，也不构建迭代。 | |
| 从Jira的RHIDP、RHDHPLAN、RHDHBUGS和RHDHSUPP中为RHDH Scrum团队的下一个迭代构建规划包：当前迭代的遗留工作、三次迭代的速度、成员个人容量、待规划就绪队列、可用容量、建议补充内容、关键客户Bug以及回顾行动项。适用于“规划迭代”、“迭代规划准备”、“我们下一个迭代的容量是多少”、“我们可以承诺什么”或“有哪些遗留工作”。针对团队和迭代工作，不处理单个问题——仅提供RHIDP-1234这类问题编号不属于迭代规划。仅面向未开始的迭代；总结刚结束的迭代属于其他任务。 | |
| 总结已完成或即将完成的RHDH迭代，数据来自Jira的RHIDP、RHDHPLAN、RHDHBUGS和RHDHSUPP：承诺与完成的故事点数对比、迭代中期新增范围、成员个人任务分解、Epic进度、包含RHDH文件和幻灯片命名规范的演示检查清单，以及速度趋势。适用于“迭代报告”、“我们这个迭代完成了什么”、“迭代评审准备”、“迭代进展如何”或“我们需要进行哪些演示”。仅回顾已完成的工作；准备未开始的迭代属于其他任务，单个问题如RHIDP-1234不属于迭代总结范畴。 | |
| 修改RHIDP、RHDHPLAN、RHDHBUGS或RHDHSUPP中已有编号的RHDH Jira问题：发布进度评论、流转状态、添加问题链接或PR网页链接、填写解决方案和理由后关闭问题，并根据团队名单、近期专业技能和迭代容量选择并设置经办人。适用于“更新Jira”、“更新RHIDP-1234”、“记录我的工作进度”、“将此移至评审状态”、“关闭这个问题”、“谁应该接手这个”或“分配RHIDP-1234”。仅编辑现有工作——不创建问题、审计待办事项或构建迭代。 | |
| 将Backstage插件、工作区或应用的@backstage/*依赖版本升级到选定的发行版，且符合Red Hat Developer Hub版本的兼容范围：读取backstage.json和package.json，从RHDH兼容性矩阵或指定版本中选择目标版本，运行backstage-cli versions:bump和versions:migrate，处理发行版变更日志中的破坏性变更，并通过yarn tsc、yarn build和yarn test重新验证。适用于“升级@backstage依赖”、“versions:bump”、“RHDH 1.8包含哪个Backstage版本”、包命名空间变更，或依赖版本过旧无法满足所需API的插件。 | |
| 使用rhdh-local-setup定制系统操作本地Red Hat Developer Hub环境：启用或禁用动态插件、应用配置、切换原始模式与定制模式、启动或停止容器、检查健康状态和日志、运行插件验证，以及备份或恢复定制内容。适用于本地RHDH操作、podman compose插件测试、PR制品验证、504错误或启动故障排查，以及本地Extensions Catalog检查。 | |
| 管理rhdh-plugin-export-overlays仓库和Extensions Catalog：插件接入、更新上游版本、修复导出或发布失败问题、检查工作区健康状态、按标签、过期时间和合并就绪情况分类处理overlay PR待办事项，以及触发/publish。适用于source.json、plugins-list.yaml、backstage.json、目录元数据、overlay CI、插件导入、overlay PR，或合并前测试精确的PR制品。如需对拉取请求进行代码层面的评审，请使用/rhdh-pr-review。如需通过overlay将rhdh-plugins发行版推广到rhdh-plugin-catalog，请使用/rhdh-plugin-midstream-propagate。 | |
| 为Red Hat Developer Hub在rhdh-plugins或community-plugins中编写Backstage插件源码：使用@backstage/backend-plugin-api的createBackendPlugin或createBackendModule搭建后端动态插件，搭建前端动态插件，并基于Backstage UI (@backstage/ui)、MUI、Scalprum bundles、fetchApi、i18n和Backstage测试工具实现功能。适用于“搭建后端动态插件”、“创建前端动态插件”、“实现此插件功能”、实体卡片、脚手架动作、目录处理器、后端扩展点、renderInTestApp和TestApiProvider测试、开发应用设置，以及本地构建门限yarn tsc:full和yarn build:api-reports:only。 | |
| 在rhdh-plugins或community-plugins仓库中重现、诊断并修复Backstage插件缺陷：根据RHIDP、RHDHBUGS、RHDHPLAN或RHDHSUPP的Jira编号、GitHub问题或普通描述解决报告；定位所属工作区；编写一个因所述问题而失败的一次性重现测试；为UI缺陷记录修复前后的Playwright视频证据；然后应用最小化修复并验证。适用于“修复此插件Bug”、“重现RHIDP-1234”、渲染内容错误的插件，或需要修复前后证据的回归问题。 | |
| 将你正在开发的Backstage插件转换为可部署的Red Hat Developer Hub动态插件制品：运行@red-hat-developer-hub/cli plugin export生成dist-dynamic和dist-scalprum，选择共享、嵌入和捆绑依赖，打包为OCI镜像、tgz归档或npm包，推送到quay.io或其他注册表，并生成部署所需的SHA-512或sha256摘要完整性值。适用于“导出我的插件”、“将插件打包为OCI”、“将插件推送到注册表”、--shared-package、--embed-package、plugin-manifest.json，或完整性哈希。如果rhdh-plugin-export-overlays仓库中的导出失败，请使用/rhdh-overlay。 | |
| 将rhdh-plugins工作区的变更通过overlay和rhdh-plugin-catalog（中游）传播：变更集 + npm发布、将overlay的source.json更新为Version Packages SHA，然后进行精准的目录MR（overlay-repo/、workspaces/、plugin_builds/、.tekton PLR标签如2.0.0--0.0.3），无需完整的sync-midstream --force-clone。适用于推广插件版本、等待npm @red-hat-developer-hub包、升级overlay repo-ref，或单个工作区的中游Hermeto/lock/PLR更新。如果是此推广链之外的overlay工作区编辑，请使用/rhdh-overlay。 | |
| 将Red Hat Developer Hub使用的旧版Backstage前端插件迁移到New Frontend System (NFS)：用createFrontendPlugin、PageBlueprint、EntityContentBlueprint、AppDrawerContentBlueprint和createFrontendModule替换createPlugin和createRoutableExtension；将RHDH app-config.dynamic.yaml挂载点映射到扩展；在package.json中添加./alpha导出且不破坏旧版消费者；并在真实RHDH实例中验证迁移后的动态插件。适用于“将我的插件迁移到NFS”、Blueprint迁移、createFrontendPlugin、compatWrapper、alpha与共存导出、迁移到带有pluginId app的createFrontendModule的翻译内容、RHDH operator app.extensions和app.routes.bindings，以及ENABLE_STANDARD_MODULE_FEDERATION测试。 | |
| 生成Red Hat Developer Hub的dynamic-plugins.yaml配置，使导出的Backstage前端插件在RHDH中可见：从plugin-manifest.json或包名推导Scalprum名称，编写包含dynamicRoutes、menuItems、mountPoints、appIcons、apiFactories、routeBindings、实体标签页、卡片、上下文菜单项和提供者组件的pluginConfig.dynamicPlugins.frontend块。适用于“为此插件生成配置”、“此卡片需要哪个挂载点”、实体页面定制、importName，或已安装但从未渲染的插件。如需将配置应用到运行中的实例，请使用/rhdh-local。 | |
| 发布rhdh-plugins或community-plugins中已验证的变更：检测仓库和受影响的工作区，运行仓库构建流水线，创建包变更集，安全暂存生成的文件，创建已签署的提交和分支，推送，打开GitHub拉取请求，上传可选的Bug修复记录，并关联Jira或GitHub问题。适用于“提交PR”、“创建或打开插件PR”、“推送已验证的插件变更”，或发布其他技能移交的已验证变更。 | |
| 评审Red Hat Developer Hub拉取请求中的代码：获取差异、关联问题和CI状态，分析变更，起草行内评论，将评审发布到GitHub，对于rhdh-operator PR，可选择将其CI构建的bundle部署到实时OpenShift集群并验证变更。适用于GitHub PR URL或编号、“评审此PR”、仅分析评审、行内评论、发布评审、在集群上测试operator PR镜像或bundle，或代码与集群结合的评审。如需对overlay PR待办事项进行标签和合并就绪情况分类，请使用/rhdh-overlay。 | |
| 建议Red Hat Developer Hub动态插件生态的永久自动化测试应放置的位置：哪个仓库（rhdh、rhdh-plugins或rhdh-plugin-export-overlays）、哪个层级（L1单元测试、L2 startTestBackend集成测试、L3 React Testing Library组件测试、L4a无集群Playwright测试或L4b集群端到端测试）、哪个测试框架，以及参考哪个相邻文件。适用于“此测试应放在哪里”、“此测试应使用哪个仓库和层级”、“是否需要集群”、“此端到端测试成本过高吗”，或评审评论中提到测试层级错误的情况。仅提供建议——推荐放置位置并命名模板；不编写测试或修改文件。 | |
在 | |
在RHDH中游和rhdh-plugin-catalog树中，升级 | |
在openshift/release Prow ci-operator配置中列出、生成和删除RHDH测试条目和Hive ClusterPools。涵盖OCP | |
为单个RHDH发行分支配置或取消配置openshift/release Prow：ci-operator配置文件 | |
通过OpenShift CI Gangway REST API按需运行RHDH夜间ProwJob，支持 | |
在所有RHDH仓库中升级Yarn Berry——rhdh-plugins、rhdh中游、rhdh-plugin-export-overlays、rhdh-cli，以及GitLab CEE的rhidp/rhdh和rhdh-plugin-catalog——使用 | |
通过遍历发行分支上 | |
| 报告RHDH及其运行平台的供应商支持阶段和终止日期：OpenShift、ARO、OSD、ROSA、AKS、EKS、GKE、PostgreSQL、Red Hat build of Keycloak和Quay。适用于“OCP 4.16是否仍受支持”、“PostgreSQL 15何时终止支持”、“AKS应使用哪个Kubernetes版本”、“RHDH 1.10支持哪些OCP版本”，或RHBK或Quay生命周期查询。仅涉及产品生命周期——RHDH里程碑日期（如代码冻结）属于rhdh-release-schedule的范畴。 | |
| 为RHDH功能冻结或代码冻结起草Slack消息——当天发送的里程碑公告或提前发送的状态更新——从Jira的RHIDP和RHDHPLAN填充团队数量、阻塞Bug、CVE、发行说明、功能演示和测试日数据。适用于“公告功能冻结”、“为1.10版本起草代码冻结消息”、“发送1.11版本的冻结更新”，或“为发行频道撰写冻结帖子”。 | |
| 提供RHDH版本的里程碑日期——功能冻结、代码冻结、文档输入冻结、文档冻结、Go/No Go & Push和GA发布——从Jira的RHDHPLAN发行Feature读取活跃版本，从RHDH发行计划电子表格读取计划版本。适用于“1.11版本的代码冻结时间是什么时候”、“RHDH发行日期”、“2.1版本的GA日期”、“1.10.3版本的关键日期是什么”，或“1.10版本是否已过功能冻结期”。 | |
| 报告Jira的RHIDP、RHDHPLAN、RHDHBUGS和RHDHSUPP中RHDH发行版仍未解决的问题：按类型统计问题数量、阻塞Bug、CVE、工程EPIC、团队细分、发行说明生命周期、代码冻结后新增范围，以及RHIDP Operational Rich Filter导出中的任何查询结果。还报告Feature和Program Increment级别的就绪情况：PI漏斗、功能状态矩阵、扩展功能、Epic汇总、跨团队依赖图、Feature一致性和风险评估。适用于“1.10版本的发行状态”、“1.10.3版本的阻塞因素是什么”、“我们是否准备好发布1.10版本”，或“2.1版本的PI漏斗”。 | |
从RHDH Team Mapping电子表格解析RHDH团队名单——团队名称、类别、团队ID、负责人、Slack句柄，以及 | |
| 根据供应商生命周期数据和发行计划，评审RHDH测试计划Jira问题中的平台和集成版本表以及关键日期表，然后应用已接受的编辑。涵盖OCP、ARO、OSD、ROSA、AKS、EKS、GKE、PostgreSQL、RHBK和Quay行。适用于“评审1.11版本的测试计划”、“1.10版本的测试计划应列出哪些平台版本”、“更新测试计划日期”，或测试计划Jira URL或编号（如RHIDP-1234）。 | |
| 列出Red Hat Developer Hub插件使用的Backstage New Frontend System早期alpha版本与当前GA版本之间的破坏性和显著变更：移除NavItemBlueprint，改为从PageBlueprint自动发现导航；用顶级configSchema（直接导入zod/v4）替换config.schema；将AppRootWrapperBlueprint Component重命名为component并移至@backstage/plugin-app-react；defaultPath/defaultTitle/defaultGroup重命名；添加SubPageBlueprint；useRouteRef返回undefined；AppDrawerContentBlueprint接受element而非loader。适用于曾经可编译的NFS代码现在编译失败、Blueprint参数产生TypeScript错误，或针对旧alpha版本迁移的插件需要升级的情况。 | |
| 提供其他RHDH技能在会话外进行变更时应用的审批规则：如何表述每个操作、审批绑定到什么内容、事后报告什么，以及如何在计划预览中避免泄露凭据。由执行工作的技能按名称引用。不是入口点——本身不执行任何forge、Jira或仓库操作，打开、评论、流转、推送或发布请求属于对应目标的技能负责。 | |
解析其他RHDH技能的起始环境，并返回一个JSON文档：已检出的RHDH仓库及其位置——rhdh、rhdh-operator、rhdh-plugins、rhdh-plugin-export-overlays、rhdh-plugin-catalog、rhdh-cli、rhdh-chart、rhdh-local、backstage等——PATH中的工具，以及生成这些版本的RHDH和Backstage目标版本。还负责工作区状态、工作日志和待办事项背后的 | |
| 代表其他RHDH技能读取GitHub和GitLab：解析问题、拉取请求或合并请求引用，以JSON格式获取问题详情，解析问题所属的插件工作区，读取检查或流水线状态以及失败运行日志，通过API读取仓库文件。适用于GitHub或GitLab问题URL、纯数字#编号、!编号合并请求、“此问题属于哪个工作区”、过期的statusCheckRollup、“检查失败的原因是什么”、gh、glab或jq语法的forge读取，以及评论、标签、经办人、审批或/publish写入背后的精确负载。 | |
读取RHDH Jira，并负责其他所有RHDH Jira技能所需的机制： | |
| 提供在RHIDP、RHDHPLAN、RHDHBUGS和RHDHSUPP中编写优质RHDH Jira工作项的技巧：Feature、Epic、Story、Task和Bug的描述模板及填充示例、用于压力测试范围、规模、验收标准和Epic独立性的RHDH挑战矩阵、T恤和斐波那契规模度量、关键词重复检测，以及将Feature拆分为Epic或Epic拆分为Story的追踪规则。适用于起草或判断问题（如RHIDP-1234）的文本和结构——这个问题规模多大、验收标准是否可测试、应该是一个Epic还是三个、是否已存在重复项。仅负责文案和估算技巧；不执行任何Jira命令。 | |
| 使用agentready工具评估并提升git仓库对AI编码代理的就绪度，报告分数、认证级别、失败项以及报告写入位置。涵盖单个仓库或目录下的所有RHDH仓库，并应用报告支持的修复。适用于“评估代理就绪度”、“运行agentready”、“提升我们的代理就绪度分数”、“为编码代理准备此仓库”，或“评估所有RHDH仓库”。 | |
| 创建、审计和整合遵循Agent Skills开放标准的Agent Skills，并返回已起草或修复的技能，同时应用其分支的评审检查清单。适用于“创建技能”、“起草SKILL.md”、“将此专业知识打包为技能”、“为什么此技能从未触发”、“审计此SKILL.md”、“提升此技能”，或将重叠技能合并为更少更深入的模块。涵盖前置元数据、触发描述、渐进式披露、完成标准和捆绑脚本。 | |
如果结果不明确，提出一个问题区分冲突的行。否则，在对话中说明交接内容并调用选定的模型技能：
- 领域 — 匹配的路由行。
- 结果 — 用户请求的可观察成果。
- 输入 — 用户的原话。
- 约束与审批 — 用户已确定的取舍。
交接内容需保留在对话中。选定的模型技能负责所有工作产出。使用用户的原话表述请求，而非转换为文件系统路径或实现细节。
Completion
完成标准
Complete when exactly one row of the generated table has been named to the user, the handoff
repeats the request in the user's own words, and that skill has been invoked by name. When two rows
compete, ask the single disambiguating question and get its answer first. When the selected skill
stops because a capability is missing, complete only once that capability and the exact
supplying it have been reported. This skill routes and reports; it
changes nothing.
/setup-rhdh-skills <route>当向用户明确指定生成表格中的某一行、交接内容重复用户原话、且已按名称调用该技能时，任务完成。当两行存在冲突时，先提出一个明确的区分问题并获取答案。当选定的技能因缺少功能而停止时，仅在报告该缺失功能以及提供该功能的具体后，任务才算完成。本技能仅负责路由和报告，不进行任何修改操作。
/setup-rhdh-skills <route>