New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

DeepChat Release Process

by ThinkInAIXYZ in ThinkInAIXYZ/deepchat

Runs the DeepChat repository's release flow: prepares bilingual release notes and a version bump on dev, cuts or updates a release branch, then fast-forwards main and tags the version.

Apache-2.0Auto-check passedDevelopment

Install DeepChat Release Process

skills CLI
$ npx skills add ThinkInAIXYZ/deepchat --skill deepchat-release -a claude-code

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

GitHub CLI
$ gh skill install ThinkInAIXYZ/deepchat deepchat-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/ThinkInAIXYZ/deepchat.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/deepchat-release .claude/skills/deepchat-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/

Facts

Skill name
deepchat-release
GitHub stars
6.4k
Token cost
~1.1k tokens
SKILL.md length
561 words
Files
3 (incl. references)
Skills in repo
15
Repo updated
First seen
Licence
Apache-2.0

At a glance

Runs the DeepChat repository's release flow: prepares bilingual release notes and a version bump on dev, cuts or updates a release branch, then fast-forwards main and tags the version.

  • Works in 4 steps: prepare metadata → cut release branch → update existing release branch → …
  • Preparing a new DeepChat version with an updated changelog
  • SKILL.md covers Overview, Start With Repo State, Choose The Release Mode and Update Release Metadata, plus 5 more sections
  • Calls pnpm

What it does

The skill first inspects git state, checking the current branch, working tree, and whether a release/<version> branch or v<version> tag already exists locally or on origin, stopping to ask before replacing a tag on the wrong commit. It then picks one of four modes to match the request: preparing metadata on dev (bumping package.json, adding a CHANGELOG.md section and committing), cutting a new release branch, updating an existing release branch after metadata changed with a force-push limited to that disposable branch, or publishing, which fast-forwards main, tags the same commit and deletes the temporary release branch.

For v1.0.1 onward, changelog entries list English bullets first and Chinese bullets second under a dated version heading, derived from commits or the diff since the previous tag and covering only user-visible changes; older sections are preserved unless you ask to rewrite them. After editing metadata, the skill runs the repository's required pnpm format, pnpm i18n and pnpm lint checks. A bundled release-checklist reference gives the exact commands for each mode.

When your agent uses it

  • Preparing a new DeepChat version with an updated changelog
  • Cutting or updating a release branch for an upcoming version
  • Publishing an approved release by fast-forwarding main and tagging it
  • Resuming a release that was only partly finished

Example prompts

  • “Prepare release metadata for v1.2.0 on dev.”
  • “Cut the release branch for v1.2.0 and push it.”
  • “The release PR for v1.2.0 is approved, so publish it now.”

Requirements

  • pnpm
  • Git with push access to the repository

Workflow steps

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

  1. prepare metadata
  2. cut release branch
  3. update existing release branch
  4. publish

What it can do on your machine

Read from SKILL.md and the folder at commit f873e78. 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

DeepChat Release Process loads about 1.1k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 561 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~124
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.6k

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 ThinkInAIXYZ/deepchat at commit f873e78, republished under its Apache-2.0 licence (© ThinkInAIXYZ). 561 words, ~1,140 tokens.

Download SKILL.mdSave it as .claude/skills/deepchat-release/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
deepchat-release
description
Prepare and publish DeepChat releases in this repository. Use when Codex needs to bump the app version, update CHANGELOG.md, keep release notes bilingual from v1.0.1 onward with English bullets first and Chinese bullets second, run release checks, create or update versioned release branches such as release/v1.0.1, continue a half-finished release, fast-forward main with the documented release flow, create or push version tags, or clean up release branches after publishing.

DeepChat Release

Overview

Follow the repository-specific DeepChat release process. Prepare release metadata on dev, keep CHANGELOG.md concise, and publish through the documented fast-forward flow instead of merge commits on main.

Start With Repo State

Inspect git state before changing anything:

  • Check the current branch and working tree.
  • Check whether release/<version> exists locally or on origin.
  • Check whether v<version> exists locally or on origin.

If a local or remote tag already exists on the wrong commit, stop and ask before replacing it.

Choose The Release Mode

Pick the mode that matches the user's request and current git state:

  1. prepare metadata Update package.json, CHANGELOG.md, and the release notes commit on dev.
  2. cut release branch Create release/<version> from the release-ready commit on dev and push it.
  3. update existing release branch Use this when the release branch already exists but metadata changed afterward. Commit on dev, move release/<version> to the new dev commit, and force-push only the disposable release branch.
  4. publish Use this only after the release PR is approved. Fast-forward main, create the version tag on the same commit, push the tag, and then delete the temporary release branch.

Use references/release-checklist.md for exact commands.

Update Release Metadata

When preparing a release on dev:

  • Update package.json to the target version.
  • Add a new CHANGELOG.md section at the top.
  • Summarize only user-visible or release-relevant changes since the previous tag.
  • Prefer deriving the notes from recent commits or the diff since the previous release tag.
  • Do not create SDD folders for pure release metadata, branch, tag, or release PR work.

For v1.0.1 and later, format changelog entries in this order:

md
## vX.Y.Z (YYYY-MM-DD)
- English bullet
- English bullet
- 中文条目
- 中文条目

Use the current local date in YYYY-MM-DD form. Preserve older changelog sections unless the user explicitly asks to rewrite them.

Run Release Checks

After editing release metadata, run these repo-required commands:

  • pnpm run format
  • pnpm run i18n
  • pnpm run lint

Prefer running pnpm run typecheck before cutting the release branch. Run tests when the user asks, when the release touches behavior beyond metadata, or when risk is unclear. Report pre-existing failures separately from the release metadata work.

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

Follow Release Branch Policy

  • Keep dev as the integration branch.
  • Treat release/<version> as disposable and identical to a commit already on dev.
  • Never use the GitHub merge button for releases to main.
  • Never click "Update branch" on the release PR.
  • Use pnpm run release:ff -- release/<version> --tag v<version> to publish after approval.

Read ../../../docs/release-flow.md when you need the full repository policy or if the checklist and repo docs ever diverge.

Common Recovery Case

When the user says something like "the release branch already exists but the tag is not created yet" or "I fixed the changelog after cutting the release branch":

  1. Commit the metadata fix on dev.
  2. Push dev.
  3. Move release/<version> to HEAD.
  4. Force-push release/<version> with --force-with-lease.
  5. Continue with the existing or updated PR to main.
  6. After approval, publish and create the tag.

Response Rules

  • Act on the repo when the user wants the release advanced; do not stop at generic advice.
  • Tell the user exactly which step of the release flow they are currently in.
  • Use concrete versions and dates such as v1.0.1 and 2026-04-02.
  • Keep commands copy-pastable and repo-specific.
  • If checks fail, separate blocking failures from unrelated existing warnings.

Examples

Activate this skill for requests like:

  • "准备发布 1.0.2，更新版本号和 changelog"
  • "继续发 1.0.1，release 分支已经有了，还没打 tag"
  • "帮我按项目流程把 release/v1.0.3 发出去"
  • "检查一下现在离发布 v1.0.4 还差什么"

© ThinkInAIXYZ, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/deepchat-release of ThinkInAIXYZ/deepchat.

  • SKILL.md
  • agents/openai.yaml
  • references/release-checklist.md

Open the folder on GitHubat commit f873e78

Compare with similar skills

DeepChat Release Process 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.

DeepChat Release Process compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
DeepChat Release Process this skillThinkInAIXYZ/deepchat6.4k—~1.1kAutomated safety check: PassApache-2.0
D2mcpp Authoringmcpp-community/d2mcpp1.8k—~2.7kAutomated safety check: PassCustom licence
Pre ReleaseZhuoZhuoCrayon/throttled-py651—~1.1kAutomated safety check: PassMIT
Pulse Releasequnqin24/Pulse516—~1.3kAutomated safety check: PassApache-2.0
Release WorkflowCaldis/react-zmage946—~3.6kAutomated safety check: NotesMIT
Release New Versionniki914/zafiro227—~2kAutomated safety check: PassMIT

Similar skills

  • D2mcpp Authoring

    mcpp-community/d2mcpp

    Authoring conventions, design principles, and file formats for the d2mcpp (D2X) Modern C++ tutorial project.

    1.8k GitHub stars~2.7k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Pre Release

    ZhuoZhuoCrayon/throttled-py

    Automates release preparation for throttled-py. An agent skill from ZhuoZhuoCrayon/throttled-py.

    651 GitHub stars~1.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed

  • Pulse Release

    qunqin24/Pulse

    Release a new Pulse version end to end — checks, bilingual CHANGELOG entry, VERSION, tag, the release workflow, syncing main, and the issue replies that go with it.

    516 GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Release Workflow

    Caldis/react-zmage

    A skill your agent uses when the user wants to ship a new version of react-zmage to npm.

    946 GitHub stars~3.6k tokensUpdated 4 mo ago
    DevelopmentAuto-check: notes

  • Release New Version

    niki914/zafiro

    A skill your agent uses when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and…

    227 GitHub stars~2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Changelog Entries

    hugodemenez/deltalytix

    Write new bilingual English and French Deltalytix changelog entries from a reviewed release outline.

    159 GitHub stars~1.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from ThinkInAIXYZ/deepchat

All 15 skills in this repo

  • DeepChat Provider Integration

    ThinkInAIXYZ/deepchat

    Guides adding an LLM provider to DeepChat through explicit source changes: collect the provider details, pick a transport path and add registry entries and tests.

    6.4k GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed

  • DeepChat CLI

    ThinkInAIXYZ/deepchat

    Lets an agent drive DeepChat's bundled CLI for model calls, media generation, transcription, OCR, artifacts, configuration, Skills and MCP operations, within strict command rules.

    6.4k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • DeepChat Settings

    ThinkInAIXYZ/deepchat

    Changes DeepChat's own application settings, such as theme, language, font size and sound, through a fixed set of settings tools, and points to the right screen for anything else.

    6.4k GitHub stars~786 tokensUpdated today
    Auto-check passed

  • DeepChat Data Import Helper

    ThinkInAIXYZ/deepchat

    Guides building a third-party importer for DeepChat's local SQLite data, covering schema, encryption and safe read-only access patterns.

    6.4k GitHub stars~738 tokensUpdated today
    Auto-check passed

  • DeepChat Desktop Control

    ThinkInAIXYZ/deepchat

    Operates native desktop apps through DeepChat's built-in Computer Use tools, following a snapshot-then-act loop with session setup, app launch and window inspection.

    6.4k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • AntV Infographic Syntax Creator

    ThinkInAIXYZ/deepchat

    Turns user content into AntV Infographic syntax, choosing a matching template and structuring the data into a single infographic code block.

    6.4k GitHub stars~278 tokensUpdated today
    Auto-check passed

Categories

Questions about DeepChat Release Process

What does DeepChat Release Process do?

Runs the DeepChat repository's release flow: prepares bilingual release notes and a version bump on dev, cuts or updates a release branch, then fast-forwards main and tags the version. The skill first inspects git state, checking the current branch, working tree, and whether a release/<version> branch or v<version> tag already exists locally or on origin, stopping to ask before replacing a tag on the wrong commit.md section and committing), cutting a new release branch, updating an existing release branch after metadata changed with a force-push limited to that disposable branch, or publishing, which fast-forwards main, tags the same commit and deletes the temporary release branch.

When should I use DeepChat Release Process?

DeepChat Release Process fits situations like: preparing a new DeepChat version with an updated changelog; cutting or updating a release branch for an upcoming version; publishing an approved release by fast-forwarding main and tagging it; resuming a release that was only partly finished.

How do I install DeepChat Release Process in Claude Code?

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

How do I install DeepChat Release Process in Codex?

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

Can I use DeepChat Release Process 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 ThinkInAIXYZ/deepchat --skill deepchat-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/deepchat-release, .gemini/skills/deepchat-release, .github/skills/deepchat-release and .opencode/skills/deepchat-release in your project.

What does DeepChat Release Process need to run?

Going by SKILL.md and its folder, DeepChat Release Process needs the command-line tools its instructions call (pnpm). Our summary lists: pnpm; Git with push access to the repository.

Does DeepChat Release Process 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 DeepChat Release Process 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 DeepChat Release Process use?

DeepChat Release Process is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does DeepChat Release Process use?

About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 488 tokens, read only when the agent opens those files.

What are the alternatives to DeepChat Release Process?

Skills that share tags, products or a category with DeepChat Release Process: D2mcpp Authoring (mcpp-community/d2mcpp, 1.8k stars), Pre Release (ZhuoZhuoCrayon/throttled-py, 651 stars), Pulse Release (qunqin24/Pulse, 516 stars) and Release Workflow (Caldis/react-zmage, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains DeepChat Release Process?

ThinkInAIXYZ (a GitHub organization) maintains it in ThinkInAIXYZ/deepchat, which has 6,359 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 8, 2026.

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