ThinkInAIXYZ/deepchat / .agents/skills/deepchat-release
deepchat-release
VerifiedPrepare 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 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:
prepare metadataUpdatepackage.json,CHANGELOG.md, and the release notes commit ondev.cut release branchCreaterelease/<version>from the release-ready commit ondevand push it.update existing release branchUse this when the release branch already exists but metadata changed afterward. Commit ondev, moverelease/<version>to the newdevcommit, and force-push only the disposable release branch.publishUse this only after the release PR is approved. Fast-forwardmain, 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.jsonto the target version. - Add a new
CHANGELOG.mdsection 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:
## 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 formatpnpm run i18npnpm 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.
Follow Release Branch Policy
- Keep
devas the integration branch. - Treat
release/<version>as disposable and identical to a commit already ondev. - 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":
- Commit the metadata fix on
dev. - Push
dev. - Move
release/<version>toHEAD. - Force-push
release/<version>with--force-with-lease. - Continue with the existing or updated PR to
main. - 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.1and2026-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 还差什么"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 196k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |