review-pr-risk
Skill14 starsChanged 3 months agoMITView on GitHub
Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Review PR Risk”. A useful skill states the six fields from Skills and routines. An open pull request needs a review that starts with what can break, what is untested, and what the description promised but the diff did not do. Every risk cites a path. No invented files. No coverage percentages unless they appear in CI output. Facts and inferences…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Dafenxz0/codex-maintainer-skillstheir own version, first seen Jun 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Dafenxz0/codex-maintainer-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- convert/claude.mdCLAUDE.md
- docs/llms.txtllms.txt
- audit-subscriptionsSkill
- cited-researchSkill
- cloud-bill-noteSkill
- collate-feature-asksSkill
- coordinate-launchSkill
- daily-digestSkill
- defend-calendarSkill
- design-bot-templateSkill
- detect-docs-driftSkill
- diff-competitorsSkill
- draft-call-followupSkill
- draft-changelogSkill
- draft-issueSkill
- draft-newsletterSkill
- draft-security-answersSkill
- draft-sqlSkill
- draft-support-replySkill
- garden-memorySkill
- harden-repoSkill
- incident-timelineSkill
- install-teamSkill
- interrogate-assumptionsSkill
- investigate-perfSkill
- log-promisesSkill
- package-evidenceSkill
- plan-tripSkill
- prep-meetingSkill
- queue-socialSkill
- ramp-new-hireSkill
- rank-account-healthSkill
- recommend-media-reallocSkill
- reconcile-expensesSkill
- remix-contentSkill
- reproduce-bugSkill
- research-accountsSkill
- route-workSkill
- sanitize-shareSkill
- scout-x-threadsSkill
- source-talentSkill
- sweep-ciSkill
- triage-inboxSkill
- vendor-renewalsSkill
- watch-aeoSkill
- watch-brandSkill
- weekly-saas-financeSkill
- write-win-lossSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 23
Read the description, the diff, and CI — in that order.
- Distinctive: line 31
Every risk cites a path. No invented files.
- Distinctive: line 41
Never merge, push, comment on GitHub, request reviewers, or change status checks without explicit in-chat approval.
≈ “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
Review PR Risk
Paste this into Grok Bot after a successful run:
Save the process we just used as a skill called “Review PR Risk”.
A useful skill states the six fields from Skills and routines.
1. When to use it
An open pull request needs a review that starts with what can break, what is untested, and what the description promised but the diff did not do.
2. Required inputs and access
- GitHub connector or a pasted PR URL
- Repository access on the shared computer if already cloned
- CI logs linked from the PR when present
3. Sequence of work
- Open the PR. If you cannot, stop and say so.
- Read the description, the diff, and CI — in that order.
- List breakage risk with file paths.
- List untested paths. If CI is missing, write "CI not found" rather than "tests look fine".
- Diff the description against the diff (context gap).
- Nits last. Verdict is one of request changes, comment, or approve-with-notes.
4. How to validate the result
Every risk cites a path. No invented files. No coverage percentages unless they appear in CI output. Facts and inferences are labeled.
5. What to return
A review pack with Risk, Tests, Context gap, Nits, Verdict, Action log. Not posted as a GitHub comment unless approved.
6. What requires approval
Never merge, push, comment on GitHub, request reviewers, or change status checks without explicit in-chat approval.
Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.
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.