release-notes
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.
What this skill does
# 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 Changes` section 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: ```bash 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 ``` 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: ```markdown ## [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: 1. **Conventional commit prefixes**: `feat:`, `fix:`, `docs:`, `chore:`, `BREAKING:` 2. **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](./README.md) for full configuration options and workflow setup instructions.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.