메뉴
Ship a GoPost GitHub release (notes, tag, push, CI assets) using the repo's established v1.x.0 pattern. Use when the user asks to release, cut a version, tag, publish release notes, or run scripts/release.sh.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with Prometheus runtime metrics. Also use when the developer needs deep analysis on a specific performance indicator - this skill provides the measurement methodology, while `samber/cc-skills-golang@golang-performance` provides the optimization patterns.
Golang concurrency patterns. Use when writing or reviewing concurrent Go code involving goroutines, channels, select, locks, sync primitives, errgroup, singleflight, worker pools, or fan-out/fan-in pipelines. Also triggers when you detect goroutine leaks, race conditions, channel ownership issues, or need to choose between channels and mutexes.
Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing Go data structures, implementing generic containers, using container/ packages, unsafe or weak pointers, or questioning slice/map internals.
Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture, setting up dependency injection, refactoring tightly coupled code, managing singletons or service factories, or when the user asks about inversion of control, service containers, or wiring dependencies in Go. For a specific DI library, → See `samber/cc-skills-golang@golang-google-wire`, `samber/cc-skills-golang@golang-uber-dig`, `samber/cc-skills-golang@golang-uber-fx`, or `samber/cc-skills-golang@golang-samber-do` skills.
Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices. Triggers for both libraries and applications/CLIs.
Compile-time dependency injection in Golang using google/wire — wire.NewSet, wire.Build, wire.Bind (interface→concrete), wire.Struct, wire.Value, wire.InterfaceValue, wire.FieldsOf, cleanup functions, //go:build wireinject injector files, and generated wire_gen.go. Apply when using or adopting google/wire, when the codebase imports `github.com/google/wire`, or when wiring an application graph at compile time via `wire.Build`. For runtime DI with reflection, see `samber/cc-skills-golang@golang-uber-dig` skill.
| name | release-gopost |
| description | Ship a GoPost GitHub release (notes, tag, push, CI assets) using the repo's established v1.x.0 pattern. Use when the user asks to release, cut a version, tag, publish release notes, or run scripts/release.sh. |
Do not improvise the release process. Use scripts/release.sh + docs/releases/.
vMAJOR.MINOR.PATCH (historically always v1.x.0 minor bumps)../scripts/release.sh nextvX.Y.Z — short, comma-separated keywords (match prior releases).Copy and track:
Release Progress:
- [ ] Diff since last tag understood (commits + uncommitted work)
- [ ] Notes drafted at docs/releases/vX.Y.Z.md
- [ ] Code + notes committed on main
- [ ] Tests: go test ./app/pkg/... -race && (cd frontend && npm test)
- [ ] ./scripts/release.sh ship X.Y.Z
- [ ] Release URL returned; assets present
./scripts/release.sh next
Title keywords = 3–6 user-facing phrases (e.g. send without save, scratch requests, virtualized responses).
./scripts/release.sh prepare 1.10.0 "keyword one, keyword two"
Edit docs/releases/vX.Y.Z.md:
### subsections + short prose (see docs/releases/v1.9.0.md / v1.8.0 GH release).<!-- title: vX.Y.Z — keywords -->Do not invent a new notes layout.
mainCommit message style (match history):
v1.10.0 — keyword one, keyword two
- Bullet of user-facing change
- Bullet of user-facing change
- Fix: …
Include docs/releases/vX.Y.Z.md in the same commit (or an immediately prior commit on main).
Working tree must be clean; branch must be main:
./scripts/release.sh ship 1.10.0
This tags, pushes main + tag, waits for .github/workflows/release.yml, and sets the GH release title/body from the notes file.
CI builds macOS dmg, Windows exe, CLI archives, checksums, and attaches them. Notes come from body_path: docs/releases/<tag>.md — do not hand-paste boilerplate into the workflow.
gh release view vX.Y.Z --json url,name,assets --jq '{url,name,assets:[.assets[].name]}'
Expect ~8 assets including GoPost-v*-macOS.dmg, GoPost.exe, CLI tarballs/zip, checksums.txt.
Mirror docs/releases/_TEMPLATE.md and the latest docs/releases/v*.md:
## GoPost vX.Y.Z<details> What's New with emoji section headersvX.Y.Z with Z≠0.--force tags.frontend/dist, wails3 dev, local testserver) belong in contributor docs, not release notes, unless they are user-facing fixes..github/workflows/release.ymlscripts/release.shdocs/releases/task release -- prepare … / task release -- ship …