baijum/github-release
.cursor/skills/github-release/SKILL.md
Create a GitHub release with a version tag and auto-generated release notes. Does not build artifacts or upload to any store. Use when the user asks to tag a version, create a GitHub release, cut a release, or prepare release notes.
$ install --global
skillsauthnpx skillsauth add baijum/ukulele-companion github-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 17, 2026, 10:38 AM14.3s1 file scanned
SKILL.md
- name:
- github-release
- description:
- Create a GitHub release with a version tag and auto-generated release notes. Does not build artifacts or upload to any store. Use when the user asks to tag a version, create a GitHub release, cut a release, or prepare release notes.
GitHub Release
Create a version tag on main and a GitHub release with release notes summarizing changes since the previous tag.
Prerequisites
ghCLI authenticated (gh auth status)- Working tree is clean (
git statusshows no uncommitted changes) - You are on the
mainbranch and up to date with origin
Workflow
Step 1: Verify clean state
git status
git branch --show-current
Confirm the branch is main and there are no uncommitted changes. If the working tree is dirty, stop and ask the user to commit or stash first.
Step 2: Determine the next version
Read the latest existing tag:
git describe --tags --abbrev=0
The project uses semantic versioning (major.minor.patch) with a v prefix (e.g., v9.10.1).
If the user did not specify a version or release type, ask which type of release to create:
| Release type | What changes | Example |
|--------------|-------------|---------|
| Major | Bump major, reset minor and patch to 0 | 9.10.1 -> 10.0.0 |
| Feature | Bump minor, reset patch to 0 | 9.10.1 -> 9.11.0 |
| Bugfix | Bump patch | 9.10.1 -> 9.10.2 |
Ask the user to confirm the new version before proceeding.
Step 3: Create and push the tag
Create an annotated tag on HEAD and push it:
git tag -a v<version> -m "v<version>"
git push origin v<version>
Step 4: Generate release notes
Review commits since the previous tag to build the release notes:
git log <previous-tag>..v<version> --oneline
Summarize the changes into categories (Add, Fix, Update, Refactor, etc.) matching the project's commit format.
Step 5: Create GitHub release
Use the gh CLI to create the release. Do not attach any binary files -- binaries are distributed through the Play Store and App Store.
gh release create v<version> \
--title "v<version>" \
--notes "$(cat <<'EOF'
## What's New
- <categorized summary of changes since last release>
EOF
)"
Step 6: Report to user
Provide:
- The new tag name (e.g.,
v9.11.0) - The GitHub release URL
- Reminder that platform releases (Android, iOS) can now be run using this tag
Related Skills
baijum/record-clips
tools
VerifiedTrustedCommunity
Record scene video clips for a TOML video project. Reads the android.toml or ios.toml to get the scene list and min_clip_duration, navigates to each screen via ADB (Android) or simctl (iOS), and records individual clips. Use when the user says /record-clips and provides a TOML path.
8SKILL.mdUpdated Apr 17, 2026
baijum/play-store-upload
tools
VerifiedTrustedCommunity
Upload a release AAB to Google Play Store using the Gradle Play Publisher plugin. Use when the user asks to upload to Play Store, publish to Google Play, deploy to internal testing, promote a release, or mentions Play Console.
8SKILL.mdUpdated Apr 17, 2026
baijum/play-store-promote
development
VerifiedTrustedCommunity
Promote a release from Google Play internal testing to a closed testing track (Alpha or App Hive Testing). Use when the user asks to promote a release, move to closed testing, push to alpha, push to App Hive Testing, or mentions track promotion.
8SKILL.mdUpdated Apr 17, 2026
baijum/play-store-promote-public
development
VerifiedTrustedCommunity
Promote a release to Google Play open testing or production tracks. Supports full rollout and staged rollout to production. Use when the user asks to promote to open testing, beta, go to production, release to all users, staged rollout, or increase rollout percentage.
8SKILL.mdUpdated Apr 17, 2026