Agent skill

Release Sync

PromptHub release update skill. An agent skill from legeling/PromptHub.

AGPL-3.0Auto-check passedDevelopment

Install Release Sync

skills CLI

$ npx skills add legeling/PromptHub --skill release-sync -a claude-code

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

GitHub CLI

$ gh skill install legeling/PromptHub release-sync --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/legeling/PromptHub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-sync .claude/skills/release-sync && 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 "release-sync" agent skill from https://github.com/legeling/PromptHub/tree/main/.agents/skills/release-sync into .claude/skills/release-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-sync", 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/legeling/PromptHub/tree/main/.agents/skills/release-sync

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 legeling/PromptHub --skill release-sync -a codex

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

GitHub CLI

$ gh skill install legeling/PromptHub release-sync --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/legeling/PromptHub.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/release-sync .agents/skills/release-sync && 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 "release-sync" agent skill from https://github.com/legeling/PromptHub/tree/main/.agents/skills/release-sync into .agents/skills/release-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-sync", 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 legeling/PromptHub --skill release-sync -a cursor

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

GitHub CLI

$ gh skill install legeling/PromptHub release-sync --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/legeling/PromptHub.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/release-sync .cursor/skills/release-sync && 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 "release-sync" agent skill from https://github.com/legeling/PromptHub/tree/main/.agents/skills/release-sync into .cursor/skills/release-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-sync", 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/legeling/PromptHub.git --path .agents/skills/release-sync

--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 legeling/PromptHub --skill release-sync -a gemini-cli

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

GitHub CLI

$ gh skill install legeling/PromptHub release-sync --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/legeling/PromptHub.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/release-sync .gemini/skills/release-sync && 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 "release-sync" agent skill from https://github.com/legeling/PromptHub/tree/main/.agents/skills/release-sync into .gemini/skills/release-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-sync", 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 legeling/PromptHub release-sync

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 legeling/PromptHub --skill release-sync -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/legeling/PromptHub.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/release-sync .github/skills/release-sync && 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 "release-sync" agent skill from https://github.com/legeling/PromptHub/tree/main/.agents/skills/release-sync into .github/skills/release-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-sync", 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 legeling/PromptHub --skill release-sync -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 legeling/PromptHub release-sync --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/legeling/PromptHub.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/release-sync .opencode/skills/release-sync && 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 "release-sync" agent skill from https://github.com/legeling/PromptHub/tree/main/.agents/skills/release-sync into .opencode/skills/release-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-sync", 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: release-sync
GitHub stars: 1.7k
Token cost: ~978 tokens
SKILL.md length: 403 words
Files: 1
Skills in repo: 2
Repo updated: Sep 28, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

PromptHub release update skill. An agent skill from legeling/PromptHub.

Works in 4 steps: AGENTS.md → spec/releases/release-rules.md → spec/releases/README.md and the target… → …
Changelog updates
SKILL.md covers Read First, Establish Scope, Source And Sync Order and Release Semantics, plus 2 more sections
Calls pnpm

What it does

Release Sync is an agent skill from legeling/PromptHub. PromptHub release update skill. Use for /update-readme, version bumps, changelog updates, website sync, GUI screenshot/doc refresh, and multilingual release/documentation alignment.

Its SKILL.md is about 980 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 Changelog and release notes and Technical documentation. The repository describes itself as: 一款包含了 Prompt管理，Skill管理，Agent管理的一站式AI工具箱，助你高效管理提示词，一键分发skills ，一站式管理Agent资产，并实现云同步，备份，版本管理 | An all-in-one AI toolbox for prompt, agent, and skills management. Reuse prompts…. The licence is AGPL-3.0.

When your agent uses it

Changelog updates
GUI screenshot/doc refresh
Multilingual release/documentation alignment

Example prompts

“/release-sync”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

AGENTS.md
spec/releases/release-rules.md
spec/releases/README.md and the target version record, when present
package.json, workspace package manifests, and the newest relevant

What it can do on your machine

Read from SKILL.md and the folder at commit 5439436. 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:
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, 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

Release Sync loads about 978 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 403 words of instructions outside code blocks.

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

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 legeling/PromptHub at commit 5439436, republished under its AGPL-3.0 licence (© legeling). 403 words, ~978 tokens.

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

name: release-sync
description: PromptHub release update skill. Use for `/update-readme`, version bumps, changelog updates, website sync, GUI screenshot/doc refresh, and multilingual release/documentation alignment.

PromptHub Release Sync

Use this skill for version bumps, release preparation, changelog or README updates, website release sync, screenshots, and multilingual release material.

Read First

AGENTS.md
spec/releases/release-rules.md
spec/releases/README.md and the target version record, when present
package.json, workspace package manifests, and the newest relevant CHANGELOG.md section

Do not treat this skill as a second release-policy source. Stable release semantics belong in spec/releases/release-rules.md; this skill is the execution procedure.

Establish Scope

Before editing, identify:

target version and release date
stable, prerelease, historical prerelease, or docs-only update
affected distributions: desktop, CLI, self-hosted web, worker, mobile
whether public copy, in-app copy, screenshots, installers, or signing changed

For non-trivial release work, create or update the matching active change before implementation.

Source And Sync Order

Update version-bearing manifests for affected distributions, including the root and workspace packages when the monorepo version changes.
Update CHANGELOG.md and spec/releases/<version>.md.
Sync repository-facing documentation:
- README.md
- docs/README.md
- docs/README.en.md
- docs/README.zh-TW.md
- docs/README.ja.md
- docs/README.de.md
- docs/README.es.md
- docs/README.fr.md
Run pnpm --dir website sync:release and inspect:
- website/src/generated/release.ts
- website/src/content/docs/changelog.md
- website/src/content/docs/introduction.md
- website/src/content/docs/en/introduction.md
Update non-generated website copy only when the release contract changed:
- website/src/i18n/ui.ts
- website/src/pages/index.astro
- website/src/pages/en/index.astro
When desktop user-facing copy changed, synchronize all locale files under apps/desktop/src/renderer/i18n/locales/.
When visible GUI or feature emphasis changed, inspect and update matching assets under docs/imgs/ and website/public/imgs/.
Synchronize durable conclusions into spec/workflow/*, spec/knowledge/*, spec/rules/*, or spec/adr/* only when their stable contracts changed.

Show full SKILL.md (174 more words)Show less

Release Semantics

Stable-facing badges, default downloads, and install instructions continue to point to the latest stable version when preparing a prerelease.
Historical prereleases below an existing stable version are manual testing artifacts, not the default upgrade path.
Do not document a GUI state without matching current UI evidence or updated screenshots.
Do not silently skip localized docs or locale files; record why a surface is unaffected.
When mentioning CLI availability, distinguish the CLI/npm distribution from desktop-bundled behavior.
Use the website sync command instead of hand-editing generated metadata.

Verification

Run the lowest relevant checks first, then:

pnpm verify:release:quick for local release-impacting changes
pnpm verify:release before tagging or publishing a release candidate
platform signing/notarization checks required by spec/releases/release-rules.md for packaged macOS artifacts

Record commands, results, skipped surfaces, and residual risks in the active change implementation.md. The quick profile is diagnostic and does not grant release approval.

Completion Report

Report:

target version and release type
affected distributions and manifests
website sync status
screenshot status
updated docs and locales
verification results
intentionally skipped surfaces and remaining release risk

Files

Just SKILL.md in .agents/skills/release-sync of legeling/PromptHub.

Open the folder on GitHubat commit 5439436

Compare with similar skills

Release Sync 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.

Release Sync compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Release Sync this skilllegeling/PromptHub	1.7k	—	~978	Automated safety check: Pass	AGPL-3.0	9 days ago
Simple Englishmoeru-ai/airi	50k	2 repos	~4.6k	Automated safety check: Pass	MIT	today
Ccb GitHubSeemSeam/claude_codex_bridge	3.5k	—	~4.9k	Automated safety check: Pass	Custom licence	yesterday
Golang Documentationunxed/f4	240	3 repos	~3.5k	Automated safety check: Pass	MIT	today
Simple Englishropensci/ckanr	104	3 repos	~2k	Automated safety check: Pass	MIT	15 days ago
Opik Documentation Patternscomet-ml/opik	22k	—	~1.3k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
50k GitHub starsUsed in 2 repos~4.6k tokens
DevelopmentAuto-check passed
Ccb GitHub
SeemSeam/claude_codex_bridge
Maintain this CCB project's GitHub-facing release and npm publication surface.
3.5k GitHub stars~4.9k tokensUpdated yesterday
DevelopmentAuto-check passed
Golang Documentation
unxed/f4
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt.
240 GitHub starsUsed in 3 repos~3.5k tokens
DevelopmentAuto-check passed
Simple English
ropensci/ckanr
Write or rewrite text in plain, layman-readable English in the spirit of ASD-STE100 Simplified Technical English: short sentences, active voice, simple tenses, one word one meaning, condition before…
104 GitHub starsUsed in 3 repos~2k tokens
DevelopmentAuto-check passed
Opik Documentation Patterns
comet-ml/opik
Rules for writing PR descriptions, changelog entries and feature documentation in the Opik repository, including the exact headings that CI requires.
22k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
Release
jrswab/axe
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
895 GitHub stars~1.4k tokensUpdated 2 days ago
DevelopmentAuto-check passed

Questions about Release Sync

What does Release Sync do?

PromptHub release update skill. An agent skill from legeling/PromptHub. Release Sync is an agent skill from legeling/PromptHub. PromptHub release update skill.

When should I use Release Sync?

Release Sync fits situations like: changelog updates; GUI screenshot/doc refresh; multilingual release/documentation alignment.

How do I install Release Sync in Claude Code?

Run `npx skills add legeling/PromptHub --skill release-sync -a claude-code`. Or copy the skill folder (.agents/skills/release-sync in legeling/PromptHub) into .claude/skills/release-sync in your project. Claude Code loads it when a task matches its description.

How do I install Release Sync in Codex?

Run `npx skills add legeling/PromptHub --skill release-sync -a codex`. Or copy the skill folder (.agents/skills/release-sync in legeling/PromptHub) into .agents/skills/release-sync in your project. Codex loads it when a task matches its description.

Can I use Release Sync 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 legeling/PromptHub --skill release-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-sync, .gemini/skills/release-sync, .github/skills/release-sync and .opencode/skills/release-sync in your project.

What does Release Sync need to run?

Going by SKILL.md and its folder, Release Sync needs the command-line tools its instructions call (pnpm).

Does Release Sync access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Release Sync 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 Release Sync use?

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

How many tokens does Release Sync use?

About 978 tokens (SKILL.md is roughly 3.9k 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 Release Sync?

Skills that share tags, products or a category with Release Sync: Simple English (moeru-ai/airi, 50k stars), Ccb GitHub (SeemSeam/claude_codex_bridge, 3.5k stars), Golang Documentation (unxed/f4, 240 stars) and Simple English (ropensci/ckanr, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Sync?

legeling (a GitHub user) maintains it in legeling/PromptHub, which has 1,697 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 28, 2026.

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

Release Sync

Install Release Sync

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

PromptHub Release Sync

Read First

Establish Scope

Source And Sync Order

Release Semantics

Verification

Completion Report

Files

Compare with similar skills

Similar skills

Simple English

Ccb GitHub

Golang Documentation

Simple English

Opik Documentation Patterns

Release

More from legeling/PromptHub

Spec Init

Questions about Release Sync

Install Release Sync

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

PromptHub Release Sync

Read First

Establish Scope

Source And Sync Order

Release Semantics

Verification

Completion Report

Files

Compare with similar skills

Similar skills

Simple English

Ccb GitHub

Golang Documentation

Simple English

Opik Documentation Patterns

Release

More from legeling/PromptHub

Spec Init

Related

Questions about Release Sync