deepchat-release
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.
npx skills add ThinkInAIXYZ/deepchat --skill deepchat-release --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 t
- Overview
- Start With Repo State
- Choose The Release Mode
- Update Release Metadata
- Run Release Checks
- Follow Release Branch Policy
- Common Recovery Case
- Response Rules
- Examples
What does the deepchat-release skill do?
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.
How do I install it?
Run `npx skills add ThinkInAIXYZ/deepchat --skill deepchat-release --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ThinkInAIXYZ/deepchat, a repository with 6,191 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.