メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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 | managing-git-workflow |
| description | 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. |
| user-invocable | false |
| Branch | Purpose | Base |
|---|---|---|
feature/* | New features | develop |
release/* | Release preparation | develop |
hotfix/* | Critical fixes | main |
claude/* | Claude-generated branches | develop |
Conventional commits required: <type>(<scope>): <description>
Types: feat, fix, docs, style, refactor, test, chore
Examples:
feat(message): add CloudEvents validation
fix(router): handle nil handler gracefully
docs: update architecture roadmap
Tag in dependency order — Go proxy resolves from published tags:
channel/vX.Y.Z — no internal dependenciespipe/vX.Y.Z — depends on channelmessage/vX.Y.Z — depends on channel and pipeexamples/vX.Y.Z — optionalPush all at once: git push origin channel/vX.Y.Z pipe/vX.Y.Z message/vX.Y.Z
Always pause and ask for explicit approval before:
make test && make build && make vet before pushgit merge main → develop)--force instead of --force-with-lease)