gopipe

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.

Check documentation quality and consistency across the project.

Create and release a hotfix branch. Usage: /hotfix NAME (e.g. /hotfix fix-nil-panic)

Provides expertise in git flow procedures for the gopipe multi-module Go repository. Apply when working with git operations, branch management, releases, or multi-module tagging. Covers branch naming, commit conventions, approval gates, and tag ordering.

Merge a feature branch to develop following the git flow procedure (history cleanup, PR, verify).

Release develop to main with multi-module tags and GitHub release. Usage: /release VERSION (e.g. /release v0.13.0)

Review a pull request against gopipe project standards. Usage: /review-pr [NUMBER] (omit for current branch PR)

Run the full pre-push verification suite (make test, build, vet).