changelog-from-prs
Skill1 starsChanged 5 days agoMITView on GitHub
Draft a release changelog by summarizing merged pull requests since the last tag. Use when preparing a release or writing release notes.
In this repository163 other files it gives its agents.
- agents.mdAGENTS.md
- 3d-asset-handoff-sheetSkill
- accessibility-regression-auditorSkill
- adr-writerSkill
- agent-memory-designerSkill
- agent-trajectory-evaluatorSkill
- alerting-rules-tunerSkill
- analysis-memo-writerSkill
- annotation-disagreement-ledgerSkill
- annotation-task-spec-builderSkill
- api-deprecation-plannerSkill
- api-error-contract-designerSkill
- architecture-diagram-generatorSkill
- asset-metadata-review-ledgerSkill
- auth-flow-reviewerSkill
- background-job-reliability-auditorSkill
- branch-rebaserSkill
- brand-voice-profilerSkill
- bundle-analyzerSkill
- cache-policy-designerSkill
- canary-release-plannerSkill
- caption-correction-ledgerSkill
- chart-chooserSkill
- chunking-strategy-optimizerSkill
- circular-dependency-breakerSkill
- claude-settings-auditorSkill
- code-example-verifierSkill
- cold-email-deliverability-auditorSkill
- cold-start-optimizerSkill
- commit-splitterSkill
- competitor-teardownSkill
- component-spec-writerSkill
- connection-pool-tunerSkill
- content-repurposerSkill
- contract-obligation-registerSkill
- contract-test-designerSkill
- conventional-commitsSkill
- cors-configuratorSkill
- coverage-gap-finderSkill
- crm-export-auditorSkill
- dashboard-designerSkill
- data-retention-auditorSkill
- dataset-first-lookSkill
- dead-code-finderSkill
- deadlock-diagnoserSkill
- decision-log-reconcilerSkill
- dependency-auditSkill
- dependency-upgrade-plannerSkill
- design-brief-writerSkill
- design-critique-checklistSkill
- design-token-extractorSkill
- devcontainer-designerSkill
- distributed-tracing-instrumenterSkill
- dockerfile-optimizerSkill
- email-sequence-drafterSkill
- embedding-index-tunerSkill
- embedding-set-inspectorSkill
- entity-match-candidate-ledgerSkill
- exit-ticket-builderSkill
- extract-moduleSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Find the last release tag: Use the most recent semantic-version tag as the lower bound.
- Distinctive: line 27
Collect merged PRs in the range: Prefer the GitHub CLI so you get titles, numbers, authors, and labels.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Turn a range of merged pull requests into a clean, human-readable changelog. This skill collects the PRs merged since the previous release tag, groups them by change type (features, fixes, breaking changes, and more), and drafts release notes that are accurate, scannable, and ready to paste into a GitHub release or CHANGELOG.md.
When to use this skill
- You are cutting a new release and need release notes that reflect what actually shipped.
- You want a first draft of a
CHANGELOG.mdentry that follows Keep a Changelog conventions. - You need to summarize a noisy list of merge commits into something a human reader can understand.
- You are reviewing what changed between two tags before deciding on a version bump.
[!NOTE] This skill drafts notes from real PR data. It does not push tags or publish releases. Always review the draft before publishing.
Instructions
Find the last release tag. Use the most recent semantic-version tag as the lower bound. If no tag exists, fall back to the first commit.
git describe --tags --abbrev=0Collect merged PRs in the range. Prefer the GitHub CLI so you get titles, numbers, authors, and labels. Use the merge date of the last tag as the cutoff.
LAST_TAG=$(git describe --tags --abbrev=0) SINCE=$(git log -1 --format=%cI "$LAST_TAG") gh pr list --state merged --base main --limit 200 \ --search "merged:>$SINCE" \ --json number,title,author,labels,mergedAt- Classify each PR. Map it to a changelog section using labels first, then the title prefix (Conventional Commits style), then a judgment call:
feat/enhancement-> Added or Changedfix/bug-> Fixedbreaking/!in the title -> Breaking Changes (call these out at the top)deprecate-> Deprecatedsecurity-> Securitydocs,chore,ci,test, dependency bumps -> omit unless user-facing.
- Rewrite titles into reader-facing notes. Drop the type prefix, use the imperative-to-past or noun phrasing the section expects, and explain the user impact rather than the implementation. Keep the PR number for traceability.
- Order and group. Lead with breaking changes, then Added, Changed, Deprecated, Removed, Fixed, Security. Within a section, order by importance, not PR number.
- Suggest the version bump. Breaking changes -> major; new features -> minor; fixes only -> patch. State the recommendation but let the user confirm.
- Emit the draft. Output Markdown ready to paste, with a version header and date. Note any PRs you could not confidently classify so the user can review them.
[!WARNING] Do not invent changes. If a PR title is ambiguous, list it under an "Uncategorized — needs review" heading instead of guessing its impact.
Examples
Input — three merged PRs since v1.3.0:
#142 feat: add --json output flag to export command (label: enhancement)
#147 fix: prevent crash when config file is empty (label: bug)
#151 feat!: rename `--token` to `--api-key` (label: breaking)Output — drafted changelog entry:
## v1.4.0 — 2026-06-02
### Breaking Changes
- Renamed the `--token` flag to `--api-key` for clarity. Update scripts that pass `--token`. (#151)
### Added
- `export` now supports a `--json` flag for machine-readable output. (#142)
### Fixed
- Fixed a crash that occurred when the config file was empty. (#147)
> Recommended bump: minor → major (contains a breaking change). Suggested version: v2.0.0.Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

