技能分享发布
- 作者仓库星标 1,897
- 作者仓库 skillshare
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @runkids · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
运行完整的测试套件和代码质量检查。在继续之前修复所有故障。如果测试失败:修复它们,不要跳过。不要询问用户 - 修复并重新运行。
调用`/changelog $VERSION`生成变更日志条目。这处理: 收集自最后一个标签以来的提交 按传统提交类型分类 编写面向用户的 CHANGELOG.md 条目
检查是否以维护者身份运行:如果维护者:读取最新的`specs/RELEASE_NOTES_*.md`作为样式参考,然后生成`specs/RELEASE_NOTES_<version>.md`(无`v`前缀,例如`RELEASE_NOTES_0.19.0.md`)。结构: 标题:`# skillshare vX.Y.Z Release Notes`
更新`skills/skillshare/SKILL.md` frontmatter 中的版本:这可以确保`skillshare upgrade --skill` 正确检测到新版本。
暂时不要推送——等待用户确认。
准备两份草稿供用户审阅: GitHub 发行说明 — 适合 GitHub 发行页面的简洁、面向用户的摘要。比 RELEASE_NOTES 短,用一行行突出显示前 3-5 个更改。社交媒体帖子 — 最多 2-3 句话,随意的语气,提及版本和 1-2 个标题特征。没有主题标签垃圾邮件。语气:短促、直接。不要过度销售。用户将在发布前进行编辑。
向用户显示: [ ] 测试结果(通过/失败) [ ] CHANGELOG.md diff [ ] RELEASE_NOTES 文件(如果生成) [ ] 版本冲突 diff
End-to-end release workflow for skillshare. $ARGUMENTS specifies the version (e.g., `v0.19.0`).
## Prerequisites
- All feature work merged to current branch
- Working directory clean (`git status` shows no uncommitted changes)
## Workflow
### Phase 1: Validate
Run full test suite and code quality checks. Fix any failures before proceeding.
```bash
make check # fmt-check + lint + test (builds binary first)
```
If tests fail: fix them, don't skip. Do not ask the user — fix and re-run.
### Phase 2: Changelog
Invoke `/changelog $VERSION` to generate the changelog entry.
This handles:
- Collecting commits since last tag
- Categorizing by conventional commit type
- Writing user-facing CHANGELOG.md entry
- Syncing website changelog (`website/src/pages/changelog.md`)
Review the output before proceeding.
### Phase 3: Release Notes (Maintainer Only)
Check if running as maintainer:
```bash
git config user.name # Should match "Willie" or maintainer identity
```
**If maintainer**:
Read the most recent `specs/RELEASE_NOTES_*.md` as a style reference, then generate `specs/RELEASE_NOTES_<version>.md` (no `v` prefix, e.g., `RELEASE_NOTES_0.19.0.md`).
Structure:
- Title: `# skillshare vX.Y.Z Release Notes`
- TL;DR section with numbered highlights
- One `##` section per feature/fix — describe **what changed** in plain language, with a CLI example or code block if relevant
- Include migration guide if breaking changes exist
**Wording rules** (same user-facing standard as CHANGELOG):
- Describe **what changed** from the user's perspective, not how the code changed
- **Never mention**: function names, variable names, struct fields, file paths, Go syntax, internal APIs
- ✅ Good: "Sync now auto-creates missing target directories and shows what it did"
- ❌ Bad: "upgraded `Server.mu` from `sync.Mutex` to `sync.RWMutex` and applied a snapshot pattern across 30 handlers"
- Keep it concise — a short paragraph per feature is enough
**If not maintainer**: Skip this phase.
### Phase 4: Version Bump
Update the version in `skills/skillshare/SKILL.md` frontmatter:
```yaml
metadata:
version: vX.Y.Z
```
This ensures `skillshare upgrade --skill` detects the new version correctly.
### Phase 5: Commit & Tag
```bash
git add -A
git commit -m "chore: release vX.Y.Z"
git tag vX.Y.Z
```
Do NOT push yet — wait for user confirmation.
### Phase 6: Draft Announcements
Prepare two drafts for user review:
1. **GitHub Release Notes** — concise, user-facing summary suitable for the GitHub release page. Shorter than RELEASE_NOTES, highlight top 3-5 changes with one-liners.
2. **Social media post** — 2-3 sentences max, casual tone, mention the version and 1-2 headline features. No hashtag spam.
**Tone**: short, direct. Don't oversell. The user will edit before posting.
### Phase 7: Present & Confirm
Show the user:
- [ ] Test results (pass/fail)
- [ ] CHANGELOG.md diff
- [ ] RELEASE_NOTES file (if generated)
- [ ] Version bump diff
- [ ] GitHub release draft
- [ ] Social media draft
Wait for user approval before pushing:
```bash
git push origin HEAD --tags
```
## Rules
- **Fix, don't skip** — if tests fail, fix them before continuing
- **User perspective** — all written output is for users, not developers
- **Short drafts** — announcements default to concise; user will ask for more detail if needed
- **No fabricated links** — never invent URLs or references
- **Verify before claiming** — grep source before stating a feature exists
- **Ask before push** — never push or publish without explicit user confirmation
- **Commit message** — always `chore: release vX.Y.Z`
- **No competitive references** — never mention competitor repos in commit messages or notes
按说明文件中的顺序排列。
先决条件
第一阶段:验证
第 2 阶段:变更日志
第 3 阶段:发行说明(仅限维护人员)
第四阶段:版本更新
文件/命令 -> v0.19.0 · git status · /changelog $VERSION · website/src/pages/changelog.md · specs/RELEASE_NOTES_*.md · specs/RELEASE_NOTES_<version>.md · prefix, e.g., · # skillshare vX.Y.Z Release Notes
内容校验值 -> a00f83ea86da
当前原文的自动摘译,尚未人工审校。
先决条件
所有功能工作都合并到当前分支 工作目录干净(
git status显示没有未提交的更改)