honk-release

Agent Skills › daeuniverse/honk › honk-release

GitHub

指导如何准备 honk 项目的发布流程，包括确认 CI 状态、生成变更日志、创建草稿版本及最终发布。

.agents/skills/honk-release/SKILL.md daeuniverse/honk

需要执行软件版本发布准备发布说明和变更日志

npx skills add daeuniverse/honk --skill honk-release -g -y

More Options

Non-standard path

npx skills add https://github.com/daeuniverse/honk/tree/main/.agents/skills/honk-release -g -y

Use without installing

npx skills use daeuniverse/honk@honk-release

指定 Agent (Claude Code)

npx skills add daeuniverse/honk --skill honk-release -a claude-code -g -y

安装 repo 全部 skill

npx skills add daeuniverse/honk --all -g -y

预览 repo 内 skill

npx skills add daeuniverse/honk --list

Frontmatter

{
    "name": "honk-release",
    "description": "Use to prepare a honk release and follow the maintainer's tag and publication sequence."
}

Read first: AGENTS.md and .agents/rules/release.md; then .github/workflows/release.yml.

Publication belongs to the maintainer. Contributors can prepare the notes without publishing.

Steps

Confirm the intended main tip has been pushed.
Confirm its branch CI from .github/workflows/ci.yml is green in GitHub Actions, through the web UI or API.
Follow the version and changelog preparation rules in .agents/rules/release.md, "Release process (standing convention)". The maintainer tags the tested tip only after it contains the collected release section.
The tag runs .github/workflows/release.yml. Wait for its test, build and release jobs to finish and create the draft GitHub Release with generated notes.
The maintainer writes the draft's Highlights and checks the collected changelog entries and embedded doona pairing. Notes format: .agents/rules/release.md, "Release process (standing convention)".
The maintainer checks the assets against the build and publishes the draft. Publish commands: .agents/rules/release.md, "Release process (standing convention)".

The intended main tip is pushed and its branch CI is green.
The maintainer created and pushed the next tag under the release rule.
The tag's base version matches Cargo.toml, and its exact version has a collected changelog section.
The tag workflow finished and created the draft Release.
The maintainer wrote the Highlights and checked the generated notes.
The maintainer checked the assets and published the draft.