What problem does it solve?
Releasing a new DeepChat version involves many error-prone manual steps: bumping package.json, writing a bilingual CHANGELOG.md entry, cutting a disposable release branch, running repo checks, and publishing via fast-forward instead of merge commits. This Skill encodes that exact repository workflow so releases are consistent and recoverable.
Core Features & Use Cases
- Release Metadata Preparation: Updates package.json and CHANGELOG.md on the dev branch, with English bullets first and Chinese bullets second for v1.0.1 onward.
- Branch and Tag Management: Creates or force-updates release/vX.Y.Z branches, publishes via pnpm run release:ff, creates version tags, and cleans up disposable branches.
- Recovery Workflows: Handles half-finished releases, such as when the release branch exists but the tag was never created or the changelog was fixed after cutting the branch.
- Use Case: You ask to "continue releasing 1.0.1, the release branch exists but no tag yet" and the Skill inspects git state, moves the branch to the fixed dev commit, force-pushes with --force-with-lease, and publishes after PR approval.
Quick Start
Ask the assistant to prepare and publish DeepChat release v1.0.2 by updating the version and changelog, cutting the release branch, and following the documented fast-forward flow.