deepchat-release
Prepare and publish DeepChat releases in this repository
Install / Use
npx skills add ThinkInAIXYZ/deepchat --skill deepchat-releaseInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Tags
Our assessment of deepchat-release
deepchat-release scores 81/100 on our quality scale, 993rd of 1,155 Content & Media skills we index.
Its SKILL.md is 4.5 KB long, well organised into 11 sections with 1 code example: a solid amount of guidance for an agent.
With 6,372 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 27 days ago, so deepchat-release is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-27. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
deepchat-release compared with similar skills
All 4 of these similar skills score higher than deepchat-release; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| deepchat-release (this skill)by ThinkInAIXYZ | 81 | 6.4k | 27d ago | SKILL.md |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install deepchat-release?
- Run
npx skills add ThinkInAIXYZ/deepchat --skill deepchat-release. The install tabs above show the steps for each supported agent. - Which AI agents does deepchat-release work with?
- It is written for OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is deepchat-release safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is deepchat-release still maintained?
- The repository was last updated 27 days ago, so deepchat-release is actively maintained.
Skill content
View source on GitHubname: 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 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
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
