Skip to content

πŸ™Œ OpenHands: AI-Driven Development

refactor: update skills to Agent Skills format (#13267)

jpelletier12d7362bf2621
diff --git a/.agents/skills/upcoming-release.md b/.agents/skills/upcoming-release.md
deleted file mode 100644
index b17a15785b..0000000000
--- a/.agents/skills/upcoming-release.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-name: upcoming-release
-description: Generate a concise summary of PRs included in the upcoming release.
-triggers:
-- /upcoming-release
----
-
-We want to know what is part of the upcoming release.
-
-To do this, you need two commit SHAs. One SHA is what is currently running. The second SHA is what is going to be
-released. The user must provide these. If the user does not provide these, ask the user to provide them before doing
-anything.
-
-Once you have received the two SHAs:
-1. Run the `.github/scripts/find_prs_between_commits.py` script from the repository root directory with the `--json` flag. The **first SHA** should be the older commit (current release), and the **second SHA** should be the newer commit (what's being released).
-2. Do not show PRs that are chores, dependency updates, adding logs, refactors.
-3. From the remaining PRs, split them into these categories:
- - Features
- - Bug fixes
- - Security/CVE fixes
- - Other
-4. The output should list the PRs under their category, including the PR number with a brief description of the PR.
diff --git a/.agents/skills/upcoming-release/SKILL.md b/.agents/skills/upcoming-release/SKILL.md
new file mode 100644
index 0000000000..c9c6fd00c7
--- /dev/null
+++ b/.agents/skills/upcoming-release/SKILL.md
@@ -0,0 +1,37 @@
+---
+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.