Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

managing-git-workflow

Étoiles4

Forks0

Mis à jour10 avril 2026 à 07:29

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.

Installation

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.

Exécuter dans Manus

Source

fxsml

fxsml/gopipe

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

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

Managing Git Workflow

Branch Naming

Branch	Purpose	Base
`feature/*`	New features	develop
`release/*`	Release preparation	develop
`hotfix/*`	Critical fixes	main
`claude/*`	Claude-generated branches	develop

Commit Conventions

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

Multi-Module Tagging

Tag in dependency order — Go proxy resolves from published tags:

channel/vX.Y.Z — no internal dependencies
pipe/vX.Y.Z — depends on channel
message/vX.Y.Z — depends on channel and pipe
examples/vX.Y.Z — optional

Push all at once: git push origin channel/vX.Y.Z pipe/vX.Y.Z message/vX.Y.Z

Approval Gates

Always pause and ask for explicit approval before:

Interactive rebase or history rewrite
Force push to any branch
Merge to develop or main
Creating or pushing tags
Creating GitHub releases

Key Rules

Never merge directly to main — always PRs through develop
Never force push to main or develop
Run make test && make build && make vet before push
Document before push: CHANGELOG, ADRs, godoc

Common Mistakes

Tagging out of order (channel must precede pipe, pipe must precede message)
Forgetting to sync develop after release (git merge main → develop)
Force pushing without lease (--force instead of --force-with-lease)

Reference Procedures

@../docs/procedures/git.md — branch naming, commits, version management
@../docs/procedures/feature-release.md — full merge workflow with approval gates
@../docs/procedures/release.md — tagging, hotfixes, multi-module release

Plus depuis ce dépôt

même dépôt

building-message-pipelines

fxsml/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.

2026-04-104

changelog

fxsml/gopipe

Add an entry to the CHANGELOG under [Unreleased]. Usage: /changelog TYPE DESC (e.g. /changelog Added support for Redis adapter)

2026-04-104

create-adr

fxsml/gopipe

Create a new Architecture Decision Record. Usage: /create-adr TITLE (e.g. /create-adr add-redis-adapter)

2026-04-104

create-feature

fxsml/gopipe

Create a new feature branch from develop. Usage: /create-feature NAME (e.g. /create-feature message-validation)

2026-04-104

create-plan

fxsml/gopipe

Create a new implementation plan document. Usage: /create-plan TITLE (e.g. /create-plan redis-adapter)

2026-04-104

developing-go-code

fxsml/gopipe

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.

2026-04-104

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

Managing Git Workflow

Branch Naming

Branch	Purpose	Base
`feature/*`	New features	develop
`release/*`	Release preparation	develop
`hotfix/*`	Critical fixes	main
`claude/*`	Claude-generated branches	develop

Commit Conventions

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

Multi-Module Tagging

Tag in dependency order — Go proxy resolves from published tags:

channel/vX.Y.Z — no internal dependencies
pipe/vX.Y.Z — depends on channel
message/vX.Y.Z — depends on channel and pipe
examples/vX.Y.Z — optional

Push all at once: git push origin channel/vX.Y.Z pipe/vX.Y.Z message/vX.Y.Z

Approval Gates

Always pause and ask for explicit approval before:

Interactive rebase or history rewrite
Force push to any branch
Merge to develop or main
Creating or pushing tags
Creating GitHub releases

Key Rules

Never merge directly to main — always PRs through develop
Never force push to main or develop
Run make test && make build && make vet before push
Document before push: CHANGELOG, ADRs, godoc

Common Mistakes

Tagging out of order (channel must precede pipe, pipe must precede message)
Forgetting to sync develop after release (git merge main → develop)
Force pushing without lease (--force instead of --force-with-lease)

Reference Procedures

@../docs/procedures/git.md — branch naming, commits, version management
@../docs/procedures/feature-release.md — full merge workflow with approval gates
@../docs/procedures/release.md — tagging, hotfixes, multi-module release