release-notes
/release-notes
Generates Markdown release notes for the most recent release of a GitHub repository. Use when the user asks to "generate release notes", "write a changelog", or "summarize the last release" for a GitHub repo (owner/repo or full URL).
- Author
- dimagi ↗
- Repository
- dimagi-claude-workflows ↗
- Licence
- MIT
- Last repository change
- 06.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Generates Markdown release notes for the most recent release of a GitHub repository. Use when the user asks to "generate release notes", "write a changelog", or "summarize the last release" for a GitHub repo (owner/repo or full URL).
Triggers from the description
Original author description
Generates Markdown release notes for the most recent release of a GitHub repository. Use when the user asks to "generate release notes", "write a changelog", or "summarize the last release" for a GitHub repo (owner/repo or full URL).
How it works
- Inputs
- Terminology
- Step 1: Find the releases
- Step 2: Find merged PRs between the releases
- Step 3: Fetch PR details
- Step 4: Categorize and group
- Step 5: Write the release notes
- Step 6: Save the output
SKILL.md preview
---
name: release-notes
description: >
Generates Markdown release notes for the most recent release of a GitHub repository.
Use when the user asks to "generate release notes", "write a changelog", or "summarize
the last release" for a GitHub repo (owner/repo or full URL).
---
# Release Notes Skill
You are generating release notes for the most recent release of a GitHub repository. The goal is a clean, human-readable Markdown summary of what changed — the kind of thing you'd send to stakeholders or post in a changelog.
## Inputs
The user will provide a GitHub repo — either as a full URL (`https://github.com/owner/repo`) or an `owner/repo` string. Extract the `owner/repo` identifier from whatever they provide.
If the user specifies a product name to use in the title, use that. For the `dimagi/commcare-connect` repo, the product name is **"Connect"** (not "CommCare Connect").
## Terminology
When writing user-facing release notes, use the correct user-facing terms — not internal code names:
| Use this | Not this |
|---|---|
| PersonalID | ConnectID |
If you encounter other code-level identifiers in PR titles or bodies, use your judgment: if it reads like an internal variable name or database field rather than a product concept, rephrase it into plain language.
## Step 1: Find the releases
```bash
gh release list --repo <owner/repo> --limit 5
```
Identify the **latest release** (most recent) and the **previous release** (the one before it). Note the tag names and published dates of both.
## Step 2: Find merged PRs between the releases
Use the published dates of the two releases to filter merged PRs:
```bash
gh pr list \
--repo <owner/repo> \
--state merged \
--search "merged:YYYY-MM-DD..YYYY-MM-DD" \
--json number,title,author,mergedAt,labels \
--limit 100
```
Use the previous release date as the start and the latest release date as the end.
## Step 3: Fetch PR details
For each PR, fetch the title and body to understand what it does:
```bash
gh pr view <number> --repo <owner/repo> --json title,body,labels
```
Read the body — not just the title — to get the actual description of what changed. The first few sentences of the body (often under a "Product Description" or similar heading) are usually the most useful.
Batch these requests efficiently — there's no need to fetch one at a time if you can parallelize.
## Step 4: Categorize and group
Assign each PR one of these categories based on what it does:
- **`New`** — A brand-new feature or capability that didn't exist before
- **`Improvement`** — An enhancement, refinement, or extension of something existing
- **`Fix`** — A bug fix or correction
- **`Infra`** — Infrastructure, performance, configuration, or DevOps changes
- **`Docs`** — Documentation-only changes
Then group related PRs into logical **sections** by feature area (e.g., "Work Areas", "Notifications & Email", "Reporting"). If several PRs all touch the same feature, they belong in the same section. A section with only one item is fine. Don't force unrelated things together.
Skip PRs that are purely internal (e.g., dependency bumps, version bumps, CI config) unless they're meaningful to users.
## Step 5: Write the release notes
Use this format:
```markdown
# Release Notes — {Product Name} v{version}
*Released {date}*
---
## {Section Name}
**`New`** **Feature Title** — One or two sentence description of what changed and why it matters. [Screenshots](PR_URL)
**`Improvement`** **Feature Title** — Description.
---
## {Section Name}
**`Fix`** **Feature Title** — Description.
```
Guidelines:
- **Feature Title**: A short noun phrase describing the change (not the PR title verbatim — rephrase if needed to be user-facing).
- **Description**: Write for a non-technical stakeholder. What does the user now see or experience? Avoid implementation details unless they matter to the user. Keep it to one or two sentences.
- **Links**: If a PR has screenshots in its body, add `[Screenshots](PR_URL)`. If there are relevant Confluence/docs links you know about, add them too. Don't make up links.
- **Order**: Lead with the most impactful / user-visible sections. Bug fixes and infra go at the end.
## Step 6: Save the output
Save the file to `./outputs/release_notes_{version}.md`, creating the `outputs/` directory if it doesn't exist.
Then tell the user the file path where the notes were saved.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · dimagi/dimagi-claude-workflows | 100 | MIT |
| mono/SkiaSharp | 100 | MIT |
| niekcandaele/claude-helpers | 100 | MIT |
| kenryu42/cc-safety-net | 100 | MIT |
| zeitlos/lucity | 100 | AGPL-3.0 |
| openshift-pipelines/pipelines-as-code | 100 | Apache-2.0 |
| paperwingio/paperwing | 100 | Apache-2.0 |
| jelvodev/yaap | 100 | MIT |
| yearzen1/LocalSkillManager | 100 | MIT |
Database snapshot: 13.11.2026 · package version 7f64f0a5a08b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100connect-web-release-notes
Generates Markdown release notes for the latest commcare-connect release and posts them to Confluence and Slack. Use when the user asks for Connect release notes, a changelog, or what changed in the last release (no repo URL needed). - 100create-release-notes
Generate user-facing release notes when the user asks to write release notes, document a release, summarize changes for users, or prepare a changelog between versions - 100minutes-release-notes
Draft user-facing Minutes release notes for a version from the commit range, recent GitHub releases, and the repository release checks. Use when the user asks to write, generate, prepare, revise, or review release notes or a changelog for a Minutes version. - 100playwright-release-notes
Write the release notes for a Playwright release - the Node.js notes in docs/src/release-notes-js.md together with the Python, Java and .NET translations, and the GitHub markdown for each language's release. Use when asked to write, translate or publish release notes. - 100release-generate-release-notes
Generate Yaak release notes from git history and PR metadata, including feedback links and full changelog compare links. Use when asked to run or replace the old Claude generate-release-notes command. - 100release-notes-generator
Generates human-readable release notes from merged pull requests, commits, or changelogs between version references or date ranges. Groups changes by type (features, fixes, breaking changes), formats for multiple targets (repository releases, chat posts, wiki pages, plain…