pr-summary SKILL.md skillA
pr-summary from gufranco/claude-engineering-rules is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gufranco/claude-engineering-rules/pr-summary@git:20261028.383f696Pins git:20261028.383f696 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gufranco/claude-engineering-rules
- Path
skills/pr-summary/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.383f696, committed Oct 28, 2026
- First version recorded
- May 21, 2026
- Size
- 8,943 bytes
- Repository stars
- 3
- License
- MIT
Generate a PR summary with reviewer suggestions based on file ownership. Fetches PR data, summarizes changes, highlights risks, and recommends reviewers from git history. Use when user says "pr summary", "summarize this PR", "who should review this", "generate PR description", when /morning finds a description that drifted from its diff, or wants a reviewer-ready summary of a pull request. For code review, use /review; for creating PRs, use /ship pr; for checking CI status, use /ship checks.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
## Overview Generates a reviewer-friendly summary of a pull request and suggests reviewers based on file ownership history. ## When to Use - A PR is open and needs reviewers picked from who actually knows the changed files. - The PR description is empty, under 50 characters, or has drifted from the diff, including when `/morning` flags the drift. - A reviewer wants the risk areas and the Merge Danger call before reading the diff. - For a line-by-line review, use `/review`; for opening the PR, use `/ship pr`; for CI status, use `/ship checks`. ## Arguments | Invocation | Action | |-----------|--------| | `/pr-summary` | Summarize the PR on the current branch | | `/pr-summary <number>` | Summarize a specific PR by number | ## Process ### 1. Fetch PR Data Determine the GitHub account from the git remote using [`standards/github-accounts.md`](../../standards/github-accounts.md). ```bash GH_TOKEN=$(gh auth token --user <account>) gh pr view <number> --json title,body,files,additions,deletions,commits,labels,baseRefName,headRefName,author,reviewRequests ``` If no number is given, detect the current branch and find its PR: ```bash …
Read the whole file at its exact version.
How to install
mdr add gufranco/claude-engineering-rules/pr-summary@sha256:15e2c4b1f5d8f6f7The line at the top of this page pins the label git:20261028.383f696, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_gq7ksd34f7towo6g)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between May 21, 2026 and Oct 28, 2026, about one every 40 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.383f696 latest | 2026-10-28 | 383f696 | 8,943 B | A | view · diff |
| git:20261013.7233f74 | 2026-10-13 | 7233f74 | 8,800 B | A | view · diff |
| git:20261012.d086513 | 2026-10-12 | d086513 | 8,165 B | A | view · diff |
| git:20260522.a91f384 | 2026-05-22 | a91f384 | 5,055 B | A | view · diff |
| git:20260521.81b3d41 | 2026-05-21 | 81b3d41 | 5,037 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8943 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gufranco/claude-engineering-rules · 3 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gq7ksd34f7towo6g GET https://markdownregistry.com/api/v1/resolve?ref=gufranco/claude-engineering-rules/pr-summary GET https://markdownregistry.com/api/v1/blob/15e2c4b1f5d8f6f73f2baca3e248b6b6bd5963499ac79d6d020f69006681099c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from gufranco/claude-engineering-rules
Every file in gufranco/claude-engineering-rules