rhdh-pr-review
Skill20 starsChanged 20 days agoApache-2.0View on GitHub
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.
In this repository73 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- rhdh-base-imagesSkill
- rhdh-konflux-rpaSkill
- rhdh-konflux-tasksSkill
- rhdh-plugin-catalog-index-status-and-update-flowSkill
- rhdh-pr-mrSkill
- rhdh-prow-jobsSkill
- rhdh-prow-release-branchSkill
- rhdh-prow-triggerSkill
- rhdh-yarn-bumpSkill
- rhdh-feature-docsSkill
- rhdh-jira-createSkill
- rhdh-jira-linkSkill
- rhdh-jira-refineSkill
- rhdh-jira-sprint-planSkill
- rhdh-jira-sprint-reportSkill
- rhdh-jira-updateSkill
- rhdh-prepare-refinementSkill
- agent-readinessSkill
- ask-rhdhSkill
- clean-proseSkill
- setup-rhdh-skillsSkill
- skill-authoringSkill
- rhdh-backportSkill
- rhdh-backstage-upgradeSkill
- rhdh-localSkill
- rhdh-operator-pr-testSkill
- rhdh-overlaySkill
- rhdh-playwrightSkill
- rhdh-plugin-authoringSkill
- rhdh-plugin-bug-fixSkill
- rhdh-plugin-exportSkill
- rhdh-plugin-midstream-propagateSkill
- rhdh-plugin-nfs-migrationSkill
- rhdh-plugin-wiringSkill
- rhdh-pr-createSkill
- rhdh-test-placementSkill
- backstage-api-changesSkill
- mutation-gateSkill
- openspec-journalSkill
- prose-editingSkill
- rhdh-contextSkill
- rhdh-forgeSkill
- rhdh-jira-apiSkill
- rhdh-jira-authoringSkill
- rhdh-spec-driven-schemaSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-audit-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- rhdh-overlay-cve-exportSkill
- rhdh-platform-lifecycleSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
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 …
- Very specific: line 33
Every /code-review run also dispatches Adversarial.
- Distinctive: line 50
Every stage passes its result to the next in conversation.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
| Outcome | Workflow sequence |
| Code review and post | workflows/fetch-github.md → workflows/review-code.md → workflows/post-to-github.md |
| Analysis only | workflows/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-reviewis required on every draft-review path, including analysis-only. If it is missing, stop, say thatcode-reviewis missing, name/setup-rhdh-skills install, and do not substitute a local two-axis review.- Every
/code-reviewrun also dispatches Adversarial. Team, worktree, and draft steps live inworkflows/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:
| Stage | Result | Defined in |
| Fetch | PR context: repository, changeRequest, files, diff, linkedIssues, jiraKeys, existingComments, existingReviews, ciStatus, specSource | workflows/fetch-github.md |
| Analysis | Review draft: changeRequest, summary, verdict, findings, edited, worktreePath | workflows/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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.