[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79ZV1XG59RTF71KZP3R8TGJ":3,"skill-same:01M79ZV1XG59RTF71KZP3R8TGJ":79},{"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":40,"commitSha":41,"skillDirectory":42,"forksCount":14,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":60},"01M79ZV1XG59RTF71KZP3R8TGJ","golang-uber-dig",null,"Implements dependency injection in Golang using uber-go\u002Fdig — reflection-based container, Provide\u002FInvoke, dig.In\u002Fdig.Out parameter and result objects, named values, value groups, optional dependencies, scopes, and Decorate. Apply when using or adopting uber-go\u002Fdig, when the codebase imports `go.uber.org\u002Fdig`, or when wiring an application graph at startup. For higher-level lifecycle and modules, see `samber\u002Fcc-skills-golang@golang-uber-fx` 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-uber-dig\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: golang-uber-dig\ndescription: \"Implements dependency injection in Golang using uber-go\u002Fdig — reflection-based container, Provide\u002FInvoke, dig.In\u002Fdig.Out parameter and result objects, named values, value groups, optional dependencies, scopes, and Decorate. Apply when using or adopting uber-go\u002Fdig, when the codebase imports `go.uber.org\u002Fdig`, or when wiring an application graph at startup. For higher-level lifecycle and modules, see `samber\u002Fcc-skills-golang@golang-uber-fx` 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.2\"\n  openclaw:\n    emoji: \"⛏\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\n    requires:\n      bins:\n        - go\n    install: []\n    skill-library-version: \"1.19.0\"\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch mcp__context7__resolve-library-id mcp__context7__query-docs Bash(godig:*) Bash(gopls:*) LSP mcp__gopls__*\npaths:\n  - \"**\u002F*.go\"\n---\n\n**Persona:** You are a Go architect wiring an application graph with dig. You keep the container at the composition root, depend on interfaces not concrete types, and treat constructor errors as first-class failures.\n\n# Using uber-go\u002Fdig for Dependency Injection in Go\n\nReflection-based DI toolkit, designed to power application frameworks (it is the engine behind `uber-go\u002Ffx`) and resolve object graphs during startup.\n\n**Official Resources:**\n\n- [pkg.go.dev\u002Fgo.uber.org\u002Fdig](https:\u002F\u002Fpkg.go.dev\u002Fgo.uber.org\u002Fdig)\n- [github.com\u002Fuber-go\u002Fdig](https:\u002F\u002Fgithub.com\u002Fuber-go\u002Fdig)\n\nThis skill is not exhaustive — refer to library documentation and code examples for more information:\n\n- For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`), preferred over Context7 for Go package facts.\n- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber\u002Fcc-skills-golang@golang-gopls` skill (`gopls`).\n- Context7 remains a fallback for docs not indexed on pkg.go.dev.\n\n```bash\ngo get go.uber.org\u002Fdig\n```\n\n## dig vs. fx\n\nfx is built on dig and shares the same container engine — the DI primitives (`Provide`, `Invoke`, `In`\u002F`Out` structs, named values, value groups) are identical. `fx.In`\u002F`fx.Out` are re-exports of `dig.In`\u002F`dig.Out`.\n\nWhat fx adds on top of dig:\n\n| Concern | dig | fx |\n| --- | --- | --- |\n| DI container | ✅ `dig.New()` | ✅ (embedded) |\n| Lifecycle hooks | ❌ | ✅ `fx.Lifecycle` OnStart\u002FOnStop |\n| Module system | ❌ | ✅ `fx.Module` with scoped decorators |\n| Signal-aware run loop | ❌ | ✅ `app.Run()` blocks on SIGINT\u002FSIGTERM |\n| Structured event logging | ❌ | ✅ `fx.WithLogger` \u002F `fxevent` |\n| Startup\u002Fshutdown timeout | ❌ | ✅ `fx.StartTimeout` \u002F `fx.StopTimeout` |\n\n**Choose dig** when you need the wiring graph only: CLI tools, libraries exposing a container to callers, test harnesses, or embedding DI into an existing app that manages its own lifecycle.\n\n**Choose fx** for long-running services (HTTP servers, workers, daemons) — lifecycle and signal handling are non-negotiable there. See `samber\u002Fcc-skills-golang@golang-uber-fx` skill.\n\n## Container\n\n```go\nimport \"go.uber.org\u002Fdig\"\n\nc := dig.New()\n```\n\nUseful options: `dig.DeferAcyclicVerification()` (faster startup), `dig.RecoverFromPanics()` (turn panics into `dig.PanicError`), `dig.DryRun(true)` (validate without invoking).\n\n## Provide and Invoke\n\n```go\n\u002F\u002F Register a constructor — lazy, only runs when its output is needed\nerr := c.Provide(func(cfg *Config) (*sql.DB, error) {\n    return sql.Open(\"postgres\", cfg.DSN)\n})\n\n\u002F\u002F Pull a service out of the container by asking for it as a function parameter\nerr = c.Invoke(func(db *sql.DB) error {\n    return db.Ping()\n})\n```\n\nConstructors are **lazy** and **memoized**: each output type is built once and shared (singleton per container). `Provide` errors at registration if the constructor is malformed; `Invoke` returns the constructor's error wrapped with the dependency path that triggered it.\n\nA dig constructor is any function whose inputs are dependencies and whose outputs are provided types. `error` (last return) signals construction failure. Follow \"accept interfaces, return structs\".\n\n## Parameter Objects with `dig.In`\n\nOnce a constructor has 4+ dependencies, embed `dig.In` to group them as struct fields and tag fields:\n\n```go\ntype HandlerParams struct {\n    dig.In\n\n    Logger *zap.Logger\n    DB     *sql.DB\n    Cache  *redis.Client `optional:\"true\"`           \u002F\u002F zero value if not provided\n    DBRO   *sql.DB       `name:\"readonly\"`           \u002F\u002F named dependency\n    Routes []http.Handler `group:\"routes\"`           \u002F\u002F value group\n}\n\nfunc NewHandler(p HandlerParams) *Handler { \u002F* ... *\u002F }\n```\n\nTags: `name:\"...\"`, `optional:\"true\"`, `group:\"...\"`.\n\n## Result Objects with `dig.Out`\n\nReturn several values from one constructor and attach `name`\u002F`group` tags to results:\n\n```go\ntype ConnResult struct {\n    dig.Out\n\n    ReadWrite *sql.DB `name:\"primary\"`\n    ReadOnly  *sql.DB `name:\"readonly\"`\n}\n\nfunc NewConnections(cfg *Config) (ConnResult, error) { \u002F* ... *\u002F }\n```\n\n## Named Values\n\nTwo providers of the same type collide. Disambiguate with `dig.Name`:\n\n```go\nc.Provide(NewPrimaryDB,  dig.Name(\"primary\"))\nc.Provide(NewReadOnlyDB, dig.Name(\"readonly\"))\n```\n\nConsume by adding `name:\"primary\"` \u002F `name:\"readonly\"` to a `dig.In` field.\n\n## Value Groups\n\nMany providers, one consumer slice — typical for HTTP handlers, health checks, migrations:\n\n```go\ntype RouteResult struct {\n    dig.Out\n    Handler http.Handler `group:\"routes\"`\n}\n\nfunc NewUserHandler(db *sql.DB) RouteResult { \u002F* ... *\u002F }\nfunc NewPostHandler(db *sql.DB) RouteResult { \u002F* ... *\u002F }\n\ntype ServerParams struct {\n    dig.In\n    Routes []http.Handler `group:\"routes\"`\n}\n```\n\n**Flatten** — append `,flatten` (e.g. `group:\"routes,flatten\"`) to unwrap a slice instead of nesting it. Group order is **not guaranteed**; if order matters, provide an explicit ordered slice from a single constructor.\n\n## Provide as Interface (`dig.As`)\n\nRegister a concrete constructor and expose it under one or more interfaces without a separate adapter:\n\n```go\nc.Provide(NewPostgresDB, dig.As(new(Database), new(io.Closer)))\n\u002F\u002F Consumers ask for Database or io.Closer; *PostgresDB stays hidden.\n```\n\n## Full Application Example\n\n```go\nfunc main() {\n    c := dig.New()\n\n    must(c.Provide(NewConfig))\n    must(c.Provide(NewLogger))\n    must(c.Provide(NewDatabase))\n    must(c.Provide(NewServer))\n\n    err := c.Invoke(func(srv *http.Server) error {\n        return srv.ListenAndServe()\n    })\n    if err != nil {\n        log.Fatal(err)\n    }\n}\n\nfunc must(err error) { if err != nil { panic(err) } }\n```\n\ndig has **no built-in lifecycle**. If you need OnStart\u002FOnStop hooks, signal handling, and graceful shutdown, use fx — see `samber\u002Fcc-skills-golang@golang-uber-fx` skill.\n\nFor Decorate, Scopes, optional deps, error helpers, and Visualize, see [advanced.md](.\u002Freferences\u002Fadvanced.md).\n\n## Best Practices\n\n1. Keep the container at the composition root — never pass `*dig.Container` as a parameter; treat it like a plumbing detail of `main()`. Service-locator patterns defeat the testability gains of DI.\n2. Depend on interfaces, not concrete types — lets you swap implementations in tests without touching production code, and lets you use `dig.As` to expose narrow interfaces from wide structs.\n3. Prefer parameter objects (`dig.In` structs) once a constructor has 4+ dependencies — call sites stay readable and adding a new dependency is a one-line change instead of a signature break.\n4. Group registration by module (one file per module that calls `c.Provide` for its types) — review and refactoring become a per-module concern, and you can extract a module into a fx.Module later without rewriting wiring.\n5. Validate the graph eagerly in tests — call `c.Invoke` against the composition root in CI to surface missing providers at boot time, not at first request. `DryRun(true)` skips constructor execution.\n6. Return errors from constructors instead of panicking — dig wraps them with the dependency path, which makes the failure point obvious.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Passing the container into services | The container belongs to `main()`. Inject the typed dependencies a service needs; otherwise tests need to build a real container. |\n| Two providers for the same type without `Name` | dig errors at `Provide` time. Either name them, or merge into a single provider that returns a `dig.Out` result struct. |\n| Ignoring `Provide` errors | Wrap each `Provide` with a `must` helper. A silent registration error becomes a missing-type error far later. |\n| Using groups when ordering matters | Groups are unordered. If order matters (middleware chain, migration sequence), provide an explicit ordered slice with one constructor. |\n| Constructors with side effects on import | Keep `init()` empty — start work only inside the constructor, after the graph is built. |\n\n## Testing\n\ndig containers are cheap — build a fresh one per test, override providers with `Decorate`, and call `Invoke` to drive the system. For full patterns (per-test wiring, shared helpers, graph validation in CI, asserting wire-time errors, recovering from constructor panics), see [testing.md](.\u002Freferences\u002Ftesting.md).\n\n## Further Reading\n\n- [advanced.md](.\u002Freferences\u002Fadvanced.md) — Decorate, Scopes, optional deps, error helpers, Visualize, full Quick Reference\n- [recipes.md](.\u002Freferences\u002Frecipes.md) — end-to-end examples: HTTP server with route group, two databases, request scopes, decorators, dry-run validation\n- [testing.md](.\u002Freferences\u002Ftesting.md) — testing patterns and graph validation\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-uber-fx` skill for application lifecycle, modules, and signal-aware Run() built on top of dig\n- → See `samber\u002Fcc-skills-golang@golang-dependency-injection` skill for DI concepts and library comparison\n- → See `samber\u002Fcc-skills-golang@golang-samber-do` skill for a generics-based alternative without reflection\n- → See `samber\u002Fcc-skills-golang@golang-google-wire` skill for compile-time DI (no runtime container)\n- → See `samber\u002Fcc-skills-golang@golang-structs-interfaces` skill for interface design patterns\n- → See `samber\u002Fcc-skills-golang@golang-testing` skill for general testing patterns\n\nIf you encounter a bug or unexpected behavior in uber-go\u002Fdig, open an issue at \u003Chttps:\u002F\u002Fgithub.com\u002Fuber-go\u002Fdig\u002Fissues>.\n","**Persona:** You are a Go architect wiring an application graph with dig. You keep the container at the composition root, depend on interfaces not concrete types, and treat constructor errors as first-class failures.\n\n# Using uber-go\u002Fdig for Dependency Injection in Go\n\nReflection-based DI toolkit, designed to power application frameworks (it is the engine behind `uber-go\u002Ffx`) and resolve object graphs during startup.\n\n**Official Resources:**\n\n- [pkg.go.dev\u002Fgo.uber.org\u002Fdig](https:\u002F\u002Fpkg.go.dev\u002Fgo.uber.org\u002Fdig)\n- [github.com\u002Fuber-go\u002Fdig](https:\u002F\u002Fgithub.com\u002Fuber-go\u002Fdig)\n\nThis skill is not exhaustive — refer to library documentation and code examples for more information:\n\n- For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`), preferred over Context7 for Go package facts.\n- To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber\u002Fcc-skills-golang@golang-gopls` skill (`gopls`).\n- Context7 remains a fallback for docs not indexed on pkg.go.dev.\n\n```bash\ngo get go.uber.org\u002Fdig\n```\n\n## dig vs. fx\n\nfx is built on dig and shares the same container engine — the DI primitives (`Provide`, `Invoke`, `In`\u002F`Out` structs, named values, value groups) are identical. `fx.In`\u002F`fx.Out` are re-exports of `dig.In`\u002F`dig.Out`.\n\nWhat fx adds on top of dig:\n\n| Concern | dig | fx |\n| --- | --- | --- |\n| DI container | ✅ `dig.New()` | ✅ (embedded) |\n| Lifecycle hooks | ❌ | ✅ `fx.Lifecycle` OnStart\u002FOnStop |\n| Module system | ❌ | ✅ `fx.Module` with scoped decorators |\n| Signal-aware run loop | ❌ | ✅ `app.Run()` blocks on SIGINT\u002FSIGTERM |\n| Structured event logging | ❌ | ✅ `fx.WithLogger` \u002F `fxevent` |\n| Startup\u002Fshutdown timeout | ❌ | ✅ `fx.StartTimeout` \u002F `fx.StopTimeout` |\n\n**Choose dig** when you need the wiring graph only: CLI tools, libraries exposing a container to callers, test harnesses, or embedding DI into an existing app that manages its own lifecycle.\n\n**Choose fx** for long-running services (HTTP servers, workers, daemons) — lifecycle and signal handling are non-negotiable there. See `samber\u002Fcc-skills-golang@golang-uber-fx` skill.\n\n## Container\n\n```go\nimport \"go.uber.org\u002Fdig\"\n\nc := dig.New()\n```\n\nUseful options: `dig.DeferAcyclicVerification()` (faster startup), `dig.RecoverFromPanics()` (turn panics into `dig.PanicError`), `dig.DryRun(true)` (validate without invoking).\n\n## Provide and Invoke\n\n```go\n\u002F\u002F Register a constructor — lazy, only runs when its output is needed\nerr := c.Provide(func(cfg *Config) (*sql.DB, error) {\n    return sql.Open(\"postgres\", cfg.DSN)\n})\n\n\u002F\u002F Pull a service out of the container by asking for it as a function parameter\nerr = c.Invoke(func(db *sql.DB) error {\n    return db.Ping()\n})\n```\n\nConstructors are **lazy** and **memoized**: each output type is built once and shared (singleton per container). `Provide` errors at registration if the constructor is malformed; `Invoke` returns the constructor's error wrapped with the dependency path that triggered it.\n\nA dig constructor is any function whose inputs are dependencies and whose outputs are provided types. `error` (last return) signals construction failure. Follow \"accept interfaces, return structs\".\n\n## Parameter Objects with `dig.In`\n\nOnce a constructor has 4+ dependencies, embed `dig.In` to group them as struct fields and tag fields:\n\n```go\ntype HandlerParams struct {\n    dig.In\n\n    Logger *zap.Logger\n    DB     *sql.DB\n    Cache  *redis.Client `optional:\"true\"`           \u002F\u002F zero value if not provided\n    DBRO   *sql.DB       `name:\"readonly\"`           \u002F\u002F named dependency\n    Routes []http.Handler `group:\"routes\"`           \u002F\u002F value group\n}\n\nfunc NewHandler(p HandlerParams) *Handler { \u002F* ... *\u002F }\n```\n\nTags: `name:\"...\"`, `optional:\"true\"`, `group:\"...\"`.\n\n## Result Objects with `dig.Out`\n\nReturn several values from one constructor and attach `name`\u002F`group` tags to results:\n\n```go\ntype ConnResult struct {\n    dig.Out\n\n    ReadWrite *sql.DB `name:\"primary\"`\n    ReadOnly  *sql.DB `name:\"readonly\"`\n}\n\nfunc NewConnections(cfg *Config) (ConnResult, error) { \u002F* ... *\u002F }\n```\n\n## Named Values\n\nTwo providers of the same type collide. Disambiguate with `dig.Name`:\n\n```go\nc.Provide(NewPrimaryDB,  dig.Name(\"primary\"))\nc.Provide(NewReadOnlyDB, dig.Name(\"readonly\"))\n```\n\nConsume by adding `name:\"primary\"` \u002F `name:\"readonly\"` to a `dig.In` field.\n\n## Value Groups\n\nMany providers, one consumer slice — typical for HTTP handlers, health checks, migrations:\n\n```go\ntype RouteResult struct {\n    dig.Out\n    Handler http.Handler `group:\"routes\"`\n}\n\nfunc NewUserHandler(db *sql.DB) RouteResult { \u002F* ... *\u002F }\nfunc NewPostHandler(db *sql.DB) RouteResult { \u002F* ... *\u002F }\n\ntype ServerParams struct {\n    dig.In\n    Routes []http.Handler `group:\"routes\"`\n}\n```\n\n**Flatten** — append `,flatten` (e.g. `group:\"routes,flatten\"`) to unwrap a slice instead of nesting it. Group order is **not guaranteed**; if order matters, provide an explicit ordered slice from a single constructor.\n\n## Provide as Interface (`dig.As`)\n\nRegister a concrete constructor and expose it under one or more interfaces without a separate adapter:\n\n```go\nc.Provide(NewPostgresDB, dig.As(new(Database), new(io.Closer)))\n\u002F\u002F Consumers ask for Database or io.Closer; *PostgresDB stays hidden.\n```\n\n## Full Application Example\n\n```go\nfunc main() {\n    c := dig.New()\n\n    must(c.Provide(NewConfig))\n    must(c.Provide(NewLogger))\n    must(c.Provide(NewDatabase))\n    must(c.Provide(NewServer))\n\n    err := c.Invoke(func(srv *http.Server) error {\n        return srv.ListenAndServe()\n    })\n    if err != nil {\n        log.Fatal(err)\n    }\n}\n\nfunc must(err error) { if err != nil { panic(err) } }\n```\n\ndig has **no built-in lifecycle**. If you need OnStart\u002FOnStop hooks, signal handling, and graceful shutdown, use fx — see `samber\u002Fcc-skills-golang@golang-uber-fx` skill.\n\nFor Decorate, Scopes, optional deps, error helpers, and Visualize, see [advanced.md](.\u002Freferences\u002Fadvanced.md).\n\n## Best Practices\n\n1. Keep the container at the composition root — never pass `*dig.Container` as a parameter; treat it like a plumbing detail of `main()`. Service-locator patterns defeat the testability gains of DI.\n2. Depend on interfaces, not concrete types — lets you swap implementations in tests without touching production code, and lets you use `dig.As` to expose narrow interfaces from wide structs.\n3. Prefer parameter objects (`dig.In` structs) once a constructor has 4+ dependencies — call sites stay readable and adding a new dependency is a one-line change instead of a signature break.\n4. Group registration by module (one file per module that calls `c.Provide` for its types) — review and refactoring become a per-module concern, and you can extract a module into a fx.Module later without rewriting wiring.\n5. Validate the graph eagerly in tests — call `c.Invoke` against the composition root in CI to surface missing providers at boot time, not at first request. `DryRun(true)` skips constructor execution.\n6. Return errors from constructors instead of panicking — dig wraps them with the dependency path, which makes the failure point obvious.\n\n## Common Mistakes\n\n| Mistake | Fix |\n| --- | --- |\n| Passing the container into services | The container belongs to `main()`. Inject the typed dependencies a service needs; otherwise tests need to build a real container. |\n| Two providers for the same type without `Name` | dig errors at `Provide` time. Either name them, or merge into a single provider that returns a `dig.Out` result struct. |\n| Ignoring `Provide` errors | Wrap each `Provide` with a `must` helper. A silent registration error becomes a missing-type error far later. |\n| Using groups when ordering matters | Groups are unordered. If order matters (middleware chain, migration sequence), provide an explicit ordered slice with one constructor. |\n| Constructors with side effects on import | Keep `init()` empty — start work only inside the constructor, after the graph is built. |\n\n## Testing\n\ndig containers are cheap — build a fresh one per test, override providers with `Decorate`, and call `Invoke` to drive the system. For full patterns (per-test wiring, shared helpers, graph validation in CI, asserting wire-time errors, recovering from constructor panics), see [testing.md](.\u002Freferences\u002Ftesting.md).\n\n## Further Reading\n\n- [advanced.md](.\u002Freferences\u002Fadvanced.md) — Decorate, Scopes, optional deps, error helpers, Visualize, full Quick Reference\n- [recipes.md](.\u002Freferences\u002Frecipes.md) — end-to-end examples: HTTP server with route group, two databases, request scopes, decorators, dry-run validation\n- [testing.md](.\u002Freferences\u002Ftesting.md) — testing patterns and graph validation\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-uber-fx` skill for application lifecycle, modules, and signal-aware Run() built on top of dig\n- → See `samber\u002Fcc-skills-golang@golang-dependency-injection` skill for DI concepts and library comparison\n- → See `samber\u002Fcc-skills-golang@golang-samber-do` skill for a generics-based alternative without reflection\n- → See `samber\u002Fcc-skills-golang@golang-google-wire` skill for compile-time DI (no runtime container)\n- → See `samber\u002Fcc-skills-golang@golang-structs-interfaces` skill for interface design patterns\n- → See `samber\u002Fcc-skills-golang@golang-testing` skill for general testing patterns\n\nIf you encounter a bug or unexpected behavior in uber-go\u002Fdig, open an issue at \u003Chttps:\u002F\u002Fgithub.com\u002Fuber-go\u002Fdig\u002Fissues>.\n",{"name":5,"paths":24,"license":15,"metadata":26,"description":7,"allowed-tools":37,"compatibility":38,"user-invocable":39},[25],"**\u002F*.go",{"author":27,"version":28,"openclaw":29},"samber","1.2.2",{"emoji":30,"install":31,"homepage":32,"requires":33,"skill-library-version":36},"⛏",[],"https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":34},[35],"go","1.19.0","Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch mcp__context7__resolve-library-id mcp__context7__query-docs Bash(godig:*) Bash(gopls:*) LSP mcp__gopls__*","Designed for Claude Code, Codex or similar harness, and for projects using Golang.",true,"main","19f4d52a98d557f3a645a2cfbbeb5bd54f28831d",".github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-uber-dig","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":49,"prompt":59,"zipAvailable":39},[50,53,56],{"tool":51,"command":52},"npx","npx skills add kongnakornna\u002Fgolangapi --skill golang-uber-dig",{"tool":54,"command":55},"bunx","bunx skills add kongnakornna\u002Fgolangapi --skill golang-uber-dig",{"tool":57,"command":58},"pnpm","pnpm dlx skills add kongnakornna\u002Fgolangapi --skill golang-uber-dig","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-uber-dig\u002FSKILL.md",[61,67,71,75],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"evals\u002Fevals.json","REFERENCE","参考文档",12359,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-uber-dig\u002Fevals\u002Fevals.json",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fadvanced.md",5000,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-uber-dig\u002Freferences\u002Fadvanced.md",{"path":72,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Frecipes.md",7456,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-uber-dig\u002Freferences\u002Frecipes.md",{"path":76,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Ftesting.md",4028,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-cc-skills\u002Fskills\u002Fgolang-uber-dig\u002Freferences\u002Ftesting.md",[80,88,95,102,109,116],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"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",[],[]]