Notre avis
Cette compétence automatise la création d'une release GitHub pour le package @funstack/router, incluant le bump de version, le commit, et la génération des notes de version.
Points forts
- Automatise entièrement le processus de release
- Génère des notes de version structurées à partir du log git
- Gère le bump de version selon les règles semver
- Utilise l'outil gh pour une intégration fluide avec GitHub
Limites
- Spécifique au package @funstack/router uniquement
- Nécessite que l'utilisateur confirme le type de version (patch, minor, major)
- Suppose que le dépôt est déjà configuré avec git et gh
Utilisez cette compétence lorsque vous devez publier une nouvelle version de @funstack/router sur GitHub et voulez un processus reproductible et automatisé.
Évitez cette compétence si vous travaillez sur un autre package ou si vous préférez rédiger manuellement les notes de version sans analyse automatique du log git.
Analyse de sécurité
SûrThe skill only uses allowed tools (git, gh) for a standard release workflow. No destructive commands, no exfiltration, no obfuscation.
Aucun point d'attention détecté
Exemples
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.
Architecte Docker Compose
DevOps
Concoit des configurations Docker Compose optimisees.
Rapport de Post-Mortem
DevOps
Rédige des rapports post-mortem d'incidents structurés et blameless.
Créateur de Runbooks
DevOps
Crée des runbooks opérationnels clairs pour les procédures DevOps courantes.