Skip to content

ThinkInAIXYZ/deepchat / .agents/skills/deepchat-release

deepchat-release

Verified

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.

FileKindSize
SKILL.mdskill md4.6 KB
agents/openai.yamlconfig210 B
references/release-checklist.mdmarkdown1.9 KB

references/release-checklist.md

View on GitHub
# DeepChat Release Checklist

Use this file for the exact command sequence after you know the target version and the current git state.

## 1. Inspect state

```bash
git status --short
git branch --show-current
git branch --list "release/vX.Y.Z"
git branch -r --list "origin/release/vX.Y.Z"
git rev-parse --verify --quiet "refs/tags/vX.Y.Z"
git ls-remote --tags origin "refs/tags/vX.Y.Z"
```

If a tag already exists locally or remotely, verify it before continuing. Ask before replacing or deleting a tag.

## 2. Prepare metadata on `dev`

```bash
git switch dev
git pull --ff-only origin dev
```

Then update:

- `package.json`
- `CHANGELOG.md`

Recommended checks:

```bash
pnpm run format
pnpm run i18n
pnpm run lint
pnpm run typecheck
```

Commit and push:

```bash
git add package.json CHANGELOG.md
git commit -m "chore(release): prepare vX.Y.Z"
git push origin dev
```

## 3. Cut a new release branch

Use this when `release/vX.Y.Z` does not exist yet.

```bash
git switch -c release/vX.Y.Z
git push -u origin release/vX.Y.Z
```

Open a PR from `release/vX.Y.Z` to `main`.

## 4. Update an existing release branch

Use this when the release branch already exists and metadata changed afterward.

```bash
git switch dev
git branch -f release/vX.Y.Z HEAD
git push --force-with-lease origin release/vX.Y.Z
```

If a PR from `release/vX.Y.Z` to `main` already exists, let it update in place.

## 5. Publish after PR approval

```bash
pnpm run release:ff -- release/vX.Y.Z --tag vX.Y.Z
git tag vX.Y.Z release/vX.Y.Z
git push origin vX.Y.Z
```

## 6. Clean up the disposable release branch

```bash
git push origin --delete release/vX.Y.Z
git branch -d release/vX.Y.Z
```

## 7. Changelog format from `v1.0.1` onward

```md
## vX.Y.Z (YYYY-MM-DD)
- English bullet
- English bullet
- 中文条目
- 中文条目
```

Keep English bullets first, Chinese bullets second, and preserve older sections unless the user explicitly asks to rewrite history.
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexUnverifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall