trove-release-notes
Release notes generator. Creates user-facing release notes from git history, PR descriptions, and changelog entries. Use when: release notes; draft a changelog; what shipped; update changelog.
- License 许可
- MIT
- 所属仓库
- bravew/trove
- 最近更新
- 2026-11-12
- Stars
- ★ 10
- Forks
- 1
01 前言 Front Matter
- name
- trove-release-notes
- description
- Release notes generator. Creates user-facing release notes from git history, PR descriptions, and changelog entries. Use when: release notes; draft a changelog; what shipped; update changelog.
03 SKILL.md 正文
<!-- AUTO-GENERATED from SKILL.md.tmpl — do not edit directly --> <!-- Regenerate: bun run build:skills -->
Session Init
This skill ships Trove conventions. Prefer existing project patterns over generic best practices when they conflict.
Release Notes Conventions
Format
# Release [version] — [date]
## Highlights
One-paragraph summary of the most impactful changes.
## New Features
- **[Feature Name]** — Brief description of what users can now do
## Improvements
- **[Area]** — What got better and why it matters
## Bug Fixes
- Fixed [issue] where [symptom] occurred when [trigger]
## Breaking Changes
- **[Change]** — What changed, migration steps
## Known Issues
- [Issue] — workaround if available
Writing Guidelines
- Write for users, not developers
- Lead with benefits, not implementation details
- Use active voice ("You can now..." not "Added ability to...")
- Group related changes together
- Include screenshots/GIFs for visual changes
Changelog Updates
When asked to update CHANGELOG.md, derive the version from the repo's
existing versioning policy. For Trove CalVer, use YY.M.DD and append
.patch only when a release for the same date already exists. Insert the new
section directly below the changelog title, include only sections supported by
the actual git history, and commit only when the user explicitly asked for a
commit.
04 同仓库更多 Skills
using-trove
Skill discipline anchor for the Trove marketplace. Loaded once per session; routes the agent to the right trove-* skill before code, planning, review, or git actions.
trove-write-skill
Skill authoring workflow. Use when creating or updating a Codex or Trove skill, including rubrics, tasks, metadata, and validation.
trove-worktree
Git worktree workflow for spikes, risky experiments, and broad refactors that should not disturb the user's current branch.
trove-why
Reconstruct design rationale and decision history from evidence — source control, issue tracker (Linear), docs (Notion), chat (Slack), error tracking (Sentry) — with calibrated confidence. Use for "why does X work this way", "why did we pick Y", regressions, and postmortems. Use trove-explain for how it works now.
trove-verify
Completion verification workflow. Use before claiming done, fixed, complete, ready, or shipped.
trove-unslop
Cut AI tells from writing — PR descriptions, release notes, specs, commit bodies, and replies. Use before finalizing prose, or when the user asks to clean up, de-slop, or make text sound human.