github-release-pr-writer SKILL.md skillA
github-release-pr-writer from flc1125/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add flc1125/skills/github-release-pr-writer@git:20260727.1db491fPins git:20260727.1db491f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- flc1125/skills
- Path
skills/github-release-pr-writer/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260727.1db491f, committed Jul 27, 2026
- Size
- 6,604 bytes
- Repository stars
- 39
- License
- MIT
Draft or update GitHub release pull request descriptions from verified tags, commits, merged pull requests, and the release diff. Use when a PR prepares a version, aligns release metadata, promotes a prerelease, or needs a reviewer-focused release summary, exact change inventory, breaking-change section, or migration summary. Do not use for ordinary feature or bug-fix pull requests.
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
# GitHub Release PR Writer Write release pull request descriptions that help maintainers verify what will be released and why the release-preparation diff is correct. ## Operating Boundaries - Treat this skill as a specialized companion to a general PR workflow. Use the general PR skill for branch readiness, ordinary change descriptions, reviewers, and PR creation. - Default to a local Markdown draft. Do not create or update a GitHub pull request unless the user explicitly asks for that write. - Inspect URLs and GitHub state read-only when the user asks to review, assess, draft, or improve wording. - Separate release-preparation changes from the product history being released. - Use repository evidence instead of reconstructing a release solely from conversation memory, commit wording, or the files changed by the release PR. ## Workflow ### 1. Discover repository and release conventions Read applicable repository instructions, PR templates, release documentation, version manifests, and representative recent release pull requests. Identify: - repository and target PR - base and head branches and immutable SHAs - intended version and release channel …
Read the whole file at its exact version.
How to install
mdr add flc1125/skills/github-release-pr-writer@sha256:560c324bdc527ec2The line at the top of this page pins the label git:20260727.1db491f, 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_bqxd4rs56ainxg3b)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 27, 2026.
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 (6604 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
flc1125/skills · 39 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bqxd4rs56ainxg3b GET https://markdownregistry.com/api/v1/resolve?ref=flc1125/skills/github-release-pr-writer GET https://markdownregistry.com/api/v1/blob/560c324bdc527ec203360b129737c8af1c1333c9766194b6a0d002ae182213ca
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.