ShellOpenHandsFree

upcoming-release

This skill should be used when the user asks to "generate release notes", "list upcoming release PRs", "summarize upcoming release", "/upcoming-release", or needs to know what changes are part of an upcoming release.

View on GitHub ↗</>github.com/OpenHands/OpenHands Yours? Claim it ↗

§ 01 — Stats

Stars73.2k

Forks9.3k

Prior1425

Quality—

Score—

§ 02 — Install

Get upcoming-release.

Free SKILL.md scraped from GitHub. Clone the repo or copy the file directly into your Claude Code skills directory.

One-line install · Claude Code

$npx versuz@latest install upcoming-release

Or clone the repo

$git clone https://github.com/OpenHands/OpenHands.git

Or copy the SKILL.md manually

$cp OpenHands/.agents/skills/upcoming-release/SKILL.md ~/.claude/skills/upcoming-release/SKILL.md

More Versuz picks

★ Featured$1.99

vz-bench-debug

Document

★ Featured$0.99

vz-scrape-runner

Web

Got something better ?Submit your skill — it enters tomorrow's cycle. No fee.

Submit yours →

§ 05 — Challenge

Think you can beat it?

$npx versuz challenge upcoming-release↵

Show SKILL.md content (~321 tokens)

---
name: upcoming-release
description: This skill should be used when the user asks to "generate release notes", "list upcoming release PRs", "summarize upcoming release", "/upcoming-release", or needs to know what changes are part of an upcoming release.
---

# Upcoming Release Summary

Generate a concise summary of PRs included in the upcoming release.

## Prerequisites

Two commit SHAs are required:
- **First SHA**: The older commit (current release)
- **Second SHA**: The newer commit (what's being released)

If the user does not provide both SHAs, ask for them before proceeding.

## Workflow

1. Run the script from the repository root with the `--json` flag:
   ```bash
   .github/scripts/find_prs_between_commits.py <older-sha> <newer-sha> --json
   ```

2. Filter out PRs that are:
   - Chores
   - Dependency updates
   - Adding logs
   - Refactors

3. Categorize the remaining PRs:
   - **Features** - New functionality
   - **Bug fixes** - Corrections to existing behavior
   - **Security/CVE fixes** - Security-related changes
   - **Other** - Everything else

4. Format the output with PRs listed under their category, including the PR number and a brief description.