write-release-notes skillA
write-release-notes is agent-read markdown (skill) from tailcallhq/forgecode: Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes for a version (e.g. "write release notes for v1.32.0", "generate release notes for the latest release", "create changelog for v2.0")..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Write Release Notes Generate clear, informative, and enthusiastic release notes by pulling live data from GitHub and synthesizing every PR into a cohesive narrative. ## Workflow ### 1. Fetch Release Data Run the bundled script to pull the release metadata and all linked PR details in one shot: ```bash bash .forge/skills/write-release-notes/scripts/fetch-release-data.sh <version> [owner/repo] ``` - `<version>`: The release tag (e.g. `v1.32.0`) - `[owner/repo]`: Optional. Defaults to the current repo detected via `gh repo view`. The script outputs two sections: - `### RELEASE METADATA ###` — tag name, publish date, release name, raw body - `### PR DETAILS ###` — one JSON object per PR with: `number`, `title`, `body`, `labels`, `author`, `mergedAt`, `url` ### 2. Categorize Changes Group PRs by their conventional commit prefix or label: | Category | Prefixes / Labels | |---|---| | Features | `feat`, `type: feature` | | Bug Fixes | `fix`, `type: fix` | | Performance | `perf` | | Refactors | `refactor` | | Maintenance | `chore`, `docs`, `ci`, `build`, `deps` | Dependency bumps (e.g. Dependabot PRs) go into Maintenance. Skip PRs with `error: "not found"`. …
Read the whole file at its exact version.
How to install
mdr add tailcallhq/forgecode/write-release-notes@git:20260413.a1642f4mdr add tailcallhq/forgecode/write-release-notes@sha256:91f2ef1404710ac2Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_3gmb4gcp2jfzhd5x)
2 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260413.a1642f4 latest | 2026-04-13 | a1642f4 | 5,599 B | A | view · diff |
| git:20260330.3d4fd44 | 2026-03-30 | 3d4fd44 | 5,181 B | A | view · diff |
| git:20260320.a7316c1 | 2026-03-20 | a7316c1 | 5,018 B | A | view · diff |
| git:20260315.d684df9 | 2026-03-15 | d684df9 | 4,209 B | A | view · diff |
| git:20260312.6987017 | 2026-03-12 | 6987017 | 3,975 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 (5599 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
tailcallhq/forgecode · 7,637 stars · license Apache-2.0 · pushed 2026-09-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3gmb4gcp2jfzhd5x GET https://markdownregistry.com/api/v1/resolve?ref=tailcallhq/forgecode/write-release-notes GET https://markdownregistry.com/api/v1/blob/91f2ef1404710ac29e915361cfd65f7f35e46a3579d35700204c2779501a0b26
Your agent 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.