openhands/release-notes
plugins/release-notes/SKILL.md
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v*.*.*) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
$ install --global
skillsauthnpx skillsauth add openhands/extensions release-notesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 2, 2026, 6:24 AM135.5s9 files scanned
SKILL.md
- name:
- release-notes
- description:
- Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v*.*.*) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
Release Notes Generator Plugin
Automates the generation of standardized release notes for OpenHands repositories using an OpenHands agent. The agent reviews the release range, judges significance, groups related PRs, and produces concise markdown for GitHub releases or changelogs.
Features
- Automatic tag detection: Finds the previous release tag to determine the commit range
- Agent-based editing: Lets the agent decide which changes matter, open with a short conversational summary, and group related PRs into higher-signal summaries while keeping toolkit-maintainer-only details out of the main sections unless they are unusually significant
- Structured GitHub context: Supplies PR titles, labels, descriptions, and contributor metadata to guide the agent
- Contributor attribution: Includes PR numbers and author usernames for each change
- Attribution validation: Verifies every change bullet contains explicit PR/commit references and the matching author handles
- Full coverage appendix: Appends a compact
### 🔎 Small Fixes/Internal Changessection grouped by author when needed so every PR and author in the release range is still listed somewhere in the final markdown - New contributor highlighting: Identifies first-time human contributors from merged PR history and excludes bot accounts
- Flexible output: Can update GitHub release notes or generate CHANGELOG.md entries
Quick Start
As a GitHub Action
Copy the workflow file to your repository:
mkdir -p .github/workflows
curl -o .github/workflows/release-notes.yml \
https://raw.githubusercontent.com/OpenHands/extensions/main/plugins/release-notes/workflows/release-notes.yml
PowerShell equivalent:
New-Item -ItemType Directory -Force .github\workflows | Out-Null
Invoke-WebRequest `
-Uri https://raw.githubusercontent.com/OpenHands/extensions/main/plugins/release-notes/workflows/release-notes.yml `
-OutFile .github\workflows\release-notes.yml
Configure required secrets (see the README for details).
Manual Invocation
Use the /release-notes trigger in an OpenHands conversation to generate release notes for the current repository.
Release Notes Format
Generated release notes follow this structure:
## [v1.2.0] - 2026-03-06
### ⚠️ Breaking Changes
- Remove deprecated `--legacy` CLI flag (#456) @maintainer
### ✨ New Features
- Add support for Claude Sonnet 4.6 model (#445) @contributor1
### 🐛 Bug Fixes
- Fix WebSocket reconnection on network interruption (#451) @contributor3
### 📚 Documentation
- Update installation guide (#442) @contributor2
### 👥 New Contributors
- @contributor3 made their first contribution in #451
**Full Changelog**: https://github.com/org/repo/compare/v1.1.0...v1.2.0
Change Categorization
Changes are categorized based on:
- Conventional commit prefixes:
feat:,fix:,docs:,chore:,BREAKING: - PR labels:
breaking-change,bug,enhancement,documentation
| Category | Commit Prefixes | PR Labels |
|----------|-----------------|-----------|
| Breaking Changes | BREAKING:, !: suffix | breaking-change, breaking |
| Features | feat:, feature: | enhancement, feature |
| Bug Fixes | fix:, bugfix: | bug, bugfix |
| Documentation | docs: | documentation, docs |
| Internal | chore:, ci:, refactor:, test: | internal, chore, ci |
Configuration
See the README for full configuration options and workflow setup instructions.
Related Skills
openhands/iterate
tools
VerifiedTrustedCommunity
Iterate on a GitHub pull request — drive it through CI, code review, and QA until it is merge-ready. Poll verification layers with `gh` CLI, diagnose and fix CI failures, address review feedback, retry flaky checks, push fixes, and repeat. The agent is the orchestration loop.
125SKILL.mdUpdated Apr 18, 2026
openhands/technical-writing
development
VerifiedTrustedCommunity
Guides technical explanations toward flowing, direct, conversational prose. This skill should be used for engineering chat, design discussion, architecture analysis, code-review explanations, and technical recommendations that should be concise without becoming fragmented or vague.
124SKILL.mdUpdated Jul 13, 2026
openhands/jira-issue-to-pr
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "set up a Jira automation to create pull requests", "poll Jira for create-pr issues", "automatically create GitHub PRs from Jira tickets", "deploy a Jira issue-to-PR automation", "create a Jira to GitHub PR workflow", or mentions automating GitHub PR creation from a Jira label. Deploys a cron-based OpenHands automation that watches a Jira Cloud project for issues labeled with a configurable label (default: "create-pr") and spawns an agent conversation to create a GitHub pull request for each new issue found. The target GitHub repository is read from the body of the Jira ticket - no repo parameter is required at deploy time.
123SKILL.mdUpdated Jul 7, 2026
openhands/openhands-automation
tools
VerifiedTrustedCommunity
This skill should be used when the user asks to "create an automation", "schedule a task", "set up a cron job", "webhook integration", "event-triggered automation", or mentions automations, scheduled tasks, cron scheduling, or webhook events in OpenHands Cloud.
123SKILL.mdUpdated Apr 24, 2026