release-governance
Use when auditing release readiness, writing release notes, choosing a semantic version tag, or preparing a GitHub draft release from repository evidence.
- License 许可
- Apache-2.0
- 最近更新
- 2026-08-25
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- release-governance
- description
- Use when auditing release readiness, writing release notes, choosing a semantic version tag, or preparing a GitHub draft release from repository evidence.
- allowed-tools
- [ "inspect_release_state", "run_release_checks", "workspace", "save_release_candidate", "get_release_candidate", "publish_draft_release" ]
02 资源文件 1
- 参考文档references/review-checklist.md490 B
03 SKILL.md 正文
Release governance
- Inspect the authoritative release snapshot. A dirty tree, detached HEAD, wrong branch, or moving HEAD is a hard stop.
- Run every configured check and require a passing result bound to the same HEAD.
- Read the changesets and representative source or documentation changes. Commit subjects are leads, not sufficient evidence by themselves.
- Group user-visible changes under Added, Changed, Fixed, Security, and Operations. Omit empty groups.
- State breaking changes and migration work explicitly. If none are evidenced, do not invent a compatibility promise.
- Keep internal implementation trivia out unless it changes operation, security, performance, or the public API.
- Save one candidate, read it back, and present its revision and exact tag to the operator before publication.
- Publication means a GitHub draft only. A human owns final editing, tagging, and publishing.
Read references/review-checklist.md before saving a candidate.
04 同仓库更多 Skills
kuralle-agents
Build, extend, or debug an agent with the Kuralle framework (`@kuralle-agents/*`). Use this skill whenever the task touches `defineAgent`, `defineFlow`, `defineTool`, `createRuntime`, a `*.flow.json` definition, an agent folder compiled by `kuralle build`, a Kuralle skill or plugin, or a Kuralle deployment on Hono, Cloudflare Workers, or Next.js. Trigger it for any mention of Kuralle agents, flows, triage routing, durable tools, effect logs, session stores, agent handoffs, collect/reply/action/decide nodes, or the `kuralle` CLI — and also when the user asks to "build an agent", "add a flow", "add a tool to the bot", "make the bot ask for X first", or "deploy the agent", inside a repository that depends on `@kuralle-agents/core`.
remotion-upgrade
Upgrade Remotion, and related packages
remotion-studio
Preview a Remotion video
remotion-saas
Build an app with Remotion
remotion-render
Export a Remotion video
remotion-multimedia
Interacting with Mediabunny