[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79ZEXDBH1P8YN8VSEA1PAEM":3,"skill-same:01M79ZEXDBH1P8YN8VSEA1PAEM":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":59},"01M79ZEXDBH1P8YN8VSEA1PAEM","golang-concurrency",null,"Golang concurrency design — goroutine lifecycle and leak prevention, channels and `select`, channel ownership and direction, `sync.Mutex`\u002F`RWMutex`\u002F`sync.Map`\u002F`sync.Once`\u002Fatomics, `errgroup`, `singleflight`, worker pools, and fan-out\u002Ffan-in pipelines. Use when writing or reviewing concurrent Go code, when choosing between channels and mutexes, when protecting a shared map or counter, or when a goroutine has no clear exit. Not for defensive coding unrelated to concurrency such as nil panics, slice aliasing, or numeric overflow (→ See `samber\u002Fcc-skills-golang@golang-safety` skill), and not for debugging a specific hung, crashing, or racing program after the fact (→ See `samber\u002Fcc-skills-golang@golang-troubleshooting` skill).","kongnakornna\u002Fgolangapi","kongnakornna","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10528904?v=4","01M79Z5JQPPV5CWQHXS235Q9MD","Kongnakorn Jantakun","01M79Z5JRHJJJ6PR2DGQS4P985",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-concurrency\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: golang-concurrency\ndescription: \"Golang concurrency design — goroutine lifecycle and leak prevention, channels and `select`, channel ownership and direction, `sync.Mutex`\u002F`RWMutex`\u002F`sync.Map`\u002F`sync.Once`\u002Fatomics, `errgroup`, `singleflight`, worker pools, and fan-out\u002Ffan-in pipelines. Use when writing or reviewing concurrent Go code, when choosing between channels and mutexes, when protecting a shared map or counter, or when a goroutine has no clear exit. Not for defensive coding unrelated to concurrency such as nil panics, slice aliasing, or numeric overflow (→ See `samber\u002Fcc-skills-golang@golang-safety` skill), and not for debugging a specific hung, crashing, or racing program after the fact (→ See `samber\u002Fcc-skills-golang@golang-troubleshooting` skill).\"\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code, Codex or similar harness, and for projects using Golang.\nmetadata:\n  author: samber\n  version: \"1.2.1\"\n  openclaw:\n    emoji: \"⚡\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\n    requires:\n      bins:\n        - go\n    install: []\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent AskUserQuestion\npaths:\n  - \"**\u002F*.go\"\n---\n\n**Persona:** You are a Go concurrency engineer. You assume every goroutine is a liability until proven necessary — correctness and leak-freedom come before performance.\n\n**Orchestration mode:** Fan out the five sub-agents described in the \"Parallelizing Concurrency Audits\" section for auditing concurrent code across a large codebase, and consolidate their findings into one report. On Claude Code, use `ultracode` to opt into multi-agent orchestration explicitly.\n\n**Modes:**\n\n- **Write mode** — implement concurrent code (goroutines, channels, sync primitives, worker pools, pipelines). Follow the sequential instructions below.\n- **Review mode** — reviewing a PR's concurrent code changes. Focus on the diff: check for goroutine leaks, missing context propagation, ownership violations, and unprotected shared state. Sequential.\n- **Audit mode** — auditing existing concurrent code across a codebase. Use up to 5 parallel sub-agents as described in the \"Parallelizing Concurrency Audits\" section.\n\n> **Community default.** A company skill that explicitly supersedes `samber\u002Fcc-skills-golang@golang-concurrency` skill takes precedence.\n\n# Go Concurrency Best Practices\n\nGo's concurrency model is built on goroutines and channels. Goroutines are cheap but not free — every goroutine you spawn is a resource you must manage. The goal is structured concurrency: every goroutine has a clear owner, a predictable exit, and proper error propagation.\n\n## Core Principles\n\n1. **Every goroutine must have a clear exit** — without a shutdown mechanism (context, done channel, WaitGroup), they leak and accumulate until the process crashes\n2. **Share memory by communicating** — channels transfer ownership explicitly; mutexes protect shared state but make ownership implicit\n3. **Send copies, not pointers** on channels — sending pointers creates invisible shared memory, defeating the purpose of channels\n4. **Only the sender closes a channel** — closing from the receiver side panics if the sender writes after close\n5. **Specify channel direction** (`chan\u003C-`, `\u003C-chan`) — the compiler prevents misuse at build time\n6. **Default to unbuffered channels** — larger buffers mask backpressure; use them only with measured justification\n7. **Always include `ctx.Done()` in select** — without it, goroutines leak after caller cancellation\n8. **Avoid repeated `time.After` in hot loops** — each call allocates a timer and creates unnecessary churn; use `time.NewTimer` + `Reset` for long-running loops\n9. **Track goroutine leaks in tests** with `go.uber.org\u002Fgoleak`\n\nFor detailed channel\u002Fselect code examples, see [Channels and Select Patterns](references\u002Fchannels-and-select.md).\n\n## Channel vs Mutex vs Atomic\n\n| Scenario | Use | Why |\n| --- | --- | --- |\n| Passing data between goroutines | Channel | Communicates ownership transfer |\n| Coordinating goroutine lifecycle | Channel + context | Clean shutdown with select |\n| Protecting shared struct fields | `sync.Mutex` \u002F `sync.RWMutex` | Simple critical sections |\n| Simple counters, flags | `sync\u002Fatomic` | Lock-free, lower overhead |\n| Many readers, few writers on a map | `sync.Map` | Optimized for read-heavy workloads. **Concurrent map read\u002Fwrite causes a hard crash** |\n| Caching expensive computations | `sync.Once` \u002F `singleflight` | Execute once or deduplicate |\n\n## WaitGroup vs errgroup\n\n| Need | Use | Why |\n| --- | --- | --- |\n| Wait for goroutines, errors not needed | `sync.WaitGroup` | Fire-and-forget |\n| Wait + collect first error | `errgroup.Group` | Error propagation |\n| Wait + cancel siblings on first error | `errgroup.WithContext` | Context cancellation on error |\n| Wait + limit concurrency | `errgroup.SetLimit(n)` | Built-in worker pool |\n\n## Sync Primitives Quick Reference\n\n| Primitive | Use case | Key notes |\n| --- | --- | --- |\n| `sync.Mutex` | Protect shared state | Keep critical sections short; never hold across I\u002FO |\n| `sync.RWMutex` | Many readers, few writers | Never upgrade RLock to Lock (deadlock) |\n| `sync\u002Fatomic` | Simple counters, flags | Prefer typed atomics (Go 1.19+): `atomic.Int64`, `atomic.Bool` |\n| `sync.Map` | Concurrent map, read-heavy | No explicit locking; use `RWMutex`+map when writes dominate |\n| `sync.Pool` | Reuse temporary objects | Always `Reset()` before `Put()`; reduces GC pressure |\n| `sync.Once` | One-time initialization | Go 1.21+: `OnceFunc`, `OnceValue`, `OnceValues` |\n| `sync.WaitGroup` | Waiting for simple goroutines | Go 1.25+: prefer `wg.Go(func(){ ... })` for fire-and-wait tasks that do not panic and do not need error propagation. For Go \u003C1.25 use `Add`\u002F`Done`. For errors\u002Fcancellation\u002Flimits, use `errgroup` with context. |\n| `x\u002Fsync\u002Fsingleflight` | Deduplicate concurrent calls | Cache stampede prevention |\n| `x\u002Fsync\u002Ferrgroup` | Goroutine group + errors | `SetLimit(n)` replaces hand-rolled worker pools |\n\nFor detailed examples and anti-patterns, see [Sync Primitives Deep Dive](references\u002Fsync-primitives.md).\n\n## Concurrency Checklist\n\nBefore spawning a goroutine, answer:\n\n- [ ] **How will it exit?** — context cancellation, channel close, or explicit signal\n- [ ] **Can I signal it to stop?** — pass `context.Context` or done channel\n- [ ] **Can I wait for it?** — `sync.WaitGroup` or `errgroup`\n- [ ] **Who owns the channels?** — creator\u002Fsender owns and closes\n- [ ] **Should this be synchronous instead?** — don't add concurrency without measured need\n\n## Pipelines and Worker Pools\n\nFor pipeline patterns (fan-out\u002Ffan-in, bounded workers, generator chains, Go 1.23+ iterators, `samber\u002Fro`), see [Pipelines and Worker Pools](references\u002Fpipelines.md).\n\n## Parallelizing Concurrency Audits\n\nWhen auditing concurrency across a large codebase, use up to 5 parallel sub-agents:\n\n1. Find all goroutine spawns (`go func`, `go method`) and verify shutdown mechanisms\n2. Search for mutable globals and shared state without synchronization\n3. Audit channel usage — ownership, direction, closure, buffer sizes\n4. Find `time.After` in loops, missing `ctx.Done()` in select, unbounded spawning\n5. Check mutex usage, `sync.Map`, atomics, and thread-safety documentation\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Fire-and-forget goroutine | Provide stop mechanism (context, done channel) |\n| Closing channel from receiver | Only the sender closes |\n| `time.After` in hot loop | Reuse `time.NewTimer` + `Reset` |\n| Missing `ctx.Done()` in select | Always select on context to allow cancellation |\n| Unbounded goroutine spawning | Use `errgroup.SetLimit(n)` or semaphore |\n| Sharing pointer via channel | Send copies or immutable values |\n| `wg.Add` inside goroutine | Call `Add` before `go` — `Wait` may return early otherwise |\n| Forgetting `-race` in CI | Always run `go test -race .\u002F...` |\n| Mutex held across I\u002FO | Keep critical sections short |\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-performance` skill for false sharing, cache-line padding, `sync.Pool` hot-path patterns\n- → See `samber\u002Fcc-skills-golang@golang-context` skill for cancellation propagation and timeout patterns\n- → See `samber\u002Fcc-skills-golang@golang-safety` skill for concurrent map access and race condition prevention\n- → See `samber\u002Fcc-skills-golang@golang-troubleshooting` skill for debugging goroutine leaks and deadlocks\n- → See `samber\u002Fcc-skills-golang@golang-design-patterns` skill for graceful shutdown patterns\n- → See `samber\u002Fcc-skills-golang@golang-continuous-integration` skill for automated AI-driven code review in CI using these guidelines\n\n### Goroutine leak profile\n\nThe goroutine leak profile (experimental behind `GOEXPERIMENT=goroutineleakprofile` in Go 1.26) is generally available in `runtime\u002Fpprof` since Go 1.27 — no build flag required. It is a useful production-oriented leak signal alongside the existing tools below.\n\n```bash\ncurl http:\u002F\u002Flocalhost:6060\u002Fdebug\u002Fpprof\u002Fgoroutineleak?debug=2\ngo tool pprof http:\u002F\u002Flocalhost:6060\u002Fdebug\u002Fpprof\u002Fgoroutineleak\n```\n\nKeep existing tools:\n\n- tests: `go.uber.org\u002Fgoleak`\n- runtime count: `runtime.NumGoroutine()`\n- stack dump: `\u002Fdebug\u002Fpprof\u002Fgoroutine?debug=2`\n- race checks: `go test -race .\u002F...`\n\n## References\n\n- [Go Concurrency Patterns: Pipelines](https:\u002F\u002Fgo.dev\u002Fblog\u002Fpipelines)\n- [Effective Go: Concurrency](https:\u002F\u002Fgo.dev\u002Fdoc\u002Feffective_go#concurrency)\n","**Persona:** You are a Go concurrency engineer. You assume every goroutine is a liability until proven necessary — correctness and leak-freedom come before performance.\n\n**Orchestration mode:** Fan out the five sub-agents described in the \"Parallelizing Concurrency Audits\" section for auditing concurrent code across a large codebase, and consolidate their findings into one report. On Claude Code, use `ultracode` to opt into multi-agent orchestration explicitly.\n\n**Modes:**\n\n- **Write mode** — implement concurrent code (goroutines, channels, sync primitives, worker pools, pipelines). Follow the sequential instructions below.\n- **Review mode** — reviewing a PR's concurrent code changes. Focus on the diff: check for goroutine leaks, missing context propagation, ownership violations, and unprotected shared state. Sequential.\n- **Audit mode** — auditing existing concurrent code across a codebase. Use up to 5 parallel sub-agents as described in the \"Parallelizing Concurrency Audits\" section.\n\n> **Community default.** A company skill that explicitly supersedes `samber\u002Fcc-skills-golang@golang-concurrency` skill takes precedence.\n\n# Go Concurrency Best Practices\n\nGo's concurrency model is built on goroutines and channels. Goroutines are cheap but not free — every goroutine you spawn is a resource you must manage. The goal is structured concurrency: every goroutine has a clear owner, a predictable exit, and proper error propagation.\n\n## Core Principles\n\n1. **Every goroutine must have a clear exit** — without a shutdown mechanism (context, done channel, WaitGroup), they leak and accumulate until the process crashes\n2. **Share memory by communicating** — channels transfer ownership explicitly; mutexes protect shared state but make ownership implicit\n3. **Send copies, not pointers** on channels — sending pointers creates invisible shared memory, defeating the purpose of channels\n4. **Only the sender closes a channel** — closing from the receiver side panics if the sender writes after close\n5. **Specify channel direction** (`chan\u003C-`, `\u003C-chan`) — the compiler prevents misuse at build time\n6. **Default to unbuffered channels** — larger buffers mask backpressure; use them only with measured justification\n7. **Always include `ctx.Done()` in select** — without it, goroutines leak after caller cancellation\n8. **Avoid repeated `time.After` in hot loops** — each call allocates a timer and creates unnecessary churn; use `time.NewTimer` + `Reset` for long-running loops\n9. **Track goroutine leaks in tests** with `go.uber.org\u002Fgoleak`\n\nFor detailed channel\u002Fselect code examples, see [Channels and Select Patterns](references\u002Fchannels-and-select.md).\n\n## Channel vs Mutex vs Atomic\n\n| Scenario | Use | Why |\n| --- | --- | --- |\n| Passing data between goroutines | Channel | Communicates ownership transfer |\n| Coordinating goroutine lifecycle | Channel + context | Clean shutdown with select |\n| Protecting shared struct fields | `sync.Mutex` \u002F `sync.RWMutex` | Simple critical sections |\n| Simple counters, flags | `sync\u002Fatomic` | Lock-free, lower overhead |\n| Many readers, few writers on a map | `sync.Map` | Optimized for read-heavy workloads. **Concurrent map read\u002Fwrite causes a hard crash** |\n| Caching expensive computations | `sync.Once` \u002F `singleflight` | Execute once or deduplicate |\n\n## WaitGroup vs errgroup\n\n| Need | Use | Why |\n| --- | --- | --- |\n| Wait for goroutines, errors not needed | `sync.WaitGroup` | Fire-and-forget |\n| Wait + collect first error | `errgroup.Group` | Error propagation |\n| Wait + cancel siblings on first error | `errgroup.WithContext` | Context cancellation on error |\n| Wait + limit concurrency | `errgroup.SetLimit(n)` | Built-in worker pool |\n\n## Sync Primitives Quick Reference\n\n| Primitive | Use case | Key notes |\n| --- | --- | --- |\n| `sync.Mutex` | Protect shared state | Keep critical sections short; never hold across I\u002FO |\n| `sync.RWMutex` | Many readers, few writers | Never upgrade RLock to Lock (deadlock) |\n| `sync\u002Fatomic` | Simple counters, flags | Prefer typed atomics (Go 1.19+): `atomic.Int64`, `atomic.Bool` |\n| `sync.Map` | Concurrent map, read-heavy | No explicit locking; use `RWMutex`+map when writes dominate |\n| `sync.Pool` | Reuse temporary objects | Always `Reset()` before `Put()`; reduces GC pressure |\n| `sync.Once` | One-time initialization | Go 1.21+: `OnceFunc`, `OnceValue`, `OnceValues` |\n| `sync.WaitGroup` | Waiting for simple goroutines | Go 1.25+: prefer `wg.Go(func(){ ... })` for fire-and-wait tasks that do not panic and do not need error propagation. For Go \u003C1.25 use `Add`\u002F`Done`. For errors\u002Fcancellation\u002Flimits, use `errgroup` with context. |\n| `x\u002Fsync\u002Fsingleflight` | Deduplicate concurrent calls | Cache stampede prevention |\n| `x\u002Fsync\u002Ferrgroup` | Goroutine group + errors | `SetLimit(n)` replaces hand-rolled worker pools |\n\nFor detailed examples and anti-patterns, see [Sync Primitives Deep Dive](references\u002Fsync-primitives.md).\n\n## Concurrency Checklist\n\nBefore spawning a goroutine, answer:\n\n- [ ] **How will it exit?** — context cancellation, channel close, or explicit signal\n- [ ] **Can I signal it to stop?** — pass `context.Context` or done channel\n- [ ] **Can I wait for it?** — `sync.WaitGroup` or `errgroup`\n- [ ] **Who owns the channels?** — creator\u002Fsender owns and closes\n- [ ] **Should this be synchronous instead?** — don't add concurrency without measured need\n\n## Pipelines and Worker Pools\n\nFor pipeline patterns (fan-out\u002Ffan-in, bounded workers, generator chains, Go 1.23+ iterators, `samber\u002Fro`), see [Pipelines and Worker Pools](references\u002Fpipelines.md).\n\n## Parallelizing Concurrency Audits\n\nWhen auditing concurrency across a large codebase, use up to 5 parallel sub-agents:\n\n1. Find all goroutine spawns (`go func`, `go method`) and verify shutdown mechanisms\n2. Search for mutable globals and shared state without synchronization\n3. Audit channel usage — ownership, direction, closure, buffer sizes\n4. Find `time.After` in loops, missing `ctx.Done()` in select, unbounded spawning\n5. Check mutex usage, `sync.Map`, atomics, and thread-safety documentation\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Fire-and-forget goroutine | Provide stop mechanism (context, done channel) |\n| Closing channel from receiver | Only the sender closes |\n| `time.After` in hot loop | Reuse `time.NewTimer` + `Reset` |\n| Missing `ctx.Done()` in select | Always select on context to allow cancellation |\n| Unbounded goroutine spawning | Use `errgroup.SetLimit(n)` or semaphore |\n| Sharing pointer via channel | Send copies or immutable values |\n| `wg.Add` inside goroutine | Call `Add` before `go` — `Wait` may return early otherwise |\n| Forgetting `-race` in CI | Always run `go test -race .\u002F...` |\n| Mutex held across I\u002FO | Keep critical sections short |\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-performance` skill for false sharing, cache-line padding, `sync.Pool` hot-path patterns\n- → See `samber\u002Fcc-skills-golang@golang-context` skill for cancellation propagation and timeout patterns\n- → See `samber\u002Fcc-skills-golang@golang-safety` skill for concurrent map access and race condition prevention\n- → See `samber\u002Fcc-skills-golang@golang-troubleshooting` skill for debugging goroutine leaks and deadlocks\n- → See `samber\u002Fcc-skills-golang@golang-design-patterns` skill for graceful shutdown patterns\n- → See `samber\u002Fcc-skills-golang@golang-continuous-integration` skill for automated AI-driven code review in CI using these guidelines\n\n### Goroutine leak profile\n\nThe goroutine leak profile (experimental behind `GOEXPERIMENT=goroutineleakprofile` in Go 1.26) is generally available in `runtime\u002Fpprof` since Go 1.27 — no build flag required. It is a useful production-oriented leak signal alongside the existing tools below.\n\n```bash\ncurl http:\u002F\u002Flocalhost:6060\u002Fdebug\u002Fpprof\u002Fgoroutineleak?debug=2\ngo tool pprof http:\u002F\u002Flocalhost:6060\u002Fdebug\u002Fpprof\u002Fgoroutineleak\n```\n\nKeep existing tools:\n\n- tests: `go.uber.org\u002Fgoleak`\n- runtime count: `runtime.NumGoroutine()`\n- stack dump: `\u002Fdebug\u002Fpprof\u002Fgoroutine?debug=2`\n- race checks: `go test -race .\u002F...`\n\n## References\n\n- [Go Concurrency Patterns: Pipelines](https:\u002F\u002Fgo.dev\u002Fblog\u002Fpipelines)\n- [Effective Go: Concurrency](https:\u002F\u002Fgo.dev\u002Fdoc\u002Feffective_go#concurrency)\n",{"name":5,"paths":24,"license":15,"metadata":26,"description":7,"allowed-tools":36,"compatibility":37,"user-invocable":38},[25],"**\u002F*.go",{"author":27,"version":28,"openclaw":29},"samber","1.2.1",{"emoji":30,"install":31,"homepage":32,"requires":33},"⚡",[],"https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":34},[35],"go","Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent AskUserQuestion","Designed for Claude Code, Codex or similar harness, and for projects using Golang.",true,"main","19f4d52a98d557f3a645a2cfbbeb5bd54f28831d",".github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-concurrency","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi","https:\u002F\u002Fgithub.com\u002Fkongnakornna","http:\u002F\u002Fcmoniot.trueddns.com:52160","Technical Skills and Expertise\r\nLanguages and Frameworks\r\nFrontend: HTML, JavaScript, TypeScript, React, Vue, Angular, Next.js\r\nBackend: Node.js,Python,Golang","2026-10-06 23:01:46",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":38},[49,52,55],{"tool":50,"command":51},"npx","npx skills add kongnakornna\u002Fgolangapi --skill golang-concurrency",{"tool":53,"command":54},"bunx","bunx skills add kongnakornna\u002Fgolangapi --skill golang-concurrency",{"tool":56,"command":57},"pnpm","pnpm dlx skills add kongnakornna\u002Fgolangapi --skill golang-concurrency","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-concurrency\u002FSKILL.md",[60,66,70,74],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"evals\u002Fevals.json","REFERENCE","参考文档",16442,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-concurrency\u002Fevals\u002Fevals.json",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fchannels-and-select.md",4450,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-concurrency\u002Freferences\u002Fchannels-and-select.md",{"path":71,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fpipelines.md",7381,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-concurrency\u002Freferences\u002Fpipelines.md",{"path":75,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fsync-primitives.md",8850,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-concurrency\u002Freferences\u002Fsync-primitives.md",[79,87,94,101,108,115],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7A0M9RJJ3383VEFYKABWV15","tb-writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-writing-plans\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7A0M4JKY4DEDRP1CBHT00WV","tb-using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-using-git-worktrees\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7A0KZ5HRAQAAT2KXR6146Q7","tb-test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-test-driven-development\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7A0KW92W3F18E2MRP8H62P2","tb-subagent-driven-development","Use when executing implementation plans with independent tasks in the current session","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-subagent-driven-development\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7A0KKYQCHYYRHA5J5BAP24M","tb-scrutinize","Outsider-perspective end-to-end review of a plan, PR, or code change. First questions intent and whether a simpler\u002Fmore elegant approach would achieve the same goal, then traces the actual code path (not just the diff) to verify the change does what it claims. Output is concise, actionable, and every call carries its rationale. Trigger on \u002Ftb-scrutinize and proactively whenever the user asks to review, audit, sanity-check, or get a second opinion on a plan, PR, diff, design doc, or proposed code change.","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-scrutinize\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7A0KFDR1V3RW7SW1XNHP82P","tb-requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-requesting-code-review\u002FSKILL.md",[],[]]