How do I install the Publish Release skill?

Run npx skillmds@latest add tomevault-io/publish-release-2 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 Publish 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 Publish 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 Publish Release free to use?

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

Who published Publish Release?

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

Publish Release by tomevault-io — Agent Skill

Name: Publish Release
Author: tomevault-io

Publish Release

Publish a new LiteEdit release to GitHub — commit code, bump version, write changelog, create GitHub release, and update the landing page. Use when the user says publish, release, ship, or deploy a new version. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Publish LiteEdit Release

Prerequisites

Working directory: project root of lite-edit
gh CLI authenticated (gh auth status)
All changes built and tested locally (per local-build.mdc rule)

Workflow

Step 1 — Commit outstanding changes

git status
git diff --stat

Stage and commit all modified source files with a descriptive message covering every change since the last tag. Use git log $(git describe --tags --abbrev=0)..HEAD --oneline to review what's new.

Step 2 — Determine the version

git tag --sort=-creatordate | head -5

Patch (v1.1.2 → v1.1.3): bug fixes only
Minor (v1.1.2 → v1.2.0): new features or enhancements
Major (v1.1.2 → v2.0.0): breaking changes

Ask only if ambiguous.

Step 3 — Tag and push

git tag vX.Y.Z
git push origin main --tags

Step 4 — Write release notes

Write notes to .release-notes.md using these sections (omit empty ones):

Editor Enhancements — new editing features
Bug Fixes — things that were broken and are now fixed
Performance — speed, memory, or responsiveness improvements
Landing Page & Community — docs, website, badges

End with: **Full Changelog**: https://github.com/arietan/lite-edit/compare/vOLD...vNEW

Step 5 — Create GitHub release

gh release create vX.Y.Z --title "vX.Y.Z" --notes-file .release-notes.md
rm .release-notes.md

Step 6 — Update landing page (`docs/index.html`)

Check what needs updating:

Features grid — add a card if a major capability was added
Shortcuts table — add rows for new keyboard shortcuts
Use Cases — update if the editor's scope expanded
Download links — use /releases/latest (auto-resolves, no version needed)

Commit and push landing page changes separately for a clean diff:

git add docs/index.html
git commit -m "Update landing page for vX.Y.Z"
git push origin main

Step 7 — Update MEMORY.md

Record the release version, date, and a one-line summary in Recent Changes.

Step 8 — Build locally

Per the local-build.mdc rule, always build and launch after everything is pushed:

swift build -c release 2>&1
ls -lh .build/release/LiteEdit | awk '{print $5}'
cp .build/release/LiteEdit LiteEdit.app/Contents/MacOS/LiteEdit
open LiteEdit.app

Binary must stay under 1 MB.

Source: arietan/lite-edit — distributed by TomeVault.

---name: publish-release-2description: Publish a new LiteEdit release to GitHub — commit code, bump version, write changelog, create GitHub release, and update the landing page. Use when the user says publish, release, ship, or deploy a new version. Use when this capability is needed.---# Publish LiteEdit Release## Prerequisites- Working directory: project root of lite-edit- `gh` CLI authenticated (`gh auth status`)- All changes built and tested locally (per `local-build.mdc` rule)## Workflow### Step 1 — Commit outstanding changes```bashgit statusgit diff --stat```Stage and commit all modified source files with a descriptive message covering every change since the last tag. Use `git log $(git describe --tags --abbrev=0)..HEAD --oneline` to review what's new.### Step 2 — Determine the version```bashgit tag --sort=-creatordate | head -5```- **Patch** (v1.1.2 → v1.1.3): bug fixes only- **Minor** (v1.1.2 → v1.2.0): new features or enhancements- **Major** (v1.1.2 → v2.0.0): breaking changesAsk only if ambiguous.### Step 3 — Tag and push```bashgit tag vX.Y.Zgit push origin main --tags```### Step 4 — Write release notesWrite notes to `.release-notes.md` using these sections (omit empty ones):- **Editor Enhancements** — new editing features- **Bug Fixes** — things that were broken and are now fixed- **Performance** — speed, memory, or responsiveness improvements- **Landing Page & Community** — docs, website, badgesEnd with: `**Full Changelog**: https://github.com/arietan/lite-edit/compare/vOLD...vNEW`### Step 5 — Create GitHub release```bashgh release create vX.Y.Z --title "vX.Y.Z" --notes-file .release-notes.mdrm .release-notes.md```### Step 6 — Update landing page (`docs/index.html`)Check what needs updating:- **Features grid** — add a card if a major capability was added- **Shortcuts table** — add rows for new keyboard shortcuts- **Use Cases** — update if the editor's scope expanded- **Download links** — use `/releases/latest` (auto-resolves, no version needed)Commit and push landing page changes **separately** for a clean diff:```bashgit add docs/index.htmlgit commit -m "Update landing page for vX.Y.Z"git push origin main```### Step 7 — Update MEMORY.mdRecord the release version, date, and a one-line summary in Recent Changes.### Step 8 — Build locallyPer the `local-build.mdc` rule, always build and launch after everything is pushed:```bashswift build -c release 2>&1ls -lh .build/release/LiteEdit | awk '{print $5}'cp .build/release/LiteEdit LiteEdit.app/Contents/MacOS/LiteEditopen LiteEdit.app```Binary must stay under 1 MB.---> Source: [arietan/lite-edit](https://github.com/arietan/lite-edit) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions