drn/release
agents/skills/release/SKILL.md
Create a versioned release with changelog generation, git tag, and GitHub release. Use for creating releases, tagging versions, or publishing changelogs.
$ install --global
skillsauthnpx skillsauth add drn/dots 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 21, 2026, 10:56 AM49.6s1 file scanned
SKILL.md
- name:
- release
- allowed-tools:
- Bash(git tag:*), Bash(git log:*), Bash(git fetch:*), Bash(git diff:*), Bash(git status:*), Bash(git rev-parse:*), Bash(git symbolic-ref:*), Bash(gh release:*)
- description:
- Create a versioned release with changelog generation, git tag, and GitHub release. Use for creating releases, tagging versions, or publishing changelogs.
- disable-model-invocation:
- true
Release
Create a versioned release: bump version, generate changelog, create git tag, and publish a GitHub release.
Arguments
$ARGUMENTS- Required: version bump type (major,minor,patch) or an explicit version (e.g.,v2.1.0). Optional:--dry-runto preview without creating anything.
Context
- Current branch: !
git branch --show-current - Git status: !
git status --short - Latest tag: !
git describe --tags --abbrev=0 2>/dev/null | head -1 - Commits since last tag: !
git log --oneline 2>/dev/null | head -30 - Remotes: !
git remote -v 2>/dev/null | head -10 - Base ref: !
git branch -r 2>/dev/null | grep -oE 'origin/(main|master)' | head -1
Instructions
Step 0: Validate state
- IF
git status --shortshows uncommitted changes, stop: "Uncommitted changes detected. Commit or stash before releasing." - Determine the default branch using
git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null. Fallback to checking fororigin/main, thenorigin/master. - IF the current branch is not the default branch and does not match
release/*, warn: "You are on <branch>, not the default branch. Releases are typically made from <default>. Proceed anyway?" Wait for confirmation.
Step 1: Determine version
Parse $ARGUMENTS for the version:
- IF an explicit version is given (e.g.,
v2.1.0), use it directly. - IF a bump type is given (
major,minor,patch):- Parse the latest tag from context. IF no tags exist, start from
v0.0.0. - Apply the bump. Examples:
v1.2.3+ patch =v1.2.4, + minor =v1.3.0, + major =v2.0.0. - Preserve the tag prefix (if existing tags use
v, keepv; if bare numbers, use bare numbers).
- Parse the latest tag from context. IF no tags exist, start from
Report: "Version: <current> -> <new>"
Step 2: Generate changelog
Fetch commits since the last tag (or all commits if no prior tag):
git log <last-tag>..HEAD --format="%H%n%s%n%b%n---END---"
Categorize using the same approach as /changelog:
- Added — new features, commands, capabilities
- Changed — modifications to existing behavior
- Fixed — bug fixes
- Removed — deleted features, deprecated code
- Infrastructure — CI/CD, build, dependencies
- Documentation — docs, README
Write concise, meaningful entries. Deduplicate related commits. Skip trivial changes. Only include categories that have entries.
Step 3: Preview
Present the release preview:
## Release Preview: <new-version>
### Changelog
<categorized entries from Step 2>
### Tag
`<new-version>` on commit `<HEAD short hash>`
### GitHub Release
Title: <new-version>
Body: <changelog>
IF --dry-run is in $ARGUMENTS, stop here: "Dry run complete. No changes made."
Otherwise, ask for confirmation: "Create this release?"
Step 4: Create tag
git tag -a <new-version> -m "<new-version>
<changelog summary>"
Push the tag:
git push origin <new-version>
Step 5: Create GitHub release
gh release create <new-version> --title "<new-version>" --notes "<changelog>"
Step 6: Report
## Release Complete
**Version:** <new-version>
**Tag:** <new-version> on <commit hash>
**GitHub Release:** <URL from gh release create output>
**Changelog:** <N> entries across <M> categories
Related Skills
drn/address-comments
development
VerifiedTrustedCommunity
Walk every unresolved review thread on a PR, triage each one, reply with a rationale of whether or not the comment will be acted upon, make the code change if warranted, and mark the thread resolved. Use when the user asks to address only the open PR comments without re-running CI, respond to review feedback, resolve review threads, or clear bot comments on a PR.
23SKILL.mdUpdated May 16, 2026
drn/rereview-loop
tools
VerifiedTrustedCommunity
Iteratively run /rereview, fix the findings, and loop until reviewers approve clean. Use for iterative automated review, when you want /rereview to loop until clean, or for a paranoid pre-merge review that auto-addresses every blocker.
23SKILL.mdUpdated May 13, 2026
drn/plannotator-visual-explainer
development
VerifiedTrustedCommunity
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
23SKILL.mdUpdated May 13, 2026
drn/plannotator-setup-goal
development
VerifiedTrustedCommunity
Create reviewed Codex goal setup packages for long-running /goal work. Use when the user wants to turn an idea, backlog, project mission, or vague objective into durable goal files under a project goals slug folder, with Plannotator review gates for brief, narrative plan with acceptance criteria, verification, blockers, and the final /goal prompt.
23SKILL.mdUpdated May 13, 2026