Our review
This skill automates the GitHub release process for the @funstack/router package, including version bumping, committing, and generating release notes.
Strengths
- Fully automates the release workflow
- Generates structured release notes from git log
- Handles semantic versioning bump (patch/minor/major)
- Leverages the gh CLI for seamless GitHub integration
Limitations
- Tailored specifically to @funstack/router
- Requires user confirmation for version type
- Assumes the repository is already set up with git and gh
Use this skill when you need to publish a new version of @funstack/router to GitHub and want a reproducible, automated process.
Avoid this skill if you are working on a different package or if you prefer to manually craft release notes without automated git log analysis.
Security analysis
SafeThe skill only uses allowed tools (git, gh) for a standard release workflow. No destructive commands, no exfiltration, no obfuscation.
No concerns found
Examples
Release a new patch version of @funstack/router.Bump the version to 0.1.0 and create a GitHub release for @funstack/router.Make a new release for the router package, include release notes from recent commits.name: release-funstack
description: A skill to make a GitHub release for the @funstack/router package. Use this skill when the user wants to release a new version of the package.
allowed-tools:
- Read
- Bash(gh:*)
- Bash(git:*) metadata: internal: true
Release FUNSTACK Skill
To release a new version of the @funstack/router package, follow these steps:
- Read the
packages/router/package.jsonfile to determine the current version of the package.
- User may or may not have already updated the version in
package.json. Ask the user to confirm if they have updated the version. If not, you should update the version based on semantic versioning rules (patch, minor, major) as per user's instruction.
- Update the version in
packages/router/package.json, commit and push if necessary.
- The commit message should be
chore: bump version to x.y.zwherex.y.zis the new version.
- Inspect the git log since the last release tag to generate release notes.
- The release notes should summarize the changes made since the last release.
- Especially, highlight any breaking changes, new features, or important fixes.
- Use the
ghCLI to create a new release on GitHub with the new version and the generated release notes.
- The tag name should be
x.y.zwherex.y.zis the new version.
- Inform the user that the release has been created successfully, providing the URL to the release page on GitHub.
Writing Release Notes
When writing release notes, consider the following structure:
## What's Changed
### Breaking Changes
- Change the `onNavigate` signature to accept an `OnNavigateInfo` object instead of the matched array. (#52)
### Features
- Add new hooks `useRouteParams`, `useRouteState` and `useRouteData` for type-safe state management (#50)
### Improvements
- Improve route matching performance by optimizing the matching algorithm (#20)
**Full Changelog**: https://github.com/uhyo/funstack-router/compare/0.0.1...0.0.2
Notes:
- Highlight breaking changes if any.
- Group changes into categories like "Features", "Improvements", "Fixes", etc.
- Documentation updates and dependency updates should be omitted unless they are significant (e.g. breaking changes).
- Provide a link to the full changelog comparing the previous version and the new version.
Docker Compose Architect
DevOps
Designs optimized Docker Compose configurations.
Incident Postmortem Writer
DevOps
Writes structured and blameless incident postmortem reports.
Runbook Creator
DevOps
Creates clear operational runbooks for common DevOps procedures.