release
Installation
SKILL.md
Release Workflow
Follow this workflow for the current repository.
Prepare changelog draft
- Run
./scripts/get-changes-since-tag.sh. - Categorize changes into these sections as needed:
Added,Changed,Deprecated,Removed,Fixed,Security,Thanks. - Use script output rules:
- Use GitHub username from script output.
- Exclude
yoshiko-pgandrenovate[bot]fromThanks. - Include PR numbers when available.
- Use commit subject and body for categorization.
- Consolidate routine dependency-only updates, including grouped dependency updates, package manager bumps, and ordinary individual dependency bumps, into a single
Changedbullet formatted as- Update dependencies (#123 #124 #125); keep a separate bullet only when the dependency change is clearly user-facing beyond routine maintenance.
- Write the categorized content into
CHANGELOG.mdunder## [Unreleased]. - Ask for user confirmation in Japanese.
Release after explicit OK
Related skills
More from yoshiko-pg/difit
difit
Ask the user for a code review through difit after code changes.
1.1Kdifit-review
A skill for reviewing a specific diff and showing the findings as comments inside difit (the diff viewer). Use it to review branch diffs, commit diffs, or GitHub PRs, then preload findings or code explanations into difit with `--comment` before launching it for the user.
737difit-dev
Ask the user for a code review through difit after code changes in this repository, using `pnpm run dev`.
15vscode-release
Execute the VS Code extension release workflow when the user asks to publish/release the difit VS Code extension. Run local VSIX build and smoke verification first, ask for explicit OK in Japanese, then publish with vsce.
14