Menu
Create and release a hotfix branch. Usage: /hotfix NAME (e.g. /hotfix fix-nil-panic)
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Provides expertise in the message package architecture for building CloudEvents-based pipelines in gopipe. Apply when working with the message package, Engine, Router, Handler, Matcher, or designing event-driven systems.
Add an entry to the CHANGELOG under [Unreleased]. Usage: /changelog TYPE DESC (e.g. /changelog Added support for Redis adapter)
Create a new Architecture Decision Record. Usage: /create-adr TITLE (e.g. /create-adr add-redis-adapter)
Create a new feature branch from develop. Usage: /create-feature NAME (e.g. /create-feature message-validation)
Create a new implementation plan document. Usage: /create-plan TITLE (e.g. /create-plan redis-adapter)
Provides Go development standards and best practices for the gopipe codebase. Apply when writing or reviewing Go code: testing patterns, godoc, error handling, API conventions, and common anti-patterns to avoid.
| name | hotfix |
| description | Create and release a hotfix branch. Usage: /hotfix NAME (e.g. /hotfix fix-nil-panic) |
Create and release a hotfix for: $ARGUMENTS
Read the full procedure before starting: @../docs/procedures/release.md
Create hotfix branch:
git checkout main && git pull origin maingit checkout -b hotfix/$ARGUMENTSImplement fix:
3. Explore the issue, implement the minimal fix
4. Add tests if applicable
5. Update CHANGELOG with new version section
6. make check must pass
Commit and PR:
7. Commit with fix: description
8. git push -u origin hotfix/$ARGUMENTS
9. gh pr create --base main --title "fix: description"
Release:
10. PAUSE: ask for approval before merge
11. gh pr merge --merge
12. git checkout main && git pull origin main
13. PAUSE: ask for approval before creating tags
14. Determine next patch version (make version)
15. Create and push module tags in order: channel → pipe → message
16. PAUSE: ask for approval before pushing tags
17. Create GitHub release
18. Merge main back to develop