skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
redhat-developer/rhdh-skills95 installs

rhdh-pr-review

Reviews Red Hat Developer Hub pull request code on GitHub in rhdh, rhdh-operator, rhdh-plugins, or community-plugins. Use for a GitHub PR URL or number, "review this PR", analysis-only review, or posting inline comments. For label and merge-readiness triage of the overlay PR backlog, use /rhdh-overlay.

How do I install this agent skill?

npx skills add https://github.com/redhat-developer/rhdh-skills --skill rhdh-pr-review
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill automates PR reviews and operator testing using GitHub and OpenShift CLI tools. It follows security best practices by implementing a user-approval gate for all write operations. The primary risk is the potential for indirect prompt injection from untrusted PR metadata, which is mitigated by the manual verification steps.

  • Socketwarn

    1 alert: gptAnomaly

  • Snykwarn

    Risk: MEDIUM · 2 issues

What does this agent skill do?

RHDH Pull Request Review

Keep forge I/O at the edges: fetch produces the PR context, analysis works from that context and checked-out code alone, and posting sends only findings already verified against the head SHA.

Route by outcome

OutcomeWorkflow sequence
Code review and postworkflows/fetch-github.md → workflows/review-code.md → workflows/post-to-github.md
Analysis onlyworkflows/fetch-github.md → workflows/review-code.md; stop after the edited draft

A bare PR URL or number defaults to code review and post.

Review invariants

  • /code-review is required on every draft-review path, including analysis-only. If it is missing, stop, say that code-review is missing, name /setup-rhdh-skills install, and do not substitute a local two-axis review.
  • Every /code-review run also dispatches Adversarial. Team, worktree, and draft steps live in workflows/review-code.md.
  • Present the complete edited draft before stating any post operation. An explicit request to post is intent, not approval of the exact write.

Write gate

Fetch and analysis are read-only. Posting a GitHub review is an external write: invoke the named skill mutation-gate and follow the gate it owns rather than restating it here. Creating or removing a local git worktree is not that gate.

A review operation's target pins the head SHA. An earlier confirmation of findings approves no write. Report each outcome with the review URL, the verification done, and any recovery still owed.

What each stage carries forward

Every stage passes its result to the next in conversation. The field names are defined once, where they are produced:

StageResultDefined in
FetchPR context: repository, changeRequest, files, diff, linkedIssues, jiraKeys, existingComments, existingReviews, ciStatus, specSourceworkflows/fetch-github.md
AnalysisReview draft: changeRequest, summary, verdict, findings, edited, worktreePathworkflows/review-code.md

Completion

Complete when the report names the head SHA reviewed, has presented the /code-review Standards and Spec reports, and presents the edited draft. On the post route, also give the outcome of every approved write with its target.

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-pr-review">View rhdh-pr-review on skillZs</a>