release

Name: release
Author: Shpigford

1.5kstars93forks

How to install release?

shpigford/chops/release

$npx -y skills add Shpigford/chops --skill release

Installs into the current project.

Summary

Determine the next version, update the marketing site, and run the full release pipeline.

Files · 1

View on GitHub

SKILL.md

1	Cut a new release of Chops. Determines the version from git history, updates the marketing site, and runs the release script.
2
3	## Instructions
4
5	### Step 1: Verify prerequisites
6
7	1. Confirm `.env` exists in the project root. If it does not, stop and tell the user:
8	"Missing `.env` file. Copy `.env.example` to `.env` and fill in APPLE_TEAM_ID, APPLE_ID, and SIGNING_IDENTITY_NAME."
9	2. Confirm the notarytool keychain profile `AC_PASSWORD` works:
10	```bash
11	xcrun notarytool history --keychain-profile "AC_PASSWORD" >/dev/null 2>&1
12	```
13	If it fails, stop and tell the user to run:
14	```bash
15	xcrun notarytool store-credentials "AC_PASSWORD" --apple-id "<APPLE_ID>" --team-id "<TEAM_ID>" --password "<app-specific-password>"
16	```
17	3. Confirm the working tree is clean (`git status --porcelain`). If there are uncommitted changes, stop and tell the user to commit or stash first.
18	4. Confirm you are on the `main` branch. If not, stop and tell the user to switch to `main` first.
19
20	### Step 2: Determine the next version
21
22	1. Get the latest tag:
23	```bash
24	git tag -l 'v*' \| sort -V \| tail -1
25	```
26	2. Get commits since that tag:
27	```bash
28	git log <latest_tag>..HEAD --oneline --format='%s'
29	```
30	3. If there are zero commits since the last tag, stop and tell the user there is nothing to release.
31	4. Apply semver logic to the current latest version:
32	- If any commit message starts with `feat:` or `feat(` → minor bump (e.g. 1.1.0 → 1.2.0)
33	- If all commits are `fix:`, `chore:`, `docs:`, or similar → patch bump (e.g. 1.1.0 → 1.1.1)
34	- If any commit contains `BREAKING CHANGE` or uses a `!:` suffix → ask the user what version to use
35	- If the commit messages are ambiguous or do not follow conventional commits, use `mcp__conductor__AskUserQuestion` to ask:
36	- question: "Commits since the last release don't clearly indicate the version bump. What version should this release be?"
37	- header: "Release version"
38	- multiSelect: false
39	- options with labels: "Patch (X.Y.Z+1)", "Minor (X.Y+1.0)", "Major (X+1.0.0)", "Custom"
40
41	### Step 3: Confirm the version
42
43	Always confirm the version before proceeding. Use `mcp__conductor__AskUserQuestion`:
44	- question: "Release as v<VERSION>? Commits included:\n<commit list>"
45	- header: "Confirm release"
46	- multiSelect: false
47	- options:
48	- "Yes, release v<VERSION>"
49	- "Use a different version"
50	- "Cancel"
51
52	If the user picks "Use a different version", ask them for the version number. If they pick "Cancel", stop.
53
54	### Step 3.5: Update CHANGELOG.md
55
56	1. Check if `CHANGELOG.md` has an `## [Unreleased]` section with content (bullet points).
57	2. If the `## [Unreleased]` section is empty or missing, draft entries from commits since the last tag:
58	- Rewrite each entry to be user-facing. Don't echo commit messages. Describe what changed from the user's perspective — what it enables, fixes, or improves.
59	- Bad: "feat: add skills registry browser with multi-agent install"
60	- Good: "Browse and install community skills directly from the app"
61	- Keep entries succinct (one line each). No technical jargon, no commit prefixes.
62	- Confirm the drafted entries with the user using `mcp__conductor__AskUserQuestion`.
63	3. Rename `## [Unreleased]` to `## [VERSION] - YYYY-MM-DD` (today's date).
64	4. Add a new empty `## [Unreleased]` section above it.
65
66	### Step 4: Update the marketing site version
67
68	1. Edit `site/src/pages/index.astro`. Find the line containing `class="requires"` and replace it with:
69	```html
70	<p class="requires">v<VERSION> · Requires macOS Sequoia</p>
71	```
72	where `<VERSION>` is the confirmed version.
73	2. Commit this change along with the changelog:
74	```bash
75	git add site/src/pages/index.astro CHANGELOG.md
76	git commit -m "chore: update site version to v<VERSION>"
77	git push
78	```
79
80	### Step 5: Run the release script
81
82	```bash
83	./scripts/release.sh <VERSION>
84	```
85
86	This handles: xcodegen → archive → export → DMG → notarize → staple → git tag → appcast → push → GitHub Release.
87
88	Let it run to completion. If it fails, report the error output to the user and stop. Do NOT retry automatically.
89
90	### Step 6: Push and report
91
92	Ensure all commits are on the remote:
93	```bash
94	git push
95	```
96
97	Tell the user:
98	- The version that was released
99	- Link: `https://github.com/Shpigford/chops/releases/tag/v<VERSION>`
100	- Remind them to deploy the marketing site if needed (`npm run build` from `site/`)
101
102	## Important Rules
103
104	- ALWAYS confirm the version with the user before proceeding
105	- NEVER run the release script if `.env` is missing or the working tree is dirty
106	- NEVER skip the marketing site version update
107	- If the release script fails, do NOT retry — report the error and stop
108	- The release script handles git tagging and GitHub release creation — do not duplicate those steps

People who liked this also viewed

6 picks

Type

lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026382k16k
lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026382k16k
lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026380k16k
lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026380k16k
lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026330k16k
lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026227k16k

release

1.5kstars93forks

View on GitHub

How to install release?

shpigford/chops/release

$npx -y skills add Shpigford/chops --skill release

Installs into the current project.

Summary

Determine the next version, update the marketing site, and run the full release pipeline.

Files · 1

View on GitHub

SKILL.md

1	Cut a new release of Chops. Determines the version from git history, updates the marketing site, and runs the release script.
2
3	## Instructions
4
5	### Step 1: Verify prerequisites
6
7	1. Confirm `.env` exists in the project root. If it does not, stop and tell the user:
8	"Missing `.env` file. Copy `.env.example` to `.env` and fill in APPLE_TEAM_ID, APPLE_ID, and SIGNING_IDENTITY_NAME."
9	2. Confirm the notarytool keychain profile `AC_PASSWORD` works:
10	```bash
11	xcrun notarytool history --keychain-profile "AC_PASSWORD" >/dev/null 2>&1
12	```
13	If it fails, stop and tell the user to run:
14	```bash
15	xcrun notarytool store-credentials "AC_PASSWORD" --apple-id "<APPLE_ID>" --team-id "<TEAM_ID>" --password "<app-specific-password>"
16	```
17	3. Confirm the working tree is clean (`git status --porcelain`). If there are uncommitted changes, stop and tell the user to commit or stash first.
18	4. Confirm you are on the `main` branch. If not, stop and tell the user to switch to `main` first.
19
20	### Step 2: Determine the next version
21
22	1. Get the latest tag:
23	```bash
24	git tag -l 'v*' \| sort -V \| tail -1
25	```
26	2. Get commits since that tag:
27	```bash
28	git log <latest_tag>..HEAD --oneline --format='%s'
29	```
30	3. If there are zero commits since the last tag, stop and tell the user there is nothing to release.
31	4. Apply semver logic to the current latest version:
32	- If any commit message starts with `feat:` or `feat(` → minor bump (e.g. 1.1.0 → 1.2.0)
33	- If all commits are `fix:`, `chore:`, `docs:`, or similar → patch bump (e.g. 1.1.0 → 1.1.1)
34	- If any commit contains `BREAKING CHANGE` or uses a `!:` suffix → ask the user what version to use
35	- If the commit messages are ambiguous or do not follow conventional commits, use `mcp__conductor__AskUserQuestion` to ask:
36	- question: "Commits since the last release don't clearly indicate the version bump. What version should this release be?"
37	- header: "Release version"
38	- multiSelect: false
39	- options with labels: "Patch (X.Y.Z+1)", "Minor (X.Y+1.0)", "Major (X+1.0.0)", "Custom"
40
41	### Step 3: Confirm the version
42
43	Always confirm the version before proceeding. Use `mcp__conductor__AskUserQuestion`:
44	- question: "Release as v<VERSION>? Commits included:\n<commit list>"
45	- header: "Confirm release"
46	- multiSelect: false
47	- options:
48	- "Yes, release v<VERSION>"
49	- "Use a different version"
50	- "Cancel"
51
52	If the user picks "Use a different version", ask them for the version number. If they pick "Cancel", stop.
53
54	### Step 3.5: Update CHANGELOG.md
55
56	1. Check if `CHANGELOG.md` has an `## [Unreleased]` section with content (bullet points).
57	2. If the `## [Unreleased]` section is empty or missing, draft entries from commits since the last tag:
58	- Rewrite each entry to be user-facing. Don't echo commit messages. Describe what changed from the user's perspective — what it enables, fixes, or improves.
59	- Bad: "feat: add skills registry browser with multi-agent install"
60	- Good: "Browse and install community skills directly from the app"
61	- Keep entries succinct (one line each). No technical jargon, no commit prefixes.
62	- Confirm the drafted entries with the user using `mcp__conductor__AskUserQuestion`.
63	3. Rename `## [Unreleased]` to `## [VERSION] - YYYY-MM-DD` (today's date).
64	4. Add a new empty `## [Unreleased]` section above it.
65
66	### Step 4: Update the marketing site version
67
68	1. Edit `site/src/pages/index.astro`. Find the line containing `class="requires"` and replace it with:
69	```html
70	<p class="requires">v<VERSION> · Requires macOS Sequoia</p>
71	```
72	where `<VERSION>` is the confirmed version.
73	2. Commit this change along with the changelog:
74	```bash
75	git add site/src/pages/index.astro CHANGELOG.md
76	git commit -m "chore: update site version to v<VERSION>"
77	git push
78	```
79
80	### Step 5: Run the release script
81
82	```bash
83	./scripts/release.sh <VERSION>
84	```
85
86	This handles: xcodegen → archive → export → DMG → notarize → staple → git tag → appcast → push → GitHub Release.
87
88	Let it run to completion. If it fails, report the error output to the user and stop. Do NOT retry automatically.
89
90	### Step 6: Push and report
91
92	Ensure all commits are on the remote:
93	```bash
94	git push
95	```
96
97	Tell the user:
98	- The version that was released
99	- Link: `https://github.com/Shpigford/chops/releases/tag/v<VERSION>`
100	- Remind them to deploy the marketing site if needed (`npm run build` from `site/`)
101
102	## Important Rules
103
104	- ALWAYS confirm the version with the user before proceeding
105	- NEVER run the release script if `.env` is missing or the working tree is dirty
106	- NEVER skip the marketing site version update
107	- If the release script fails, do NOT retry — report the error and stop
108	- The release script handles git tagging and GitHub release creation — do not duplicate those steps

People who liked this also viewed

6 picks

Type