jezweb/claude-skills / plugins/dev-tools/skills/github-release
github-release
VerifiedPrepare and publish GitHub releases. Sanitizes code for public release (secrets scan, personal artifacts, LICENSE/README validation), creates version tags, and publishes via gh CLI. Trigger with 'release', 'publish', 'open source', 'prepare for release', 'create release', or 'github release'.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.7 KB |
| references/release-workflow.md | markdown | 1.8 KB |
| references/safety-checklist.md | markdown | 1.8 KB |
references/release-workflow.md
View on GitHub# Release Workflow
Detailed reference for the tag-push-release mechanics.
## Version Detection
Check `package.json` first:
```bash
node -p "require('./package.json').version" 2>/dev/null
```
If no package.json, ask user for version. Always prefix with `v` (e.g., `v1.0.0`).
## Monorepo Tags
In monorepos, use scoped tags:
```bash
# Single repo
git tag -a v1.0.0 -m "Release v1.0.0"
# Monorepo
git tag -a mypackage-v1.0.0 -m "Release mypackage v1.0.0"
```
## Tag Conflicts
If tag already exists locally:
```bash
# Delete local tag
git tag -d v1.0.0
# If also on remote (dangerous — confirm with user)
git push origin :refs/tags/v1.0.0
```
## Push Sequence
Always push branch first, then tags:
```bash
BRANCH=$(git branch --show-current)
git push origin ${BRANCH}
git push origin --tags
```
If push fails:
- Set upstream: `git push -u origin ${BRANCH}`
- Check auth: `gh auth status`
- Verify remote: `git remote -v`
## Release Notes
Generate from commits since last tag:
```bash
LAST_TAG=$(git describe --tags --abbrev=0 HEAD^ 2>/dev/null || echo "")
if [ -z "$LAST_TAG" ]; then
git log --oneline --no-merges HEAD
else
git log --oneline --no-merges ${LAST_TAG}..HEAD
fi
```
Format as markdown bullet list under `## What's New`.
## gh release create
```bash
# Standard release
gh release create v1.0.0 --title "Release v1.0.0" --notes "## What's New
- Feature A
- Bug fix B"
# Pre-release (beta/rc)
gh release create v1.0.0-beta.1 --title "v1.0.0 Beta 1" --notes "..." --prerelease
# Draft (not published)
gh release create v1.0.0 --title "Release v1.0.0" --notes "..." --draft
```
## Post-Release
Depending on project type:
- **npm package**: `npm publish`
- **Announce**: Social media, relevant communities
- **Update docs**: Ensure README references latest version
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |