菜单
Automate a full seedit release by analyzing commits, updating the release body, bumping the version, regenerating the changelog, and finalizing the git tag. Use when the user says "release", "new version", "cut a release", "prepare release", or provides a version number to ship.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/bitsocialnet/seedit --skill release命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Orchestrates implementation of a multi-task plan by spawning plan-implementer subagents in parallel. Use when the user provides a plan file or plan text and asks to implement it, execute it, or says "implement plan", "run plan", "execute plan".
Resolve on-screen seedit DOM elements to React source files, line numbers, component names, and ownership stacks using the app's dev-only element-source helpers and playwright-cli. Use when an agent needs to inspect a page element, map a snapshot ref to source code, confirm which component rendered a node, or follow up after $profile-browsing finds a rerender hotspot and needs file-level attribution.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
| name | release |
| description | Automate a full seedit release by analyzing commits, updating the release body, bumping the version, regenerating the changelog, and finalizing the git tag. Use when the user says "release", "new version", "cut a release", "prepare release", or provides a version number to ship. |
End-to-end release automation for seedit.
The user provides a version bump (patch, minor, major, or explicit x.y.z).
If omitted, ask which bump level they want.
Copy this checklist and track progress:
Release Progress:
- [ ] Step 1: Analyze commits
- [ ] Step 2: Write release body one-liner
- [ ] Step 3: Bump version in package.json
- [ ] Step 4: Generate changelog
- [ ] Step 5: Commit, tag, push
git tag --sort=-creatordate | head -1
Then list commits since that tag:
git log --oneline <tag>..HEAD
If there are no new commits, stop.
Edit oneLinerDescription in scripts/release-body.js.
Rules:
Read package.json, compute the new version from the bump level, and update the "version" field.
| Bump | Effect |
|---|---|
patch | 0.6.7 → 0.6.8 |
minor | 0.6.7 → 0.7.0 |
major | 0.6.7 → 1.0.0 |
x.y.z | Set exactly |
yarn changelog
This regenerates CHANGELOG.md from conventional commits.
git add -A
git commit -m "chore(release): v<version>"
git push
git tag v<version>
git push --tags
If CI is configured to publish release artifacts on tags, pushing the tag will trigger it.
If the user says "dry run" or "preview", execute Steps 1–4 but skip the git operations in Step 5. Print a summary of what would be committed so the user can review it first.