with one click
update-release-notes
Update release_notes.json for the new version.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Update release_notes.json for the new version.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | update-release-notes |
| description | Update release_notes.json for the new version. |
Update release_notes.json in the project root based on feat: and fix: commits after the previous git tag.
git tag --list 'v*' --sort=-v:refname | head -n 1.git log {previous_tag}..HEAD --pretty=format:%s.feat: or fix:.
chore:, refactor:, docs:, test:, and ci:.・.release_notes.json with this exact top-level structure:[
{
"language": "en-US",
"text": "..."
},
{
"language": "ja",
"text": "..."
}
]
Use this skill when creating a git commit.
Use this skill when creating a git commit.
Bump the app version in pubspec.yaml. Accepts optional argument: major, minor (default), or patch. Build number is always set to 1.
Create a GitHub Release from an existing git tag. Uses the latest tag by default, or accepts a tag name as argument.
Create a git tag from the current version in pubspec.yaml. Format: v{MAJOR}.{MINOR}.{PATCH}.