Release Notes
- 2 installs
- 134 repo stars
- Updated August 4, 2026
- openhands/extensions
This is a copy of release-notes by openhands - installs and ranking accrue to the original listing.
Helps with productivity & planning tasks.
About
release-notes is a Claude Code skill for productivity & planning. It helps solo builders move faster with AI-assisted development.
- release-notes
- Productivity & Planning
- AI-coding skill
Release Notes by the numbers
- 2 all-time installs (skills.sh)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/openhands/extensions --skill release-notesAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 134 |
| Last updated | August 4, 2026 |
| Repository | openhands/extensions ↗ |
What it does
Helps with productivity & planning tasks.
Files
Generate a changelog for all changes from the most recent release until now.
Steps
1. Find the most recent release tag using git tag --sort=-creatordate 2. Get commits and merged PRs since that tag 3. Look at previous releases in this repo to match their format and style 4. Categorize changes into sections: Breaking Changes, Added, Changed, Fixed, Notes 5. Focus on user-facing changes (features, important bug fixes, breaking changes) 6. Include PR links and contributor attribution
Output
Present the changelog in a markdown code block, ready to copy-paste into a GitHub release.
Read and follow the complete instructions in the SKILL.md file located in this skill's directory.
$ARGUMENTS
Releasenotes
Generate formatted changelogs from git history since the last release tag. Use when preparing release notes that categorize changes into breaking changes, features, fixes, and other sections.
Triggers
This skill is activated by the following keywords:
/releasenotes
Details
Generate a changelog for all changes from the most recent release until now.
Steps
1. Find the most recent release tag using git tag --sort=-creatordate 2. Get commits and merged PRs since that tag 3. Look at previous releases in this repo to match their format and style 4. Categorize changes into sections: Breaking Changes, Added, Changed, Fixed, Notes 5. Focus on user-facing changes (features, important bug fixes, breaking changes) 6. Include PR links and contributor attribution
Output
Present the changelog in a markdown code block, ready to copy-paste into a GitHub release.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k