release

Name: release
Author: basezh

15stars1forks

How to install release?

basezh/agent-skills-on-base/release

$npx -y skills add basezh/agent-skills-on-base --skill release

Installs into the current project.

Summary

Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, blockrun server constant, build, tests, npm publish, git tag, GitHub release. No step can be skipped.

Files · 1

View on GitHub

SKILL.md

1	# ClawRouter Release Checklist
2
3	This skill is mandatory for every release. Execute every step in order. Do not skip.
4
5	## Step 1: Confirm the New Version
6
7	Read the current version:
8
9	```bash
10	cat package.json \| grep '"version"'
11	```
12
13	Ask: "What version are we releasing?" Confirm it follows semver and is higher than current.
14
15	---
16
17	## Step 2: Update `package.json` Version
18
19	Edit `package.json` — bump `"version"` to the new version.
20
21	---
22
23	## Step 3: Write CHANGELOG Entry
24
25	Open `CHANGELOG.md`. Add a new section at the top (after the header) in this format:
26
27	```markdown
28	## v{VERSION} — {DATE}
29
30	- Feature/Fix name — description
31	- Feature/Fix name — description
32	```
33
34	Rules:
35	- Date format: `Mar 8, 2026`
36	- One bullet per logical change
37	- Every bullet must be present — no "see git log"
38	- Include all changes since the previous release
39
40	---
41
42	## Step 4: Sync `CURRENT_CLAWROUTER_VERSION` in blockrun
43
44	This is the most commonly forgotten step.
45
46	File: `/Users/vickyfu/Documents/blockrun-web/blockrun/src/app/api/v1/chat/completions/route.ts`
47
48	Find this line:
49	```typescript
50	const CURRENT_CLAWROUTER_VERSION = "x.y.z";
51	```
52
53	Update it to match the new version. Verify with:
54	```bash
55	grep CURRENT_CLAWROUTER_VERSION /Users/vickyfu/Documents/blockrun-web/blockrun/src/app/api/v1/chat/completions/route.ts
56	```
57
58	Do not skip this. It controls the update nudge shown to users running outdated versions.
59
60	---
61
62	## Step 5: Build
63
64	```bash
65	npm run build
66	```
67
68	Fix any TypeScript or build errors before proceeding.
69
70	---
71
72	## Step 6: Run Tests
73
74	```bash
75	npm test
76	npm run typecheck
77	npm run lint
78	```
79
80	All must pass. Fix failures before proceeding.
81
82	---
83
84	## Step 7: Commit Everything
85
86	Stage and commit:
87
88	```bash
89	git add package.json CHANGELOG.md
90	git commit -m "chore: bump version to {VERSION}"
91	```
92
93	If blockrun's route.ts was updated, commit that separately in the blockrun repo.
94
95	---
96
97	## Step 8: Push to GitHub
98
99	```bash
100	git push origin main
101	```
102
103	---
104
105	## Step 9: Create Git Tag
106
107	```bash
108	git tag v{VERSION}
109	git push origin v{VERSION}
110	```
111
112	---
113
114	## Step 10: Create GitHub Release
115
116	```bash
117	gh release create v{VERSION} \
118	--title "v{VERSION}" \
119	--notes "$(sed -n '/^## v{VERSION}/,/^## v[0-9]/p' CHANGELOG.md \| head -n -1)"
120	```
121
122	Verify the release on GitHub: https://github.com/BlockRunAI/ClawRouter/releases
123
124	The release notes must match the CHANGELOG entry exactly.
125
126	---
127
128	## Step 11: Publish to npm
129
130	```bash
131	npm publish --access public
132	```
133
134	Verify: https://npmjs.com/package/@blockrun/clawrouter
135
136	Expected output: `+ @blockrun/clawrouter@{VERSION}`
137
138	---
139
140	## Step 12: Final Verification
141
142	Run this checklist to confirm everything is in sync:
143
144	```bash
145	# 1. package.json version
146	cat package.json \| grep '"version"'
147
148	# 2. CHANGELOG has the entry
149	head -10 CHANGELOG.md
150
151	# 3. blockrun CURRENT_CLAWROUTER_VERSION
152	grep CURRENT_CLAWROUTER_VERSION /Users/vickyfu/Documents/blockrun-web/blockrun/src/app/api/v1/chat/completions/route.ts
153
154	# 4. npm package is live
155	npm view @blockrun/clawrouter version
156
157	# 5. GitHub tag exists
158	git tag \| grep v{VERSION}
159
160	# 6. GitHub release exists
161	gh release view v{VERSION}
162	```
163
164	All 6 must match the new version. If any mismatch, fix before declaring the release done.
165
166	---
167
168	## Common Mistakes (Never Repeat These)
169
170	\| Mistake \| Prevention \|
171	\|---------\|-----------\|
172	\| Forgot to update `CURRENT_CLAWROUTER_VERSION` in blockrun \| Step 4 — always check \|
173	\| CHANGELOG entry missing or incomplete \| Step 3 — write it before building \|
174	\| npm publish before tests pass \| Steps 5-6 must precede Step 11 \|
175	\| GitHub release notes empty \| Step 10 — extract from CHANGELOG \|
176	\| Git tag not pushed \| Step 9 — push tag separately \|
177	\| docs not reflecting new features \| Update docs in same PR as the feature \|

People who liked this also viewed

6 picks

Type

remotion-to-hyperframesPort an existing Remotion (React) composition''s source to HyperFrames HTML. Use ONLY on an explicit ask to port/convert/migrate/translate a Remotion source — one-way, Remotion-only. A passing RemotioSkillsJul 2026186k37k
solana-devUse when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain SSkillsJul 202648k539
grimoire-polymarketQueries Polymarket market data and CLOB state, and manages CLOB orders via the Grimoire venue CLI wrapper backed by the official Polymarket CLI.SkillsMay 202612k6
shopify-storefront-graphqlUse for custom storefronts requiring direct GraphQL queries/mutations for data fetching and cart operations. Choose this when you need full control over data fetching and rendering your own UI. NOT foSkillsJul 20267.3k463
agentic-walletCrypto wallet operations via the awal CLI — sign in, check balances, send USDC/ETH/POL/SOL, trade tokens, fund the wallet, and use the x402 payment protocol to discover paid services, pay for API callSkillsJun 20261.6k121
quicknode-skillQuicknode blockchain infrastructure for 80+ chains: Core RPC API, Streams, Webhooks, Blazar WSS, Solana gRPC, HyperCore gRPC, SQL Explorer, Metaplex DAS API, Blockbook, Ordinals & Runes API, Swap API,SkillsJul 202621216

release

15stars1forks

View on GitHub

How to install release?

basezh/agent-skills-on-base/release

$npx -y skills add basezh/agent-skills-on-base --skill release

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# ClawRouter Release Checklist
2
3	This skill is mandatory for every release. Execute every step in order. Do not skip.
4
5	## Step 1: Confirm the New Version
6
7	Read the current version:
8
9	```bash
10	cat package.json \| grep '"version"'
11	```
12
13	Ask: "What version are we releasing?" Confirm it follows semver and is higher than current.
14
15	---
16
17	## Step 2: Update `package.json` Version
18
19	Edit `package.json` — bump `"version"` to the new version.
20
21	---
22
23	## Step 3: Write CHANGELOG Entry
24
25	Open `CHANGELOG.md`. Add a new section at the top (after the header) in this format:
26
27	```markdown
28	## v{VERSION} — {DATE}
29
30	- Feature/Fix name — description
31	- Feature/Fix name — description
32	```
33
34	Rules:
35	- Date format: `Mar 8, 2026`
36	- One bullet per logical change
37	- Every bullet must be present — no "see git log"
38	- Include all changes since the previous release
39
40	---
41
42	## Step 4: Sync `CURRENT_CLAWROUTER_VERSION` in blockrun
43
44	This is the most commonly forgotten step.
45
46	File: `/Users/vickyfu/Documents/blockrun-web/blockrun/src/app/api/v1/chat/completions/route.ts`
47
48	Find this line:
49	```typescript
50	const CURRENT_CLAWROUTER_VERSION = "x.y.z";
51	```
52
53	Update it to match the new version. Verify with:
54	```bash
55	grep CURRENT_CLAWROUTER_VERSION /Users/vickyfu/Documents/blockrun-web/blockrun/src/app/api/v1/chat/completions/route.ts
56	```
57
58	Do not skip this. It controls the update nudge shown to users running outdated versions.
59
60	---
61
62	## Step 5: Build
63
64	```bash
65	npm run build
66	```
67
68	Fix any TypeScript or build errors before proceeding.
69
70	---
71
72	## Step 6: Run Tests
73
74	```bash
75	npm test
76	npm run typecheck
77	npm run lint
78	```
79
80	All must pass. Fix failures before proceeding.
81
82	---
83
84	## Step 7: Commit Everything
85
86	Stage and commit:
87
88	```bash
89	git add package.json CHANGELOG.md
90	git commit -m "chore: bump version to {VERSION}"
91	```
92
93	If blockrun's route.ts was updated, commit that separately in the blockrun repo.
94
95	---
96
97	## Step 8: Push to GitHub
98
99	```bash
100	git push origin main
101	```
102
103	---
104
105	## Step 9: Create Git Tag
106
107	```bash
108	git tag v{VERSION}
109	git push origin v{VERSION}
110	```
111
112	---
113
114	## Step 10: Create GitHub Release
115
116	```bash
117	gh release create v{VERSION} \
118	--title "v{VERSION}" \
119	--notes "$(sed -n '/^## v{VERSION}/,/^## v[0-9]/p' CHANGELOG.md \| head -n -1)"
120	```
121
122	Verify the release on GitHub: https://github.com/BlockRunAI/ClawRouter/releases
123
124	The release notes must match the CHANGELOG entry exactly.
125
126	---
127
128	## Step 11: Publish to npm
129
130	```bash
131	npm publish --access public
132	```
133
134	Verify: https://npmjs.com/package/@blockrun/clawrouter
135
136	Expected output: `+ @blockrun/clawrouter@{VERSION}`
137
138	---
139
140	## Step 12: Final Verification
141
142	Run this checklist to confirm everything is in sync:
143
144	```bash
145	# 1. package.json version
146	cat package.json \| grep '"version"'
147
148	# 2. CHANGELOG has the entry
149	head -10 CHANGELOG.md
150
151	# 3. blockrun CURRENT_CLAWROUTER_VERSION
152	grep CURRENT_CLAWROUTER_VERSION /Users/vickyfu/Documents/blockrun-web/blockrun/src/app/api/v1/chat/completions/route.ts
153
154	# 4. npm package is live
155	npm view @blockrun/clawrouter version
156
157	# 5. GitHub tag exists
158	git tag \| grep v{VERSION}
159
160	# 6. GitHub release exists
161	gh release view v{VERSION}
162	```
163
164	All 6 must match the new version. If any mismatch, fix before declaring the release done.
165
166	---
167
168	## Common Mistakes (Never Repeat These)
169
170	\| Mistake \| Prevention \|
171	\|---------\|-----------\|
172	\| Forgot to update `CURRENT_CLAWROUTER_VERSION` in blockrun \| Step 4 — always check \|
173	\| CHANGELOG entry missing or incomplete \| Step 3 — write it before building \|
174	\| npm publish before tests pass \| Steps 5-6 must precede Step 11 \|
175	\| GitHub release notes empty \| Step 10 — extract from CHANGELOG \|
176	\| Git tag not pushed \| Step 9 — push tag separately \|
177	\| docs not reflecting new features \| Update docs in same PR as the feature \|

People who liked this also viewed

6 picks

Type