
Deepchat Release
Automates the full release cycle for the DeepChat repository, from bumping versions and maintaining bilingual changelogs to creating release branches, running format and lint checks, and fast-forwarding main without merge commits. It enforces the project's specific workflow where dev is the integration branch and release branches are disposable pointers to commits already on dev. Handles recovery scenarios like updating an existing release branch when you fix the changelog after cutting it. The bilingual requirement is a nice touch: English bullets first, Chinese second, starting from v1.0.1. If you maintain a project with a strict Git flow and repeatable release steps, this is the kind of automation that prevents you from forgetting the typecheck or force-pushing the wrong branch at 11pm.
- GitHub stars
- 6K
- last updated
- Jun 11, 2026
Install
$ npx -y skills add thinkinaixyz/deepchat --skill deepchat-release --agent claude-codeInstalls into .claude/skills of the current project.
Files
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 onorigin. - Check whether
v<version>exists locally or onorigin.
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:
Sponsors
Details
- Repository
- github.com/thinkinaixyz/deepchat
- Categories
- Git & Pull Requests, Release Management
- License
- Apache-2.0
- First seen
- Jun 11, 2026