release
starsforks
How to install release?
borda/ai-rig/release
$npx -y skills add Borda/AI-Rig --skill releasePrepare release communication and check readiness. Main mode: notes with optional flags --changelog, --summary, --migration; range as v1->v2. Other modes: prepare (full pipeline: audit → all artifacts), audit (pre-release readiness: blockers, docs alignment, version consistency,
SKILL.md
| 1 | <objective> |
| 2 | |
| 3 | Prepare release communication from changes. Output adapts to audience — user-facing notes, CHANGELOG entry, internal summary, migration guide. |
| 4 | |
| 5 | **All outputs = documentation artifacts** (CHANGELOG.md, DRAFT.md, MIGRATION.md, SUMMARY.md, demo.py). Released product = code/package published separately via project tooling (`git tag`, `gh release create`, PyPI upload). Skill prepares communication; doesn't perform release. |
| 6 | |
| 7 | NOT for ecosystem impact without release (use oss:analyse (requires `oss` plugin)). NOT for contributor communication or post-release announcements (use oss:shepherd (requires `oss` plugin)). NOT for retrospective analysis — historical review → oss:analyse (requires `oss` plugin). |
| 8 | |
| 9 | </objective> |
| 10 | |
| 11 | <inputs> |
| 12 | |
| 13 | Mode comes **first**; range or flags follow: |
| 14 | |
| 15 | | Invocation | Arguments | Writes to disk | |
| 16 | | --- | --- | --- | |
| 17 | | `/release [notes] [range]` | optional range (default: last-tag..HEAD); use `v1->v2` for explicit range | `DRAFT.md` | |
| 18 | | `/release notes [range] --changelog` | optional range + flag | `DRAFT.md` + prepends `CHANGELOG.md` | |
| 19 | | `/release notes [range] --summary` | optional range + flag | `DRAFT.md` + `.temp/output-release-summary-<branch>-<date>.md` | |
| 20 | | `/release notes [range] --migration` | optional range + flag | `DRAFT.md` + `.temp/output-release-migration-<branch>-<date>.md` | |
| 21 | | `/release notes [range] --changelog --summary --migration` | all flags | All four outputs | |
| 22 | | `/release prepare <version>` | version to stamp, e.g. `v1.3.0` | All artifacts in `releases/<version>/`: `DRAFT.md` + `CHANGELOG.md` + `SUMMARY.md` + `MIGRATION.md` + `demo.py` | |
| 23 | | `/release audit [version]` | optional target version | Terminal readiness report; emits `verdict: READY | NEEDS_ATTENTION | BLOCKED` as final line for orchestrator consumption | |
| 24 | | `/release demo [range]` | optional range (default: last-tag..HEAD) | `releases/<version>/demo.py` or `.temp/release-demo-<branch>-<date>.py` | |
| 25 | |
| 26 | Range notation: `v1->v2` (e.g. `v1.2->v2.0`) — converted internally to git range. No mode → defaults to `notes`. `prepare` = full pipeline — runs audit first, then all artifacts; use when cutting release, not drafting. |
| 27 | </inputs> |
| 28 | |
| 29 | <workflow> |
| 30 | |
| 31 | **Task hygiene**: Call `TaskList`; triage found tasks (`completed` / `deleted` / `in_progress`). |
| 32 | |
| 33 | **Task tracking** — create ALL tasks upfront, execute sequentially; mark completed as each phase finishes. After mode detection, mark inapplicable tasks `deleted`: |
| 34 | - `demo` mode: mark deleted — Classify each change, Classify breaking changes, Validate migration docs, Audit changelog, Extract contributors, Draft migration guide, Draft executive summary, Write release draft |
| 35 | - bug-fix-only release (no 🚀 Added items): mark deleted — Generate release demo |
| 36 | |
| 37 | Tasks: |
| 38 | - Gather changes (git log + find common base tag) |
| 39 | - Explore codebase (changed files, impl detail) |
| 40 | - Validate docs alignment |
| 41 | - Classify each change |
| 42 | - Classify breaking changes (codemap-gated; skip without index) |
| 43 | - Validate migration docs (skip when no migration doc found) |
| 44 | - Audit changelog |
| 45 | - Extract contributors |
| 46 | - Identify highlights |
| 47 | - Draft migration guide |
| 48 | - Generate release demo (feature releases only) |
| 49 | - Draft executive summary |
| 50 | - Write release draft |
| 51 | |
| 52 | **Sequential enforcement**: never begin phase until prior marked `completed`. On failure (empty range, git error, demo fail), stop and report — no downstream phases. |
| 53 | |
| 54 | ## Delegation strategy |
| 55 | |
| 56 | In `prepare` and `audit` modes, delegate gather/explore/validate to subagent via file-based handoff (CLAUDE.md §2) — these phases produce large output, bloat main context: |
| 57 | |
| 58 | 1. Pre-compute gather file path and create dir: |
| 59 | ```bash |
| 60 | # BRANCH, DATE from Shared setup below |
| 61 | GATHER_FILE=".temp/release-gather-$BRANCH-$DATE.md" |
| 62 | mkdir -p .temp # timeout: 5000 |
| 63 | ``` |
| 64 | 2. Assert variables |
People who liked this also viewed
6 picksType
- lark-openapi-explorer飞书/Lark 原生 OpenAPI 探索：从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足，需要查找并调用原生飞书 OpenAPI 时使用。SkillsJul 2026
- lark-skill-maker创建 lark-cli 的自定义 Skill。当用户需要把飞书 API 操作封装成可复用的 Skill（包装原子 API 或编排多步流程）时使用。SkillsJul 2026
- azure-cost-optimizationOfficial agent plugin providing skills and MCP server configurations for Azure scenarios.SkillsJul 2026
- vercel-react-native-skillsVercel's official collection of agent skillsSkillsJul 2026
- mcp-builderGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate externaSkillsJul 2026
- gws-sharedgws CLI: Shared patterns for authentication, global flags, and output formatting.SkillsJul 2026
