pr SKILL.md skillA
pr from stevepolitodesign/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add stevepolitodesign/skills/pr@git:20260925.20cc0ddPins git:20260925.20cc0dd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- stevepolitodesign/skills
- Path
pr/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260925.20cc0dd, committed Sep 25, 2026
- First version recorded
- Sep 25, 2026
- Size
- 5,788 bytes
- Repository stars
- 5
- License
- none declared
Open a pull request whose description you write yourself, with a suggested title and a light proofread.
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
# PR
The LLM wrote the commits. The user owns the feature, so the user writes the
description. The PR gets squash-merged, and its title and body become the one
commit that lands on main. So this is really writing a commit message, in the
user's words, that has to stand up in `git log` years from now.
Your job is everything around the words: title, proofreading, the mechanics of
opening it. The failure to avoid is drafting the description yourself. Even a
"starting point" anchors them to your version, and then it isn't theirs.
```
recon --> brief + title --> user writes --> proof --> sign-off --> open
^ |
+------ changes ---------+
```
## 1. Recon
Base branch is `$ARGUMENTS`, or the repo default (`gh repo view --json
defaultBranchRef`, falling back to `main`).
Read, don't ask:
- `git status`. Uncommitted changes or sitting on the base branch: stop and say
so. Committing and branching are other jobs.
- `git log <base>..HEAD` and `git diff <base>...HEAD --stat`. What the branch
does, so you can title it and later check their description against it.
…Read the whole file at its exact version.
How to install
mdr add stevepolitodesign/skills/pr@sha256:0b9fdfe6c8aebe19The line at the top of this page pins the label git:20260925.20cc0dd, 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_torwhktwj7uieayq)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Sep 25, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260925.20cc0dd latest | 2026-09-25 | 20cc0dd | 5,788 B | A | view · diff |
| git:20260925.8cf3b1f | 2026-09-25 | 8cf3b1f | 5,953 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 (5788 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
stevepolitodesign/skills · 5 stars · license none declared · pushed 2026-10-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_torwhktwj7uieayq GET https://markdownregistry.com/api/v1/resolve?ref=stevepolitodesign/skills/pr GET https://markdownregistry.com/api/v1/blob/0b9fdfe6c8aebe19fa5cd8bf793f01615af9c79ba0bfcad39087218fbe03d1df
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 stevepolitodesign/skills
Every file in stevepolitodesign/skills