Menu
Release develop to main with multi-module tags and GitHub release. Usage: /release VERSION (e.g. /release v0.13.0)
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 | release |
| description | Release develop to main with multi-module tags and GitHub release. Usage: /release VERSION (e.g. /release v0.13.0) |
Execute Phases 4–6 of the Feature Branch Release Procedure for version: $ARGUMENTS
Read the full procedure before starting: @../docs/procedures/release.md
Phase 4 — Merge to main:
git diff vOLD..HEAD -- channel/ pipe/gh pr create --base main --head develop --title "release: VERSION"gh pr merge --mergePhase 5 — Tag and release:
git checkout main && git pull origin mainchannel/VERSION, pipe/VERSION, message/VERSIONgh release create VERSION --title "VERSION" --notes "..."Phase 6 — Post-release:
git checkout develop && git merge main && git push origin developgo list -m github.com/fxsml/gopipe/channel@VERSION