Agent Skills › franklioxygen/agent-workflows › release-prep

release-prep

GitHub

用于准备 agent-workflows 库发布。检查就绪状态，收集变更文件，运行审计，起草发布说明，生成验证证据并创建发布清单。适用于用户要求准备、验证或移交发布时。

skills/release-prep/SKILL.md franklioxygen/agent-workflows

Trigger Scenarios

用户要求准备 agent-workflows 发布用户要求验证发布就绪状态用户要求总结发布内容用户要求打包或移交发布

Install

npx skills add franklioxygen/agent-workflows --skill release-prep -g -y

More Options

Use without installing

npx skills use franklioxygen/agent-workflows@release-prep

指定 Agent (Claude Code)

npx skills add franklioxygen/agent-workflows --skill release-prep -a claude-code -g -y

安装 repo 全部 skill

npx skills add franklioxygen/agent-workflows --all -g -y

预览 repo 内 skill

npx skills add franklioxygen/agent-workflows --list

SKILL.md

Frontmatter

{
    "name": "release-prep",
    "description": "Prepare the agent-workflows library for release by checking release readiness, gathering changed files, running workflow-maintainer audits, drafting release notes, producing validation evidence, and creating a final publish checklist. Use when Codex is asked to prepare, verify, summarize, package, or hand off an agent-workflows release."
}

Release Prep

Quick Start

Run scripts/prepare_release_report.py from this skill directory, or by absolute path, to collect release inputs.
Run the workflow-maintainer audit before drafting release notes if that skill is available in this repository.
Read references/release-checklist.md for release judgment checks and final handoff content.
Follow shared safety, validation, and scope rules in ../_shared/references/skill-operating-rules.md.
Do not create tags, commits, pushes, GitHub releases, or package uploads without explicit permission.

Release Workflow

Establish repository state:

python3 scripts/prepare_release_report.py

Run deterministic validation:

python3 ../workflow-maintainer/scripts/audit_workflow_library.py
python3 ../workflow-automation/scripts/find_workflow_library.py --json

Inspect changed files and classify release impact:

major: breaking workflow semantics, renamed files, removed workflows, or incompatible skill behavior.
minor: new workflows, new skills, new checks, or backward-compatible capability additions.
patch: typo fixes, docs clarifications, metadata corrections, non-breaking script fixes.

Draft release notes with:

Summary
User-facing changes
New or changed skills
Validation performed
Breaking changes, if any
Migration notes, if any
Known limitations or follow-ups

Final handoff must state whether commits, tags, pushes, and publish actions were performed. Default answer should be no unless the user explicitly approved them.

Maintenance Rules

Keep release notes factual and tied to observed changes.
Do not invent version numbers if the repo does not define a versioning convention; ask or label the release as “unversioned draft.”
Treat failed audits, broken links, missing required files, stale README inventory, invalid skill metadata, or unvalidated helper scripts as release blockers.
If the working tree is not a Git repository, produce a filesystem-based release report and state that Git diff metadata was unavailable.