release-notes SKILL.md skillA
release-notes from kenryu42/cc-safety-net is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kenryu42/cc-safety-net/release-notes@git:20260820.8c6668dPins git:20260820.8c6668d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kenryu42/cc-safety-net
- Path
.claude/skills/release-notes/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260820.8c6668d, committed Aug 20, 2026
- Size
- 12,891 bytes
- Repository stars
- 1,877
- License
- MIT
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes `$release-notes` or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
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
# Release Notes Update only the body of the latest existing GitHub Release. Treat the repository diff as the source of truth. Use pull requests and commits only as supporting evidence. ## Safety rules - Use `gh` for all GitHub Release, pull request, issue, and API operations. Use `git fetch` only when required tag objects or history are missing. - Do not create or delete a release. - Do not change a tag, title, target, draft state, prerelease state, latest-release state, or other release metadata. - Do not publish a draft. - Do not use a new release as a fallback when no release exists. - Do not infer release order from version text, semantic versions, or Git tag order. - Stop when required evidence is unavailable. Do not publish partial or speculative notes. - Treat the notes file as a full replacement for the current release body, not as text to append. ## 1. Verify prerequisites Run all checks from the repository that the user wants to release: 1. Confirm that the current directory is in a Git worktree: ```sh git rev-parse --is-inside-work-tree ``` 2. Confirm that `gh` is available: ```sh command -v gh ``` …
Read the whole file at its exact version.
How to install
mdr add kenryu42/cc-safety-net/release-notes@sha256:37f3181c7f9f1f66The line at the top of this page pins the label git:20260820.8c6668d, 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_tl66dzqmvrel6zuw)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 20, 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 (12891 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
kenryu42/cc-safety-net · 1,877 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tl66dzqmvrel6zuw GET https://markdownregistry.com/api/v1/resolve?ref=kenryu42/cc-safety-net/release-notes GET https://markdownregistry.com/api/v1/blob/37f3181c7f9f1f6641dddecd99b6e04a2d45d36ddcc77d7d251a1e7c9d6cfe3f
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 kenryu42/cc-safety-net
Every file in kenryu42/cc-safety-net