Agent skill

Publish Release

Publish a new LiteEdit release to GitHub — commit code, bump version, write changelog, create GitHub release, and update the landing page.

MITAuto-check passedDevelopment

Install Publish Release

skills CLI

$ npx skills add arietan/lite-edit --skill publish-release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install arietan/lite-edit publish-release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/arietan/lite-edit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/publish-release .claude/skills/publish-release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "publish-release" agent skill from https://github.com/arietan/lite-edit/tree/main/.cursor/skills/publish-release into .claude/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-release", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/arietan/lite-edit/tree/main/.cursor/skills/publish-release

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add arietan/lite-edit --skill publish-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install arietan/lite-edit publish-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/arietan/lite-edit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/publish-release .agents/skills/publish-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "publish-release" agent skill from https://github.com/arietan/lite-edit/tree/main/.cursor/skills/publish-release into .agents/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-release", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add arietan/lite-edit --skill publish-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install arietan/lite-edit publish-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/arietan/lite-edit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/publish-release .cursor/skills/publish-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "publish-release" agent skill from https://github.com/arietan/lite-edit/tree/main/.cursor/skills/publish-release into .cursor/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-release", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/arietan/lite-edit.git --path .cursor/skills/publish-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add arietan/lite-edit --skill publish-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install arietan/lite-edit publish-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/arietan/lite-edit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/publish-release .gemini/skills/publish-release && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "publish-release" agent skill from https://github.com/arietan/lite-edit/tree/main/.cursor/skills/publish-release into .gemini/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-release", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install arietan/lite-edit publish-release

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add arietan/lite-edit --skill publish-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/arietan/lite-edit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/publish-release .github/skills/publish-release && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "publish-release" agent skill from https://github.com/arietan/lite-edit/tree/main/.cursor/skills/publish-release into .github/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-release", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add arietan/lite-edit --skill publish-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install arietan/lite-edit publish-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/arietan/lite-edit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/publish-release .opencode/skills/publish-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "publish-release" agent skill from https://github.com/arietan/lite-edit/tree/main/.cursor/skills/publish-release into .opencode/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-release", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: publish-release
GitHub stars: 167
Token cost: ~656 tokens
SKILL.md length: 239 words
Files: 1
Skills in repo: 1
Repo updated: Apr 23, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Publish a new LiteEdit release to GitHub — commit code, bump version, write changelog, create GitHub release, and update the landing page.

Works in 8 steps: Commit outstanding changes → Determine the version → Tag and push → …
The user says publish
SKILL.md covers Prerequisites and Workflow
Calls git, gh and swift

What it does

Publish Release is an agent skill from arietan/lite-edit. 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.

Its SKILL.md is about 660 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Landing pages and Changelog and release notes. It works with GitHub. The repository describes itself as: A lightweight, fast code editor for macOS — built with Swift and AppKit. The licence is MIT.

When your agent uses it

The user says publish
Deploy a new version

Example prompts

“/publish-release”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Commit outstanding changes
Determine the version
Tag and push
Write release notes
Create GitHub release
Update landing page (docs/index.html)
Update MEMORY.md
Build locally

What it can do on your machine

Read from SKILL.md and the folder at commit 0787bd0. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- gh
- swift
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Publish Release loads about 656 tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 239 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~57
When it runs · the whole SKILL.md, loaded when a task matches: ~656

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from arietan/lite-edit at commit 0787bd0, republished under its MIT licence (© arietan). 239 words, ~656 tokens.

Download SKILL.mdSave it as .claude/skills/publish-release/SKILL.md (or your agent's skills folder).

name: publish-release
description: 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.

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

bash

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

bash

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

bash

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

bash

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:

bash

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:

bash

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.

Files

Just SKILL.md in .cursor/skills/publish-release of arietan/lite-edit.

Open the folder on GitHubat commit 0787bd0

Compare with similar skills

Publish Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Publish Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Publish Release this skillarietan/lite-edit	167	—	~656	Automated safety check: Pass	MIT	5 mo ago
Shipluongnv89/skills	131	—	~3.3k	Automated safety check: Pass	MIT	yesterday
ReleaseLanternOps/breeze	132	—	~9.8k	Automated safety check: Notes	AGPL-3.0	today
Dev Releasealecs5am/ralphy	138	—	~757	Automated safety check: Pass	Apache-2.0	17 days ago
Suede Launch PackagingJasonColapietro/suede-creator-skills	127	—	~2.4k	Automated safety check: Pass	MIT	today
Releaseselfishprimate/gerillass	171	—	~2.9k	Automated safety check: Pass	Custom licence	10 days ago

Similar skills

Ship
luongnv89/skills
Run a release end to end, autonomous by default: version bump everywhere, changelog, docs, landing page, tag, push, GitHub release, PyPI/npm.
131 GitHub stars~3.3k tokensUpdated yesterday
DevelopmentAuto-check passed
Release
LanternOps/breeze
A skill your agent uses when cutting, shipping, or announcing a Breeze RMM release — "cut a release", "ship vX.Y.Z", "release notes for X", "what do self-hosters need to know", "draft the release…
132 GitHub stars~9.8k tokensUpdated today
DevelopmentAuto-check: notes
Dev Release
alecs5am/ralphy
Cut a Ralphy CLI release across GitHub Releases, Homebrew, and npm.
138 GitHub stars~757 tokensUpdated 17 days ago
DevelopmentAuto-check passed
Suede Launch Packaging
JasonColapietro/suede-creator-skills
Suede-owned launch packaging and install verification. An agent skill from JasonColapietro/suede-creator-skills.
127 GitHub stars~2.4k tokensUpdated today
DevelopmentAuto-check passed
Release
selfishprimate/gerillass
Cut and publish a Gerillass release — version bump, changelog, tag, GitHub release, npm publish, and post-publish verification.
171 GitHub stars~2.9k tokensUpdated 10 days ago
DevelopmentAuto-check passed
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
38k GitHub stars~3.2k tokensUpdated today
DevelopmentAuto-check passed

Works with

GitHub

Questions about Publish Release

What does Publish Release do?

Publish a new LiteEdit release to GitHub — commit code, bump version, write changelog, create GitHub release, and update the landing page. Publish Release is an agent skill from arietan/lite-edit. Publish a new LiteEdit release to GitHub — commit code, bump version, write changelog, create GitHub release, and update the landing page.

When should I use Publish Release?

Publish Release fits situations like: the user says publish; deploy a new version.

How do I install Publish Release in Claude Code?

Run `npx skills add arietan/lite-edit --skill publish-release -a claude-code`. Or copy the skill folder (.cursor/skills/publish-release in arietan/lite-edit) into .claude/skills/publish-release in your project. Claude Code loads it when a task matches its description.

How do I install Publish Release in Codex?

Run `npx skills add arietan/lite-edit --skill publish-release -a codex`. Or copy the skill folder (.cursor/skills/publish-release in arietan/lite-edit) into .agents/skills/publish-release in your project. Codex loads it when a task matches its description.

Can I use Publish Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add arietan/lite-edit --skill publish-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/publish-release, .gemini/skills/publish-release, .github/skills/publish-release and .opencode/skills/publish-release in your project.

What does Publish Release need to run?

Going by SKILL.md and its folder, Publish Release needs the command-line tools its instructions call (git, gh and swift).

Does Publish Release access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Publish Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Publish Release use?

Publish Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Publish Release use?

About 656 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Publish Release?

Skills that share tags, products or a category with Publish Release: Ship (luongnv89/skills, 131 stars), Release (LanternOps/breeze, 132 stars), Dev Release (alecs5am/ralphy, 138 stars) and Suede Launch Packaging (JasonColapietro/suede-creator-skills, 127 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Publish Release?

arietan (a GitHub user) maintains it in arietan/lite-edit, which has 167 GitHub stars. The repository was last updated on April 23, 2026.

Source: arietan/lite-edit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Publish Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Publish LiteEdit Release

Prerequisites

Workflow

Step 1 — Commit outstanding changes

Step 2 — Determine the version

Step 3 — Tag and push

Step 4 — Write release notes

Step 5 — Create GitHub release

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

Step 7 — Update MEMORY.md

Step 8 — Build locally

Files

Compare with similar skills

Similar skills

Ship

Release

Dev Release

Suede Launch Packaging

Release

Cutting A Release

Related

Questions about Publish Release

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