# Release Sync

PromptHub release update skill.

- Repository: https://github.com/legeling/PromptHub (1785 stars)
- Category: Git and review
- License: AGPL-3.0
- Last updated: 2026-10-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add legeling/PromptHub --skill release-sync -g -a claude-code -y`
Codex: `npx skills add legeling/PromptHub --skill release-sync -g -a codex -y`
Cursor: `npx skills add legeling/PromptHub --skill release-sync -g -a cursor -y`
Gemini CLI: `npx skills add legeling/PromptHub --skill release-sync -g -a gemini-cli -y`

## Description

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

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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

1. `AGENTS.md`
2. `spec/releases/release-rules.md`
3. `spec/releases/README.md` and the target version record, when present
4. `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

The rest: https://github.com/legeling/PromptHub/blob/HEAD/.agents/skills/release-sync/SKILL.md