Our review
This skill automates the GitHub release process for the @funstack/router package, including version bumping, release notes generation, and publishing via the gh CLI.
Strengths
- Fully automates the release workflow from version bump to GitHub release creation.
- Generates structured release notes with categorized changes (breaking, features, fixes).
- Follows semantic versioning and good commit/tag practices.
Limitations
- Specific to the @funstack/router package; not reusable without adaptation.
- Requires user confirmation if the version hasn't been updated beforehand.
- Depends on gh CLI and git being properly configured in the environment.
Use this skill when you need to release a new version of @funstack/router with automated changelog generation and GitHub release.
Do not use for other packages, or if you need a more comprehensive CI/CD pipeline including tests or npm deployment.
Security analysis
SafeThe skill instructs standard release tasks: reading package.json, committing version bumps, generating release notes from git logs, and using gh CLI to create releases. All operations are confined to the repository and use explicit, allowed tools (gh, git). No destructive, exfiltrating, or obfuscated actions are present.
No concerns found
Examples
Release a new patch version of @funstack/router.Bump the minor version of @funstack/router and create a GitHub release with release notes.Do a major release of @funstack/router, update version, commit, and create a release with changelog highlighting breaking changes.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.
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.