dasdae/draft-release
.agents/skills/draft-release/SKILL.md
Draft the next release version and changelog by fetching tags, computing the next semantic v* tag, collecting merged PRs into master since last release via gh, and printing the proposed version and categorized changelog.
$ install --global
skillsauthnpx skillsauth add dasdae/dascore draft-releaseInstall 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: Apr 14, 2026, 3:18 AM33.7s1 file scanned
SKILL.md
- name:
- draft-release
- description:
- Draft the next release version and changelog by fetching tags, computing the next semantic v* tag, collecting merged PRs into master since last release via gh, and printing the proposed version and categorized changelog.
draft-release
Draft the next release version and changelog from merged PRs.
Inputs
release_type(optional):major,minor,patch, orbugfix.- If omitted, default to
bugfix(patchandbugfixare equivalent).
Workflow
- Ask for elevated permissions with network access to run
git fetch --all --tagsand the GitHub CLI PR commands used to collect merged PRs (for examplegh pr list,gh pr view, orgh api). - Fetch the latest refs and tags:
git fetch --all --tags
- Determine the next version number:
- Consider only tags that start with
vand match strict semver:^v[0-9]+\.[0-9]+\.[0-9]+$(ignore pre-release/build suffixes). - Find the latest existing release tag from that set (e.g.,
v1.2.3). - If no matching tags exist, use
v0.0.0as the base. - Bump according to
release_type:major:X+1.0.0minor:X.Y+1.0patch/bugfix(default):X.Y.Z+1
- Output the computed new tag as
vX.Y.Z.
- Collect merged PRs since the last release:
- Use the previous release tag identified in step 2 as the lower bound.
- Define PR scope as changes reachable in
last_release_tag..origin/master(or..origin/<default_branch>if default branch is notmaster). - Use GitHub CLI (
gh) to read merged PRs for that scope. - Include at minimum PR number, title, merge date, URL, labels, and body text.
- Look at the git diffs to extract additional info if needed.
- Draft a changelog with these sections:
New FeaturesBug FixesBreaking Changes
- Classify PRs deterministically:
Breaking Changesif any of:- title contains
!in conventional-commit style segment, or - label indicates breaking change (e.g.,
breaking), or - body contains
BREAKING CHANGE.
- title contains
- Otherwise
New Featuresif labels/titles indicate feature work (e.g.,feature,enhancement,feat). - Otherwise
Bug Fixes. - Sort entries by PR number ascending.
- Include a link to the PR in the changelog.
- Print to screen:
- The new version tag.
- The drafted changelog.
Output Format
Next Version: vX.Y.Z
## New Features
- #123: Short summary (https://github.com/OWNER/REPO/pull/123)
## Bug Fixes
- #124: Short summary (https://github.com/OWNER/REPO/pull/124)
## Breaking Changes
- #125: Short summary (https://github.com/OWNER/REPO/pull/125)
Notes
- If there are no items for a section, include the section with
- None. - Prefer explicit, user-facing PR summaries over internal implementation details.
- If no merged PRs are found in scope, still print the next version and include
all sections with
- None.
Related Skills
dasdae/start-task
tools
VerifiedTrustedCommunity
Instructions for working on a task in this repo.
143SKILL.mdUpdated Apr 14, 2026
openclaw/openclaw-secret-scanning-maintainer
development
VerifiedTrustedCommunity
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
357,764SKILL.mdUpdated Apr 15, 2026
openclaw/openclaw-release-maintainer
development
VerifiedTrustedCommunity
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
357,764SKILL.mdUpdated Apr 10, 2026
openclaw/openclaw-qa-testing
development
VerifiedTrustedCommunity
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
357,764SKILL.mdUpdated Apr 10, 2026