pr-description SKILL.md skillA
pr-description from alexisbalayre/claude-code-config is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add alexisbalayre/claude-code-config/pr-description@git:20261017.1456344Pins git:20261017.1456344 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- alexisbalayre/claude-code-config
- Path
.claude/skills/pr-description/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.1456344, committed Oct 17, 2026
- First version recorded
- Jul 11, 2026
- Size
- 9,871 bytes
- Repository stars
- 3
- License
- MIT
Write a PR title and description in this repo's house style, then create or update the PR via gh. Use when asked to draft or rewrite a PR title or body, to open a PR, or when another skill opens a PR. Assumes commits exist on the branch.
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
# Write a PR title and description
Use this template for writing the PR body:
```markdown
## Summary
<diagram, diff-sketch, or tree>
## Evidence
- **Before:** <screenshot/output/failing test run>
**After:** <screenshot/output/passing test run>
## Merge Danger
**Door:** <one-way or two-way>
<optional: description>
**Blast Radius:** <one-word description>
<optional: potential ramifications of merge>
Closes PROJ-XXXX. Part of PROJ-YYYY.
```
> **Setup:** the tracker steps use an issue-tracker MCP server (`mcp__linear-server__*` tool
> names are placeholders: swap them for your tracker's tools). The ticket prefix (`PROJ`) comes
> from `TRACKER_ISSUE_PREFIX` in `.env`. No tracker? Skip step 2 and drop the ticket id and the
> closing line everywhere.
## Sections
Skip all preambles and keep prose brief. Use the user's domain language from `docs/glossary.md`.
### Summary
Pick the smallest view that makes the key point clear.
- Show logic or an algorithm as pseudocode:
```text
on(save)
if content is unchanged
return cached result
write new content
return fresh result
```
- Show runtime control flow as a call tree:
```text
submitForm
createSession
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ktvd2jmcib4s7pua/5fa563c33e3c17917f16a7cd7a39a5c757b32b6dd79508e8510f774b641c733d.json
Then /plugin install pr-description@markdownregistry-ktvd2jmcib4s7pua in Claude Code. It installs git:20261017.1456344, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add alexisbalayre/claude-code-config/pr-description@sha256:5fa563c33e3c1791The line at the top of this page pins the label git:20261017.1456344, 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_ktvd2jmcib4s7pua)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in alexisbalayre/claude-code-config/pr-description since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of pr-description from somewhere else? Ask it: where did my pr-description come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between Jul 11, 2026 and Oct 17, 2026, about one every 33 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.1456344 latest | 2026-10-17 | 1456344 | 9,871 B | A | view · diff |
| git:20260917.e147a85 | 2026-09-17 | e147a85 | 9,809 B | A | view · diff |
| git:20260917.a589e3f | 2026-09-17 | a589e3f | 6,896 B | A | view · diff |
| git:20260711.4f85074 | 2026-07-11 | 4f85074 | 6,800 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/pr-description/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (9871 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
alexisbalayre/claude-code-config · 3 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ktvd2jmcib4s7pua GET https://markdownregistry.com/api/v1/resolve?ref=alexisbalayre/claude-code-config/pr-description GET https://markdownregistry.com/api/v1/blob/5fa563c33e3c17917f16a7cd7a39a5c757b32b6dd79508e8510f774b641c733d
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 alexisbalayre/claude-code-config
Every file in alexisbalayre/claude-code-config