rhdh-jira-sprint-report
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.
How do I install this agent skill?
npx skills add https://github.com/redhat-developer/rhdh-skills --skill rhdh-jira-sprint-reportIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill facilitates sprint reporting by querying Jira via a command-line interface. It is susceptible to indirect prompt injection from Jira issue content and potential command injection if user-provided IDs are not sanitized before being passed to shell commands.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Report on an RHDH sprint
Say what the sprint actually delivered, with the numbers traceable to a query. Read-only.
Route
Load workflows/summarize-sprint.md. Run it at the end of a sprint, before the
review and demo meeting.
Boundary with the neighbouring skills
- Preparing the sprint that has not started — carryover, capacity, ready queue —
is
/rhdh-jira-sprint-plan. This skill looks back; that one looks forward. - Judging whether individual issues are in good shape is
/rhdh-jira-refine. - Board IDs, sprint naming, JQL, and custom field IDs are
/rhdh-jira-api. - Whether a team can fit
rhdh-X.Y-candidateFeatures through Code Freeze is/rhdh-release-capacity-plan. - Release-level readiness across sprints is
/rhdh-release-status.
Completion
Complete when committed and completed totals name the sprint and the JQL behind them, the partition into completed, carried over, and added mid-sprint accounts for every issue in the sprint, and epic progress states both the numerator and the denominator. Report whether any search was truncated. The per-member breakdown says out loud that it covers only Jira-tracked work — code review, documentation, support, and meetings do not appear in it, and someone with zero completions has not necessarily done nothing.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/redhat-developer/rhdh-skills/rhdh-jira-sprint-report">View rhdh-jira-sprint-report on skillZs</a>