Loading...
Loading...
Found 14 Skills
Install, configure, diagnose, or repair the complete RHDH skills environment.
Human wayfinder for the RHDH skills collection.
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.
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.
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.
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 `repo #N: <title>`, post or update the structured comment, fill empty issue fields, move an RHDHPLAN Epic, Story, or Task to RHIDP, and mark a Web link merged. Raises the PR or MR first when one does not exist yet. Use for "link this PR to RHIDP-1234", "attach the MR to the Jira issue", "mark the Web links merged", replacing a hand-rolled remotelink or comment step, or a PR outside the rhdh-plugins and community-plugins monorepo flow. The full monorepo flow — build, changeset, recordings — is rhdh-pr-create.
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 `rhdh` CLI behind workspace status, worklogs, and todos. Use for RHDH orientation, "where is my rhdh checkout", "which Backstage version goes with RHDH 1.10", `rhdh status`, `rhdh doctor`, `rhdh config`, `rhdh workspace`, `rhdh log`, `rhdh todo`, and for the read-only context another RHDH skill needs before it starts. Read-only — implementation work belongs to the domain skill that owns the requested outcome.
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.
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.
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".
Reads RHDH Jira and owns the mechanics every other RHDH Jira skill needs: `acli` flags and their traps, JQL for RHIDP, RHDHPLAN, RHDHBUGS and RHDHSUPP, custom field IDs, GraphQL and REST fallbacks, board and sprint IDs, the component catalog, and the workflow states with their exit criteria. Use to look up an issue such as RHIDP-1234, to write or debug a JQL query, to answer "which field is Story Points", "why is my search returning 30 rows", or "what does Release Pending require". Reading and query mechanics only — deciding what to file, judging readiness, or changing an issue belongs to the Jira skill that owns that verb.
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.