/release
Update CHANGELOG.md with all changes from the latest tag to current commit.
$ npx -y skills add yoshiko-pg/difit --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/release
Context preview
What this command does when you run it.
Update CHANGELOG.md with all changes from the latest tag to current commit.
Command definition
release.mdUpdate CHANGELOG.md with all changes from the latest tag to current commit.
First, run the script to get commit information:
./scripts/get-changes-since-tag.sh
Use the script output to categorize changes:
- `Added` for new features.
- `Changed` for changes in existing functionality.
- `Deprecated` for soon-to-be removed features.
- `Removed` for now removed features.
- `Fixed` for any bug fixes.
- `Security` in case of vulnerabilities.
- `Thanks` for contributors mention with GitHub username and PR number
When processing commits: 1. Use the GitHub username from script output (not git commit author names) 2. Only include contributors in Thanks section (exclude yoshiko-pg as that's the maintainer, and exclude renovate[bot]) 3. Include PR numbers when available 4. Use commit subject and body to properly categorize changes
Write the categorized changes to the Unreleased section of CHANGELOG.md, then inform the user in Japanese and ask for confirmation. (Don't just output the changes - write them to the file first so the user can review the actual file.)
If confirmed OK:
- npm version --no-git-tag-version patch
- Treat the Unreleased section *as-is* at the time of user OK as the single source of truth. Do not regenerate, re-categorize, or overwrite it after the OK signal.
- Create a version section in CHANGELOG.md and move Unreleased section content there
- Update the version links at the bottom of CHANGELOG.md (add new version links and update Unreleased link)
- Commit CHANGELOG.md
- create current version git tag
- git push origin main --tags
- create release on github with CHANGELOG.md target version section text (to origin)
Read more
Update CHANGELOG.md with all changes from the latest tag to current commit.
First, run the script to get commit information:
./scripts/get-changes-since-tag.sh
Use the script output to categorize changes:
- `Added` for new features.
- `Changed` for changes in existing functionality.
- `Deprecated` for soon-to-be removed features.
- `Removed` for now removed features.
- `Fixed` for any bug fixes.
- `Security` in case of vulnerabilities.
- `Thanks` for contributors mention with GitHub username and PR number
When processing commits: 1. Use the GitHub username from script output (not git commit author names) 2. Only include contributors in Thanks section (exclude yoshiko-pg as that's the maintainer, and exclude renovate[bot]) 3. Include PR numbers when available 4. Use commit subject and body to properly categorize changes
Write the categorized changes to the Unreleased section of CHANGELOG.md, then inform the user in Japanese and ask for confirmation. (Don't just output the changes - write them to the file first so the user can review the actual file.)
If confirmed OK:
- npm version --no-git-tag-version patch
- Treat the Unreleased section *as-is* at the time of user OK as the single source of truth. Do not regenerate, re-categorize, or overwrite it after the OK signal.
- Create a version section in CHANGELOG.md and move Unreleased section content there
- Update the version links at the bottom of CHANGELOG.md (add new version links and update Unreleased link)
- Commit CHANGELOG.md
- create current version git tag
- git push origin main --tags
- create release on github with CHANGELOG.md target version section text (to origin)
A lightweight command-line tool that spins up a local web server to display Git commit diffs in a GitHub-like Files changed view
Repo: yoshiko-pg/difit