How do I install the Create Release skill?

Run npx skillmds@latest add tomevault-io/create-release-5 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 Create Release safe to use?

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

Which AI agents work with Create 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 Create Release free to use?

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

Who published Create Release?

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

Create Release by tomevault-io — Agent Skill

Name: Create Release
Author: tomevault-io

Create Release

Cut a versioned NetMonitor-2.0 release. Creates a git tag, pushes it, which triggers the release.yml workflow to build both targets and publish a GitHub Release with auto-generated notes. Use when all P0/P1 bugs are fixed, tests pass, and the release prep checklist (NetMonitor-2.0-c0p) is complete. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Create a Release — NetMonitor-2.0

Prerequisites — complete the release prep checklist first

bd show NetMonitor-2.0-c0p    # View the release prep checklist

All items must be checked before tagging:

All blocking bugs fixed and verified
Full test suite passing (use check-coverage skill)
No P0 silent failures outstanding
Coverage meets all thresholds
Build succeeds with release scheme
Signing/provisioning verified
Release notes drafted (auto-generated, but review them)

Step 1 — Verify clean state

git status                   # Must show clean working tree
git log --oneline -5         # Confirm latest commits are as expected
swiftlint lint --quiet       # Must show 0 errors
swiftformat --lint .         # Must show 0 files need formatting

Step 2 — Bump version in project.yml

Version fields to update in project.yml:

# NetMonitor-macOS
CFBundleShortVersionString: "2.0"   # User-visible version (e.g. 2.0.1)
CFBundleVersion: "16"               # Build number — increment by 1 each release

# NetMonitor-iOS
CFBundleShortVersionString: "2.0"
CFBundleVersion: "2"

After editing project.yml:

xcodegen generate           # Regenerate .xcodeproj
git add project.yml NetMonitor-2.0.xcodeproj/
git commit -m "chore: bump version to 2.x.y (build N)"
git push

Step 3 — Create and push the tag

# Format: v{major}.{minor}.{patch}
git tag -a v2.0.0 -m "NetMonitor 2.0.0"
git push origin v2.0.0

This triggers .github/workflows/release.yml automatically.

Step 4 — Monitor the release workflow

gh run list --workflow=release.yml --limit 5
gh run view --log $(gh run list --workflow=release.yml --limit 1 --json databaseId --jq '.[0].databaseId')

Step 5 — Review and publish the GitHub Release

The workflow creates a draft release with auto-generated notes. Review it:

gh release view v2.0.0

If the notes look correct, publish:

gh release edit v2.0.0 --draft=false

Step 6 — Close the release prep issue

bd close NetMonitor-2.0-c0p
bd sync
git push

Version convention

v2.0.0 — major feature release
v2.0.1 — bug fix release
v2.1.0 — minor feature addition
Build number increments on every release regardless of semver

Source: jbcrane13/NetMonitor-2.0 — distributed by TomeVault.

---name: create-release-5description: Cut a versioned NetMonitor-2.0 release. Creates a git tag, pushes it, which triggers the release.yml workflow to build both targets and publish a GitHub Release with auto-generated notes. Use when all P0/P1 bugs are fixed, tests pass, and the release prep checklist (NetMonitor-2.0-c0p) is complete. Use when this capability is needed.---# Create a Release — NetMonitor-2.0## Prerequisites — complete the release prep checklist first```bashbd show NetMonitor-2.0-c0p # View the release prep checklist```All items must be checked before tagging:- All blocking bugs fixed and verified- Full test suite passing (use `check-coverage` skill)- No P0 silent failures outstanding- Coverage meets all thresholds- Build succeeds with release scheme- Signing/provisioning verified- Release notes drafted (auto-generated, but review them)## Step 1 — Verify clean state```bashgit status # Must show clean working treegit log --oneline -5 # Confirm latest commits are as expectedswiftlint lint --quiet # Must show 0 errorsswiftformat --lint . # Must show 0 files need formatting```## Step 2 — Bump version in project.ymlVersion fields to update in `project.yml`:```yaml# NetMonitor-macOSCFBundleShortVersionString: "2.0" # User-visible version (e.g. 2.0.1)CFBundleVersion: "16" # Build number — increment by 1 each release# NetMonitor-iOSCFBundleShortVersionString: "2.0"CFBundleVersion: "2"```After editing `project.yml`:```bashxcodegen generate # Regenerate .xcodeprojgit add project.yml NetMonitor-2.0.xcodeproj/git commit -m "chore: bump version to 2.x.y (build N)"git push```## Step 3 — Create and push the tag```bash# Format: v{major}.{minor}.{patch}git tag -a v2.0.0 -m "NetMonitor 2.0.0"git push origin v2.0.0```This triggers `.github/workflows/release.yml` automatically.## Step 4 — Monitor the release workflow```bashgh run list --workflow=release.yml --limit 5gh run view --log $(gh run list --workflow=release.yml --limit 1 --json databaseId --jq '.[0].databaseId')```## Step 5 — Review and publish the GitHub ReleaseThe workflow creates a draft release with auto-generated notes. Review it:```bashgh release view v2.0.0```If the notes look correct, publish:```bashgh release edit v2.0.0 --draft=false```## Step 6 — Close the release prep issue```bashbd close NetMonitor-2.0-c0pbd syncgit push```## Version convention- `v2.0.0` — major feature release- `v2.0.1` — bug fix release- `v2.1.0` — minor feature addition- Build number increments on every release regardless of semver---> Source: [jbcrane13/NetMonitor-2.0](https://github.com/jbcrane13/NetMonitor-2.0) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions