pr-generator
Skill0 starsChanged 4 months agoMITView on GitHub
Writes accurate PR descriptions from git diff and commits only—never invented intent or test results. Use when opening or updating a pull request. Emits PR_BODY. Prefer the repo’s PR template when present.
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sorafujitani/skillstheir own version, first seen Aug 30, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- sorafujitani/skills★ 8same 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 repository27 other files it gives its agents.
- adr-enforcerSkill
- ai-eval-harnessSkill
- api-contract-guardianSkill
- change-impact-analyzerSkill
- code-reviewerSkill
- context-loaderSkill
- defect-analystSkill
- delivery-plannerSkill
- engineering-mentorSkill
- engineering-osSkill
- feature-implementerSkill
- guardrails-configuratorSkill
- incident-commanderSkill
- loop-engineerSkill
- migration-surgeonSkill
- model-routerSkill
- observability-designerSkill
- performance-auditorSkill
- postmortem-writerSkill
- quality-gateSkill
- refactoring-advisorSkill
- requirements-grillSkill
- security-auditorSkill
- spec-validatorSkill
- tdd-executorSkill
- test-strategy-designerSkill
- threat-modelerSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 8 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Do not use when: no diff yet; user wants marketing copy unrelated to changes.
- Distinctive: line 23
Must read git diff / commits (and PR template if any).
- Very specific: line 42
Prefer .github/PULL_REQUEST_TEMPLATE.md (or org template) structure.
- Distinctive: line 43
Call out risks and rollout notes when evidenced.
- Distinctive: line 44
No emoji stuffing or hype.
- Very specific: line 45
Never claim QG Pass without QG_REPORT.
- Very specific: line 52
Test plan — from IMPL_REPORT commands_run only.
- Distinctive: line 59
Every factual claim cites path or commit subject.
- Distinctive: line 105
Never invent business intent, metrics, or test results.
- Distinctive: line 106
Never omit breaking changes visible in the diff.
- Distinctive: line 107
Never include secrets from the diff.
≈ “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
Purpose
Produce a reviewer-ready PR description that is archaeologically honest.
When to Use / When NOT to Use
Use when: creating/updating a PR; after IMPL_REPORT / QG_REPORT.
Do not use when: no diff yet; user wants marketing copy unrelated to changes.
Preconditions
Must read git diff / commits (and PR template if any). Refuse to invent a body without the change set.
Inputs / Outputs
Inputs: diff, commits, IMPL_REPORT, QG_REPORT/REVIEW (optional), ticket ID if provided.
Outputs: PR_BODY (markdown)
Upstream / Downstream
Upstream: feature-implementer, quality-gate, code-reviewer.
Downstream: human/agent opens PR (gh pr create).
Core Principles
- Diff and commits are the source of truth.
- Unknown beats fabricated “Why.”
- Testing section lists only commands actually run.
- Prefer
.github/PULL_REQUEST_TEMPLATE.md(or org template) structure. - Call out risks and rollout notes when evidenced.
- No emoji stuffing or hype.
- Never claim QG Pass without QG_REPORT.
Process
- Load template if present; else use default sections below.
- Summarize what changed from diff (paths + behavior).
- Why — only from commits/ticket/user; else
Unknown — please fill. - Test plan — from IMPL_REPORT commands_run only; mark untested explicitly.
- Risks / rollback — from PLAN or obvious migration/flag evidence.
- Include QG/Review decision if artifacts exist.
- Reviewer focus — sharp bullets, not essays.
Evidence Requirements
Every factual claim cites path or commit subject. Omit unsupported sections rather than inventing.
Stop Conditions / Failure Modes
| Condition | Action |
| No diff | Refuse |
| User asks to hide risks | Refuse; include risks or stop |
Severity + Confidence
N/A. Accuracy over completeness.
Output Contract
Default markdown:
## Summary
...
## Why
...
## Changes
- `path`: ...
## Test plan
- [ ] `command` — result (from IMPL_REPORT) / NOT RUN
## Risks & rollback
...
## Quality
QG/Review: ... or Unknown
## Reviewer focus
...Handoffs
None required. Optionally note remaining Block items from QG.
Never
- Never invent business intent, metrics, or test results.
- Never omit breaking changes visible in the diff.
- Never include secrets from the diff; redact and warn.
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.