How do I install the Github Release skill?

Run npx skillmds@latest add majiayu000/github-release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Release safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Release?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Release by majiayu000 — Agent Skill

Name: Github Release
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

GitHub Release

Create GitHub release with formatted notes from commits since last tag.

Prereqs: gh authenticated, existing tags in repo

Workflow

Get commits since latest tag (run as separate commands):

# First: get latest tag
git tag --sort=-v:refname | head -1

# Then: get commits since that tag (replace <TAG> with result above)
git log <TAG>..HEAD --pretty=format:"%h %s%n%b---" --no-merges

Bump version if needed:
- Check if version in decentpaste-app/src-tauri/tauri.conf.json matches latest tag
- If yes, run /bump-version skill first
- If already bumped, continue
Categorize by conventional commit prefix:

Prefix Section

feat: Features & Improvements

fix: Bug Fixes

chore:, docs:, refactor:, perf:, style:, test: Under the Hood

Prefix	Section
`feat:`	Features & Improvements
`fix:`	Bug Fixes
`chore:`, `docs:`, `refactor:`, `perf:`, `style:`, `test:`	Under the Hood

Generate notes (omit empty sections):

## What's New in vX.X.X

[1-2 sentence summary]

### Features & Improvements
- **Feature** - Description

### Bug Fixes
- **Fix** - Description

### Under the Hood
- **Change** - Description

### Downloads

| Platform | Download |
|----------|----------|
| Windows | `DecentPaste_X.X.X_x64-setup.exe` |
| macOS (Intel) | `DecentPaste_X.X.X_x64.dmg` |
| macOS (Apple Silicon) | `DecentPaste_X.X.X_aarch64.dmg` |
| Linux (Debian/Ubuntu) | `DecentPaste_X.X.X_amd64.deb` |
| Linux (AppImage) | `DecentPaste_X.X.X_amd64.AppImage` |
| Android | `DecentPaste_X.X.X.apk` |

---
**Full Changelog**: https://github.com/decentpaste/decentpaste/compare/<prev-tag>...v<version>

Confirm with user: show version, tag, commit count, notes preview
Commit and push version bump (CRITICAL - must happen before creating release!):
```
git add -A && git commit -m "chore: bump version to X.X.X"
git push
```
⚠️ CI/CD builds from the pushed code. If you create the release before pushing, CI will build the old version!

Create release:

gh release create vX.X.X --title "DecentPaste vX.X.X" --notes "$(cat <<'EOF'
<notes>
EOF
)"

Done: Show release URL, CI will automatically build and upload artifacts

---name: github-releasedescription: Create a GitHub release with auto-generated release notes from commits since the last tag. Uses conventional commits to categorize changes into Features, Bug Fixes, and maintenance sections.--- # GitHub Release Create GitHub release with formatted notes from commits since last tag. **Prereqs**: `gh` authenticated, existing tags in repo ## Workflow 1. **Get commits** since latest tag (run as separate commands): ```bash # First: get latest tag git tag --sort=-v:refname | head -1 ``` ```bash # Then: get commits since that tag (replace <TAG> with result above) git log <TAG>..HEAD --pretty=format:"%h %s%n%b---" --no-merges ``` 2. **Bump version** if needed: - Check if version in `decentpaste-app/src-tauri/tauri.conf.json` matches latest tag - If yes, run `/bump-version` skill first - If already bumped, continue 3. **Categorize** by conventional commit prefix: | Prefix | Section | |--------|---------| | `feat:` | Features & Improvements | | `fix:` | Bug Fixes | | `chore:`, `docs:`, `refactor:`, `perf:`, `style:`, `test:` | Under the Hood | 4. **Generate notes** (omit empty sections): ```markdown ## What's New in vX.X.X [1-2 sentence summary] ### Features & Improvements - **Feature** - Description ### Bug Fixes - **Fix** - Description ### Under the Hood - **Change** - Description ### Downloads | Platform | Download | |----------|----------| | Windows | `DecentPaste_X.X.X_x64-setup.exe` | | macOS (Intel) | `DecentPaste_X.X.X_x64.dmg` | | macOS (Apple Silicon) | `DecentPaste_X.X.X_aarch64.dmg` | | Linux (Debian/Ubuntu) | `DecentPaste_X.X.X_amd64.deb` | | Linux (AppImage) | `DecentPaste_X.X.X_amd64.AppImage` | | Android | `DecentPaste_X.X.X.apk` | --- **Full Changelog**: https://github.com/decentpaste/decentpaste/compare/<prev-tag>...v<version> ``` 5. **Confirm** with user: show version, tag, commit count, notes preview 6. **Commit and push version bump** (CRITICAL - must happen before creating release!): ```bash git add -A && git commit -m "chore: bump version to X.X.X" git push ``` ⚠️ CI/CD builds from the pushed code. If you create the release before pushing, CI will build the old version! 7. **Create release**: ```bash gh release create vX.X.X --title "DecentPaste vX.X.X" --notes "$(cat <<'EOF' <notes> EOF )" ``` 8. **Done**: Show release URL, CI will automatically build and upload artifacts

Frequently asked questions

Github Release