Опишете задачата
Към всички skills

deepchat-release

ThinkInAIXYZ · Документация

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.

Оригинален текст · няма потвърден превод на български
Платформи: ClaudeНиво: СредноВ индекса: 11.06.2026 г.Обновен в GitHub: 21.09.2026 г.

Теми: agent · agent-skills · ai · ai-assistant · ai-sdk · chatgpt · claude · cross-platform · deepseek · electron · gemini · harness-design · hermes-agent · llm-client · mcp

Първо прочетете инструкцията.

Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.

Оригинален SKILL.md
GitHub хранилище
Звезди на репото
6340
Лиценз
Apache-2.0
Последна проверка на записа
21.09.2026 г.

Добавете в своя инструмент.

Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.

npx skills add ThinkInAIXYZ/deepchat

Страницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.

Откъс от SKILL.md

Началото на файла на автора, без превод.

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 on origin.
  • Check whether v<version> exists locally or on origin.

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:

  1. prepare metadata Update package.json, CHANGELOG.md, and the release notes commit on dev.
  2. cut release branch Create release/<version> from the release-ready commit on dev and push it.
  3. update existing release branch Use this when the release branch already exists but metadata changed afterward. Commit on dev, move release/<version> to the new dev commit, and force-push only the disposable release branch.
  4. publish Use this only after the release PR is approved. Fast-forward main, 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.json to the target version.
  • Add a new CHANGELOG.md section 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 format
  • pnpm run i18n
  • pnpm run lint

Целият SKILL.md в GitHub