How do I install the Pr Generator skill?

Run npx skillmds@latest add willianbs/pr-generator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pr Generator safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pr Generator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pr Generator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pr Generator?

willianbs (@willianbs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pr Generator by willianbs — Agent Skill

Name: Pr Generator
Author: willianbs

Pr Generator

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.

willianbs 2ac31c3 2 files · 3.2 KB Updated Sep 17, 2026

File contents

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.

---name: pr-generatordescription: 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.---# PurposeProduce 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.# PreconditionsMust 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 Principles1. Diff and commits are the source of truth.2. Unknown beats fabricated “Why.”3. Testing section lists only commands actually run.4. Prefer `.github/PULL_REQUEST_TEMPLATE.md` (or org template) structure.5. Call out risks and rollout notes when evidenced.6. No emoji stuffing or hype.7. Never claim QG Pass without QG_REPORT.# Process1. Load template if present; else use default sections below.2. Summarize what changed from diff (paths + behavior).3. Why — only from commits/ticket/user; else `Unknown — please fill`.4. Test plan — from IMPL_REPORT commands_run only; mark untested explicitly.5. Risks / rollback — from PLAN or obvious migration/flag evidence.6. Include QG/Review decision if artifacts exist.7. Reviewer focus — sharp bullets, not essays.# Evidence RequirementsEvery 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 + ConfidenceN/A. Accuracy over completeness.# Output ContractDefault markdown:```markdown## Summary...## Why...## Changes- `path`: ...## Test plan- [ ] `command` — result (from IMPL_REPORT) / NOT RUN## Risks & rollback...## QualityQG/Review: ... or Unknown## Reviewer focus...```# HandoffsNone 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.

Frequently asked questions