Release Sync logo

Release Sync

CommunityPopular
legeling
release-sync

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

Overview

Publisherlegeling
RepositoryPromptHub
Skill namerelease-sync
Stars
1.7K
Forks
194
Bundled files
Instructions only
LicenseAGPL-3.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by legeling on GitHub. Read the source before you install it.

Installation

Install the Release Sync AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/legeling/PromptHub/tree/main/.agents/skills/release-sync
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/legeling/PromptHub.git /tmp/PromptHub
mkdir -p .claude/skills
cp -r /tmp/PromptHub/.agents/skills/release-sync .claude/skills/release-sync
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Release Sync in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Release Sync on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Release Sync is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

  1. Update version-bearing manifests for affected distributions, including the root and workspace packages when the monorepo version changes.
  2. Update CHANGELOG.md and spec/releases/<version>.md.
  3. 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
  4. 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
  5. 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
  6. When desktop user-facing copy changed, synchronize all locale files under apps/desktop/src/renderer/i18n/locales/.
  7. When visible GUI or feature emphasis changed, inspect and update matching assets under docs/imgs/ and website/public/imgs/.
  8. Synchronize durable conclusions into spec/workflow/*, spec/knowledge/*, spec/rules/*, or spec/adr/* only when their stable contracts changed.

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

Frequently asked questions

What does the Release Sync AI skill do?

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

Why use Release Sync on TypingMind?

Because you install it once and use it with any model. Release Sync is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Release Sync in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/legeling/PromptHub/tree/main/.agents/skills/release-sync. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Release Sync?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Release Sync?

As many as you like. As long as a model supports skills, you can use Release Sync with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Release Sync AI skill free?

Yes. It is published on GitHub by legeling under the AGPL-3.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇