release · m1heng — Claude Code skill: what it does, how to install
release automates publishing the @m1heng-clawd/feishu package by running TypeScript checks, drafting GitHub notes, tagging commits, and pushing to npm.
MIT 111 installs ★ 4,217 updated 2026-03-29
npx skills add m1heng/clawdbot-feishu --skill release -a claude-codeWhat release does
The skill manages the full release sequence for the Feishu plugin. It inspects recent commits and diff stats using gh release list and git log to decide on a patch, minor, or major version bump. Next, it runs npx tsc --noEmit. The workflow stops immediately if type checking fails.
The assistant drafts release notes on GitHub with dedicated sections for Features, Bug Fixes, and Internal changes. It updates package.json, creates a Git tag, pushes the commits to main, and runs npm publish. Finally, it marks the GitHub draft release as published.
Publishing fails without an active npm login session that has write permissions for @m1heng-clawd and an authenticated gh CLI. All local modifications must be committed to main before starting.
What it helps with
- verify TypeScript types with
npx tsc --noEmitbefore cutting a release - draft structured GitHub release notes based on git diffs
- bump version in
package.json, tag the release, and push to git - publish the package to npm under the
@m1heng-clawdscope
Example prompts for the agent
- Publish a new release of the Feishu plugin
- Cut a patch release and publish to npm
- Release a new version of
@m1heng-clawd/feishu
How to install release
1Skills CLI (Vercel)
npx skills add m1heng/clawdbot-feishu --skill release -a claude-code2Manually: put the files in place
~/.claude/skills/release/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/release/
1Skills CLI (Vercel)
npx skills add m1heng/clawdbot-feishu --skill release -a codex2Manually: put the files in place
.agents/skills/release/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add m1heng/clawdbot-feishu --skill release -a cursor2Manually: put the files in place
.cursor/skills/release/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install m1heng/clawdbot-feishu .claude/skills/release2Manually: put the files in place
.github/skills/release/SKILL.md1Skills CLI (Vercel)
npx skills add m1heng/clawdbot-feishu --skill release -a gemini-cli2Platform CLI
gemini skills install https://github.com/m1heng/clawdbot-feishu --path .claude/skills/releaseManually: put the files in place
.devin/skills/release/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add m1heng/clawdbot-feishu --skill release -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about release
How do I install release in Claude Code?
Run npx skills add m1heng/clawdbot-feishu --skill release -a claude-code. The file will be placed in ~/.claude/skills/release/SKILL.md.
What does the release skill do?
It guides the agent through TypeScript type checking, package.json version bumping, Git tagging, and publishing to both npm and GitHub Releases.
What are the prerequisites before publishing?
You need a clean working tree committed to main. You also need an authenticated gh CLI and an active npm login session with publish access to @m1heng-clawd.
Source text
SKILL.md · MIT
--- name: release description: Publish a new release of the Feishu plugin. Use when the user asks to release, publish, or cut a new version. allowed-tools: Bash(npm version:*), Bash(npm publish:*), Bash(npx tsc:*), Bash(gh release:*), Bash(git tag:*), Bash(git push:*) --- # Release Workflow Publish a new version of `@m1heng-clawd/feishu` to npm and create a GitHub release. ## Prerequisites - Working tree is clean (all changes committed to `main`) - `npm login` session is active with publish access to `@m1heng-clawd` scope - `gh` CLI is authenticated ## Steps ### 1. Determine version bump Check what changed since the last release: ```bash # Find latest release tag gh release list --limit 1 # Review commits and diff stat git log <last-tag>..HEAD --oneline git diff <last-tag>..HEAD --stat ``` Choose bump type: `patch` (bug fixes), `minor` (new features), or `major` (breaking changes). ### 2. Type check ```bash npx tsc --noEmit ``` Do NOT proceed if type check fails. ### 3. Draft release notes Review the full diff to write release notes: ```bash git diff <last-tag>..HEAD ``` Create a GitHub release **draft** first: ```bash gh release create v<new-version> --draft --title "v<new-version>" --target main --notes "<release notes markdown>" ``` ### 4. Bump version in package.json Edit `package.json` to update the `"version"` field to `<new-version>`. ### 5. Commit, tag, and push ```bash git add package.json git commit -m "chore: bump version to <new-version>" git tag v<new-version> git push && git push --tags ``` ### 6. Publish to npm ```bash npm publish ``` If auth fails, ask the user to run `npm login` first, then retry. ### 7. Publish GitHub release ```bash gh release edit v<new-version> --draft=false ``` ## Release Notes Format Follow the established format (see previous releases for reference): ```markdown ## Features - **Feature title** — Description. (#PR) ## Bug Fixes - **Fix title** — Description. (#PR) ## Internal - Internal change description. ``` ## Troubleshooting ### npm publish 404 / auth error ```bash npm login # re-authenticate npm whoami # verify logged in npm publish # retry ``` ### Tag already exists If the tag was created but publish failed, delete and recreate after fixing: ```bash git tag -d v<version> git push origin :refs/tags/v<version> # fix issue, then re-tag and push ```
© m1heng · MIT · m1heng/clawdbot-feishu
Similar skills
All skills for Git and GitHub →release by other authors comes first.