How do I install the Release skill?

Run npx skillmds@latest add foru17/release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release?

foru17 (@foru17) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release by foru17 — Agent Skill

Name: Release
Author: foru17

File contents

Release Process

Two independent release lines, both driven entirely by git tags:

Line	Tag	CI workflow	Artifact
Main product	`vX.Y.Z`	`.github/workflows/docker-build.yml`	Multi-arch Docker image (Docker Hub + GHCR), ~20 min
Agent probe	`agent-vX.Y.Z`	`.github/workflows/agent-release.yml`	Multi-arch agent binaries, ~1 min

agent-v* does not build Docker images. The agent binary version is injected at build time from the tag via ldflags — there is no version file to bump for the agent.

Main product release

Version: bump version in the root package.json only (apps/* keep their own independent versions; the root field is the single source of truth).
Changelog: add a dated section to BOTH CHANGELOG.md (Chinese) and CHANGELOG.en.md (English), Keep-a-Changelog style (## [X.Y.Z] - YYYY-MM-DD, ### 修复/Fixed, ### 优化/Changed). Link issue/PR numbers as reference-style links at the section end. Credit external contributors by handle.
Env docs: any new environment variable must be documented in .env.example before release.
Test gates (all must pass):

pnpm --filter @neko-master/collector exec tsc --noEmit
pnpm --filter @neko-master/collector test
pnpm --filter @neko-master/web exec tsc --noEmit
pnpm --filter @neko-master/web exec next build

Ship:

git push origin main
git tag -a vX.Y.Z -m "<one-line summary>"
git push origin vX.Y.Z
gh release create vX.Y.Z --title "vX.Y.Z" --notes "<highlights + upgrade notes>"

Verify CI: gh run list --limit 3 → the tag-branch "Build and Push Docker Image" run must end completed/success. Multi-arch builds can exceed 20 minutes; poll rather than assume.

Agent release

See docs/agent/release.en.md for full details. Short form:

cd apps/agent && go vet ./... && go test ./... && sh -n nekoagent && sh -n install.sh
git tag agent-vX.Y.Z && git push origin agent-vX.Y.Z

Keep AgentProtocolVersion (Go, internal/config/config.go) and the collector's minimum accepted protocol version in sync when the payload changes — the collector rejects too-old agents with HTTP 426.

Conventions

Also check docs/release-checklist.md (pre-release validation for combined product+agent releases).
Upgrade notes in the release body must call out any automatic startup migration so operators aren't surprised by one-time log output.
Commit messages follow conventional-commit style (fix(scope): ..., release: vX.Y.Z — ...).

---name: releasedescription: Cut and publish a Neko Master release — main product (Docker, v* tags) or Go agent (agent-v* tags). Use when bumping versions, writing CHANGELOG entries, tagging, or verifying CI artifacts.---# Release ProcessTwo independent release lines, both driven entirely by git tags:| Line | Tag | CI workflow | Artifact ||---|---|---|---|| Main product | `vX.Y.Z` | `.github/workflows/docker-build.yml` | Multi-arch Docker image (Docker Hub + GHCR), ~20 min || Agent probe | `agent-vX.Y.Z` | `.github/workflows/agent-release.yml` | Multi-arch agent binaries, ~1 min |`agent-v*` does not build Docker images. The agent binary version is injected at build time from the tag via ldflags — there is no version file to bump for the agent.## Main product release1. **Version**: bump `version` in the **root** `package.json` only (apps/* keep their own independent versions; the root field is the single source of truth).2. **Changelog**: add a dated section to BOTH `CHANGELOG.md` (Chinese) and `CHANGELOG.en.md` (English), Keep-a-Changelog style (`## [X.Y.Z] - YYYY-MM-DD`, `### 修复/Fixed`, `### 优化/Changed`). Link issue/PR numbers as reference-style links at the section end. Credit external contributors by handle.3. **Env docs**: any new environment variable must be documented in `.env.example` before release.4. **Test gates** (all must pass):```bashpnpm --filter @neko-master/collector exec tsc --noEmitpnpm --filter @neko-master/collector testpnpm --filter @neko-master/web exec tsc --noEmitpnpm --filter @neko-master/web exec next build```5. **Ship**:```bashgit push origin maingit tag -a vX.Y.Z -m "<one-line summary>"git push origin vX.Y.Zgh release create vX.Y.Z --title "vX.Y.Z" --notes "<highlights + upgrade notes>"```6. **Verify CI**: `gh run list --limit 3` → the tag-branch "Build and Push Docker Image" run must end `completed/success`. Multi-arch builds can exceed 20 minutes; poll rather than assume.## Agent releaseSee `docs/agent/release.en.md` for full details. Short form:```bashcd apps/agent && go vet ./... && go test ./... && sh -n nekoagent && sh -n install.shgit tag agent-vX.Y.Z && git push origin agent-vX.Y.Z```Keep `AgentProtocolVersion` (Go, `internal/config/config.go`) and the collector's minimum accepted protocol version in sync when the payload changes — the collector rejects too-old agents with HTTP 426.## Conventions- Also check `docs/release-checklist.md` (pre-release validation for combined product+agent releases).- Upgrade notes in the release body must call out any automatic startup migration so operators aren't surprised by one-time log output.- Commit messages follow conventional-commit style (`fix(scope): ...`, `release: vX.Y.Z — ...`).

Frequently asked questions

Release