[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79AQMZDE3M0179V1TAS4JS6":3,"skill-same:01M79AQMZDE3M0179V1TAS4JS6":76},{"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":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":61},"01M79AQMZDE3M0179V1TAS4JS6","golang-how-to",null,"Golang skills orchestrator — always active on any Golang coding, review, debug, or setup task. Reads the task context and loads the most relevant skills from samber\u002Fcc-skills-golang, often multiple at once: writing a gRPC service loads golang-grpc + golang-testing + golang-error-handling; debugging a panic loads golang-troubleshooting + golang-safety; auditing security loads golang-security + golang-lint + golang-safety. Also: disambiguates competing clusters when two skills seem to overlap (performance vs benchmark vs troubleshooting, samber\u002Flo vs mo vs ro, DI cluster, safety vs security), and configures CLAUDE.md or AGENTS.md to force-trigger skills in a project (\u002Fgolang-how-to configure).","CCH-HQ\u002Fcchp-automation","CCH-HQ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F253065381?v=4","01M79AG9QPRTJEVTCT1ZS7TM9J","CCH HQ","01M79AG9RNM4TAB3PJQH71X62P",2,"MIT","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-how-to\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: golang-how-to\ndescription: \"Golang skills orchestrator — always active on any Golang coding, review, debug, or setup task. Reads the task context and loads the most relevant skills from samber\u002Fcc-skills-golang, often multiple at once: writing a gRPC service loads golang-grpc + golang-testing + golang-error-handling; debugging a panic loads golang-troubleshooting + golang-safety; auditing security loads golang-security + golang-lint + golang-safety. Also: disambiguates competing clusters when two skills seem to overlap (performance vs benchmark vs troubleshooting, samber\u002Flo vs mo vs ro, DI cluster, safety vs security), and configures CLAUDE.md or AGENTS.md to force-trigger skills in a project (\u002Fgolang-how-to configure).\"\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code or similar AI coding agents. Requires git.\nmetadata:\n  author: samber\n  version: \"1.3.0\"\n  openclaw:\n    emoji: \"🧭\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\n    requires:\n      bins:\n        - go\n        - gopls\n    install:\n      - kind: go\n        package: golang.org\u002Fx\u002Ftools\u002Fgopls@latest\n        bins: [gopls]\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(git:*) Agent AskUserQuestion LSP Bash(gopls:*) mcp__gopls__*\n---\n\n**Persona:** You are a Go skills orchestrator. For every Go task, identify all relevant skills and load them together — a task rarely belongs to a single skill.\n\n**Dependencies:** `gopls` — `go install golang.org\u002Fx\u002Ftools\u002Fgopls@latest`; the built-in `LSP` tool also needs `ENABLE_LSP_TOOL=1` and a Go language server wired (see [Code navigation with gopls](#code-navigation-with-gopls)).\n\n**Modes:**\n\n- **Orchestrate** — for any Go coding, review, debug, or setup task, load the primary skill plus all applicable secondary skills simultaneously.\n- **Disambiguate** — when two skills seem to overlap, show the boundary table. See [disambiguation.md](references\u002Fdisambiguation.md).\n- **Configure** — write the always-load directive for `golang-how-to` itself, plus an optional `## Required Go skills` block, to the project's `CLAUDE.md` or `AGENTS.md`. Follow [project-config.md](references\u002Fproject-config.md).\n\n## Skill loading\n\nFor each task, load the **primary skill** and all applicable **secondary skills** at the same time. Do not wait — load them together at the start.\n\n| Intent | Primary | Also load |\n| --- | --- | --- |\n| Design an API, choose a pattern | `golang-design-patterns` | `golang-structs-interfaces`, `golang-naming` |\n| Name a type, function, or package | `golang-naming` | `golang-code-style` |\n| Handle errors idiomatically | `golang-error-handling` | `golang-safety` (nil-heavy code) |\n| Write goroutines, channels, sync | `golang-concurrency` | `golang-context` (if cancellation) |\n| Pass deadlines \u002F cancel operations | `golang-context` | `golang-concurrency` (if goroutines) |\n| Design structs, embed, use interfaces | `golang-structs-interfaces` | `golang-design-patterns` |\n| Database queries and transactions | `golang-database` | `golang-error-handling`, `golang-security` |\n| Build a gRPC service | `golang-grpc` | `golang-testing`, `golang-error-handling` |\n| Build a GraphQL API | `golang-graphql` | `golang-testing`, `golang-error-handling` |\n| Build a CLI command tree | `golang-spf13-cobra` | `golang-cli`, `golang-spf13-viper` (if config) |\n| Layer config from flags\u002Fenv\u002Ffile | `golang-spf13-viper` | `golang-spf13-cobra` |\n| Write tests | `golang-testing` | `golang-stretchr-testify` (if using testify) |\n| Apply optimization patterns | `golang-performance` | `golang-benchmark` (measure first) |\n| Measure with pprof \u002F benchstat | `golang-benchmark` | `golang-performance` (fix), `golang-troubleshooting` (root cause) |\n| Debug a panic or unexpected behavior | `golang-troubleshooting` | `golang-safety`, `golang-benchmark` (if perf-related) |\n| Monitor in production | `golang-observability` | `golang-performance` (if SLO breach) |\n| Audit security vulnerabilities | `golang-security` | `golang-safety`, `golang-lint` |\n| Review formatting and style | `golang-code-style` | `golang-naming`, `golang-lint` |\n| Refactor or restructure existing code | `golang-refactoring` | `golang-naming`, `golang-code-style`, `golang-project-layout` |\n| Configure golangci-lint | `golang-lint` | `golang-code-style` |\n| Write godoc \u002F README \u002F CHANGELOG | `golang-documentation` | `golang-naming` |\n| Set up a new project structure | `golang-project-layout` | `golang-design-patterns`, `golang-dependency-injection`, `golang-lint` |\n| Set up CI\u002FCD pipeline | `golang-continuous-integration` | `golang-lint`, `golang-security` |\n| Choose a library | `golang-popular-libraries` | relevant library-specific skill |\n| Look up a package's docs, versions, importers, or CVEs | `golang-pkg-go-dev` | `golang-dependency-management` |\n| Navigate, diagnose, or refactor local code (definitions, references, rename) | `golang-gopls` | — |\n| Adopt new Go language features | `golang-modernize` | `golang-lint` |\n| Use samber\u002Flo (slice\u002Fmap helpers) | `golang-samber-lo` | `golang-data-structures`, `golang-performance` |\n| Use samber\u002Foops (structured errors) | `golang-samber-oops` | `golang-error-handling` |\n| Use log\u002Fslog | `golang-samber-slog` | `golang-observability`, `golang-error-handling` |\n| Use dependency injection | `golang-dependency-injection` | `golang-google-wire` or `golang-uber-dig` or `golang-uber-fx` or `golang-samber-do` |\n\nAll skill identifiers above are short forms of `samber\u002Fcc-skills-golang@\u003Cname>`.\n\n## Code navigation with gopls\n\n`gopls` gives semantic code intelligence for Go — go-to-definition, find references, diagnostics, package API, symbol search, refactoring. → See `samber\u002Fcc-skills-golang@golang-gopls` skill for the three ways to reach it (its own MCP server, the native `LSP` tool, and its CLI), the full capability matrix, and efficient read\u002Fedit workflows.\n\n`gopls` only reasons about code that is present and resolvable in the local build: your workspace plus every dependency exactly as pinned in `go.sum` (including `replace` directives). For any fact that isn't tied to your local build — version history, licenses, ecosystem-wide importers, a package you haven't added yet — use `golang-pkg-go-dev` (`godig`). See the `godig` vs gopls vs Context7 vs govulncheck section below for the full boundary.\n\n## `godig` vs gopls vs Context7 vs govulncheck\n\nFour tools can answer \"is this dependency OK to use,\" and they don't overlap as much as they look:\n\n- **Context7** is a general-purpose, cross-language documentation fetcher — useful when no more specific source exists. For a Go package or module, `godig` is almost always the better choice: it pulls **structured, Go-specific data** straight from pkg.go.dev — exact versions, exported symbols with signatures, runnable examples, `imported-by`, and known vulnerabilities — rather than Context7's generic scraped\u002Fcurated docs, which don't expose that structure and can lag or miss lesser-known Go modules. Reach for Context7 only when a dependency's documentation genuinely doesn't exist or isn't indexed on pkg.go.dev.\n- **`godig`** answers questions about the **published ecosystem**: any Go package or module, whether or not it's in your `go.mod` yet — it calls the remote pkg.go.dev API and never touches your local checkout. Its `vulns` command reports CVEs known for a package\u002Fversion in isolation, regardless of whether your build actually reaches the vulnerable code path.\n- **`gopls`** (→ `samber\u002Fcc-skills-golang@golang-gopls`, via its MCP server, the native `LSP` tool, or its CLI) answers questions about **your specific build**: your code plus every dependency exactly as pinned in `go.sum`, including `replace` directives pointing at forks or local paths — neither `godig` nor Context7 can see that. Its `go_vulncheck` operation runs a single, on-demand reachability check against the workspace as it stands right now.\n- **`govulncheck`** (the standalone CLI, wrapped by the `samber\u002Fcc-skills-golang@golang-security` skill) is the whole-tree audit: it walks the entire module's call graph to confirm which known vulnerabilities are actually reachable, and is the tool of record for CI gates and periodic security sweeps — `gopls`'s `go_vulncheck` is a lighter-weight, single-shot version of the same analysis for use mid-edit.\n\nPick by task:\n\n| Task | Tool | How |\n| --- | --- | --- |\n| Find where a symbol is defined in your own repo | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — `go_search`, then `go_file_context` |\n| Understand a file's intra-package dependencies | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — `go_file_context` |\n| Jump into a dependency's exact resolved source (incl. forks\u002F`replace`d versions) | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — `go_package_api`, or the native `LSP` tool's `goToDefinition` |\n| Find every call site in your own code that references a dependency's symbol | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — `go_symbol_references` — `godig`'s `imported-by` only lists public _packages_, not call sites in your repo |\n| Get compiler diagnostics right after an edit | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — `go_diagnostics` (MCP), or automatic with the native `LSP` tool |\n| Check whether your current build can reach a known vulnerability, mid-edit | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — `go_vulncheck` |\n| Rename, extract, inline, or otherwise refactor local code | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — safe rename, `refactor.*` code actions |\n| Whole-tree vulnerability audit across the module (CI, periodic sweep) | `govulncheck` | `samber\u002Fcc-skills-golang@golang-security` skill — `govulncheck .\u002F...` |\n| List available versions of a published package | `godig` | `godig versions \u003Cpath>` |\n| Check known CVEs for a package\u002Fversion you haven't added yet | `godig` | `godig vulns \u003Cpath>` |\n| See exported symbols\u002Fsignatures of a published package | `godig` | `godig symbols` \u002F `symbol doc` |\n| Get runnable code examples for a symbol | `godig` | `godig symbol examples` |\n| Read a package's rendered README\u002Fdocs | `godig` | `godig module readme` \u002F `package doc` |\n| See who imports a package across the whole public ecosystem | `godig` | `godig imported-by` |\n| Search for a package or library candidate | `godig` | `godig search` |\n| Check a package's or module's license | `godig` | `godig package licenses` \u002F `module licenses` |\n| Get docs for a non-Go library, or a Go module not indexed on pkg.go.dev | Context7 | `resolve-library-id` \u002F `query-docs` |\n\nSee the `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill for the full `godig` command reference, and the `samber\u002Fcc-skills-golang@golang-security` skill for the whole-tree `govulncheck` remediation workflow.\n\n## Categories at a glance\n\nFull catalog with \"use when\" hooks: [by-category.md](references\u002Fby-category.md)\n\n| Category | Skills |\n| --- | --- |\n| Code Quality | `golang-code-style` `golang-documentation` `golang-error-handling` `golang-lint` `golang-naming` `golang-safety` `golang-security` `golang-structs-interfaces` |\n| Architecture & Design | `golang-concurrency` `golang-context` `golang-data-structures` `golang-database` `golang-dependency-injection` `golang-design-patterns` `golang-modernize` `golang-refactoring` |\n| QA & Performance | `golang-benchmark` `golang-observability` `golang-performance` `golang-testing` `golang-troubleshooting` |\n| Project Setup | `golang-cli` `golang-continuous-integration` `golang-dependency-management` `golang-gopls` `golang-pkg-go-dev` `golang-popular-libraries` `golang-project-layout` `golang-stay-updated` |\n| APIs | `golang-graphql` `golang-grpc` `golang-swagger` |\n| Dependency Injection | `golang-dependency-injection` `golang-google-wire` `golang-uber-dig` `golang-uber-fx` `golang-samber-do` |\n| Frameworks | `golang-spf13-cobra` `golang-spf13-viper` |\n| samber\u002F\\* | `golang-samber-do` `golang-samber-hot` `golang-samber-lo` `golang-samber-mo` `golang-samber-oops` `golang-samber-ro` `golang-samber-slog` |\n| Testing | `golang-stretchr-testify` `golang-testing` |\n\n## Competing clusters — boundary lines\n\nFull boundary tables with routing examples: [disambiguation.md](references\u002Fdisambiguation.md)\n\nKey clusters and their owners:\n\n- **Performance**: `golang-performance` (optimization patterns) · `golang-benchmark` (measurement) · `golang-troubleshooting` (root cause) · `golang-observability` (always-on production)\n- **DI**: `golang-dependency-injection` (concepts\u002Fdecision) · `golang-google-wire` (compile-time) · `golang-uber-dig` (runtime reflection) · `golang-uber-fx` (lifecycle framework) · `golang-samber-do` (type-safe container)\n- **samber\u002F\\***: `golang-samber-lo` (finite transforms) · `golang-samber-ro` (reactive streams) · `golang-samber-mo` (monadic types)\n- **Errors**: `golang-error-handling` (idioms) · `golang-samber-oops` (structured errors) · `golang-safety` (prevent panics)\n- **Style**: `golang-code-style` · `golang-naming` · `golang-lint` · `golang-documentation`\n- **CLI**: `golang-cli` (architecture) · `golang-spf13-cobra` (command tree) · `golang-spf13-viper` (config layering)\n- **Package lookup**: `golang-pkg-go-dev` (query pkg.go.dev for an existing path: versions\u002Fdocs\u002Fsymbols\u002Fimporters\u002FCVEs) · `golang-gopls` (navigate\u002Frefactor your locally resolved build) · `golang-popular-libraries` (which library to adopt) · `golang-dependency-management` (manage go.mod) · `golang-security` (whole-tree CVE scan)\n- **Gap — type vs arch**: `golang-structs-interfaces` (type design) vs `golang-design-patterns` (architectural patterns)\n- **Gap — goroutine vs cancel**: `golang-concurrency` + `golang-context` — load both when cancelling goroutines via context\n- **Gap — correctness vs threat**: `golang-safety` (internal bugs) vs `golang-security` (external threats)\n- **Gap — features vs rules**: `golang-modernize` (language adoption) vs `golang-lint` (static analysis config)\n- **Gap — process vs target rules**: `golang-refactoring` (the safe, staged, at-scale _process_ of changing existing code — planning, ordering, gopls-driven mechanics, staged PRs) vs `golang-naming`\u002F`golang-code-style`\u002F`golang-project-layout`\u002F`golang-design-patterns`\u002F`golang-modernize` (what the resulting code should look like) — load `golang-refactoring` alongside whichever of these owns the target shape\n\n## Configure mode\n\nWrite an always-load directive for `golang-how-to` itself to a project's `CLAUDE.md` or `AGENTS.md`, and optionally force-trigger specific secondary skills too.\n\n`samber\u002Fcc-skills-golang@golang-project-layout` writes the always-load directive automatically at project creation, with no user confirmation needed — it costs one skill description and never imposes project-specific choices. Running `\u002Fgolang-how-to configure` writes it too if missing, and additionally lets the user confirm a `## Required Go skills` block for skills that must always apply beyond routing. Follow [project-config.md](references\u002Fproject-config.md).\n\n---\n\nThis skill is not exhaustive. Refer to individual skill files and the official Go documentation for detailed guidance.\n\nIf you encounter a bug or unexpected behavior in this skill plugin, open an issue at \u003Chttps:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\u002Fissues>.\n","**Persona:** You are a Go skills orchestrator. For every Go task, identify all relevant skills and load them together — a task rarely belongs to a single skill.\n\n**Dependencies:** `gopls` — `go install golang.org\u002Fx\u002Ftools\u002Fgopls@latest`; the built-in `LSP` tool also needs `ENABLE_LSP_TOOL=1` and a Go language server wired (see [Code navigation with gopls](#code-navigation-with-gopls)).\n\n**Modes:**\n\n- **Orchestrate** — for any Go coding, review, debug, or setup task, load the primary skill plus all applicable secondary skills simultaneously.\n- **Disambiguate** — when two skills seem to overlap, show the boundary table. See [disambiguation.md](references\u002Fdisambiguation.md).\n- **Configure** — write the always-load directive for `golang-how-to` itself, plus an optional `## Required Go skills` block, to the project's `CLAUDE.md` or `AGENTS.md`. Follow [project-config.md](references\u002Fproject-config.md).\n\n## Skill loading\n\nFor each task, load the **primary skill** and all applicable **secondary skills** at the same time. Do not wait — load them together at the start.\n\n| Intent | Primary | Also load |\n| --- | --- | --- |\n| Design an API, choose a pattern | `golang-design-patterns` | `golang-structs-interfaces`, `golang-naming` |\n| Name a type, function, or package | `golang-naming` | `golang-code-style` |\n| Handle errors idiomatically | `golang-error-handling` | `golang-safety` (nil-heavy code) |\n| Write goroutines, channels, sync | `golang-concurrency` | `golang-context` (if cancellation) |\n| Pass deadlines \u002F cancel operations | `golang-context` | `golang-concurrency` (if goroutines) |\n| Design structs, embed, use interfaces | `golang-structs-interfaces` | `golang-design-patterns` |\n| Database queries and transactions | `golang-database` | `golang-error-handling`, `golang-security` |\n| Build a gRPC service | `golang-grpc` | `golang-testing`, `golang-error-handling` |\n| Build a GraphQL API | `golang-graphql` | `golang-testing`, `golang-error-handling` |\n| Build a CLI command tree | `golang-spf13-cobra` | `golang-cli`, `golang-spf13-viper` (if config) |\n| Layer config from flags\u002Fenv\u002Ffile | `golang-spf13-viper` | `golang-spf13-cobra` |\n| Write tests | `golang-testing` | `golang-stretchr-testify` (if using testify) |\n| Apply optimization patterns | `golang-performance` | `golang-benchmark` (measure first) |\n| Measure with pprof \u002F benchstat | `golang-benchmark` | `golang-performance` (fix), `golang-troubleshooting` (root cause) |\n| Debug a panic or unexpected behavior | `golang-troubleshooting` | `golang-safety`, `golang-benchmark` (if perf-related) |\n| Monitor in production | `golang-observability` | `golang-performance` (if SLO breach) |\n| Audit security vulnerabilities | `golang-security` | `golang-safety`, `golang-lint` |\n| Review formatting and style | `golang-code-style` | `golang-naming`, `golang-lint` |\n| Refactor or restructure existing code | `golang-refactoring` | `golang-naming`, `golang-code-style`, `golang-project-layout` |\n| Configure golangci-lint | `golang-lint` | `golang-code-style` |\n| Write godoc \u002F README \u002F CHANGELOG | `golang-documentation` | `golang-naming` |\n| Set up a new project structure | `golang-project-layout` | `golang-design-patterns`, `golang-dependency-injection`, `golang-lint` |\n| Set up CI\u002FCD pipeline | `golang-continuous-integration` | `golang-lint`, `golang-security` |\n| Choose a library | `golang-popular-libraries` | relevant library-specific skill |\n| Look up a package's docs, versions, importers, or CVEs | `golang-pkg-go-dev` | `golang-dependency-management` |\n| Navigate, diagnose, or refactor local code (definitions, references, rename) | `golang-gopls` | — |\n| Adopt new Go language features | `golang-modernize` | `golang-lint` |\n| Use samber\u002Flo (slice\u002Fmap helpers) | `golang-samber-lo` | `golang-data-structures`, `golang-performance` |\n| Use samber\u002Foops (structured errors) | `golang-samber-oops` | `golang-error-handling` |\n| Use log\u002Fslog | `golang-samber-slog` | `golang-observability`, `golang-error-handling` |\n| Use dependency injection | `golang-dependency-injection` | `golang-google-wire` or `golang-uber-dig` or `golang-uber-fx` or `golang-samber-do` |\n\nAll skill identifiers above are short forms of `samber\u002Fcc-skills-golang@\u003Cname>`.\n\n## Code navigation with gopls\n\n`gopls` gives semantic code intelligence for Go — go-to-definition, find references, diagnostics, package API, symbol search, refactoring. → See `samber\u002Fcc-skills-golang@golang-gopls` skill for the three ways to reach it (its own MCP server, the native `LSP` tool, and its CLI), the full capability matrix, and efficient read\u002Fedit workflows.\n\n`gopls` only reasons about code that is present and resolvable in the local build: your workspace plus every dependency exactly as pinned in `go.sum` (including `replace` directives). For any fact that isn't tied to your local build — version history, licenses, ecosystem-wide importers, a package you haven't added yet — use `golang-pkg-go-dev` (`godig`). See the `godig` vs gopls vs Context7 vs govulncheck section below for the full boundary.\n\n## `godig` vs gopls vs Context7 vs govulncheck\n\nFour tools can answer \"is this dependency OK to use,\" and they don't overlap as much as they look:\n\n- **Context7** is a general-purpose, cross-language documentation fetcher — useful when no more specific source exists. For a Go package or module, `godig` is almost always the better choice: it pulls **structured, Go-specific data** straight from pkg.go.dev — exact versions, exported symbols with signatures, runnable examples, `imported-by`, and known vulnerabilities — rather than Context7's generic scraped\u002Fcurated docs, which don't expose that structure and can lag or miss lesser-known Go modules. Reach for Context7 only when a dependency's documentation genuinely doesn't exist or isn't indexed on pkg.go.dev.\n- **`godig`** answers questions about the **published ecosystem**: any Go package or module, whether or not it's in your `go.mod` yet — it calls the remote pkg.go.dev API and never touches your local checkout. Its `vulns` command reports CVEs known for a package\u002Fversion in isolation, regardless of whether your build actually reaches the vulnerable code path.\n- **`gopls`** (→ `samber\u002Fcc-skills-golang@golang-gopls`, via its MCP server, the native `LSP` tool, or its CLI) answers questions about **your specific build**: your code plus every dependency exactly as pinned in `go.sum`, including `replace` directives pointing at forks or local paths — neither `godig` nor Context7 can see that. Its `go_vulncheck` operation runs a single, on-demand reachability check against the workspace as it stands right now.\n- **`govulncheck`** (the standalone CLI, wrapped by the `samber\u002Fcc-skills-golang@golang-security` skill) is the whole-tree audit: it walks the entire module's call graph to confirm which known vulnerabilities are actually reachable, and is the tool of record for CI gates and periodic security sweeps — `gopls`'s `go_vulncheck` is a lighter-weight, single-shot version of the same analysis for use mid-edit.\n\nPick by task:\n\n| Task | Tool | How |\n| --- | --- | --- |\n| Find where a symbol is defined in your own repo | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — `go_search`, then `go_file_context` |\n| Understand a file's intra-package dependencies | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — `go_file_context` |\n| Jump into a dependency's exact resolved source (incl. forks\u002F`replace`d versions) | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — `go_package_api`, or the native `LSP` tool's `goToDefinition` |\n| Find every call site in your own code that references a dependency's symbol | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — `go_symbol_references` — `godig`'s `imported-by` only lists public _packages_, not call sites in your repo |\n| Get compiler diagnostics right after an edit | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — `go_diagnostics` (MCP), or automatic with the native `LSP` tool |\n| Check whether your current build can reach a known vulnerability, mid-edit | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — `go_vulncheck` |\n| Rename, extract, inline, or otherwise refactor local code | `gopls` | `samber\u002Fcc-skills-golang@golang-gopls` — safe rename, `refactor.*` code actions |\n| Whole-tree vulnerability audit across the module (CI, periodic sweep) | `govulncheck` | `samber\u002Fcc-skills-golang@golang-security` skill — `govulncheck .\u002F...` |\n| List available versions of a published package | `godig` | `godig versions \u003Cpath>` |\n| Check known CVEs for a package\u002Fversion you haven't added yet | `godig` | `godig vulns \u003Cpath>` |\n| See exported symbols\u002Fsignatures of a published package | `godig` | `godig symbols` \u002F `symbol doc` |\n| Get runnable code examples for a symbol | `godig` | `godig symbol examples` |\n| Read a package's rendered README\u002Fdocs | `godig` | `godig module readme` \u002F `package doc` |\n| See who imports a package across the whole public ecosystem | `godig` | `godig imported-by` |\n| Search for a package or library candidate | `godig` | `godig search` |\n| Check a package's or module's license | `godig` | `godig package licenses` \u002F `module licenses` |\n| Get docs for a non-Go library, or a Go module not indexed on pkg.go.dev | Context7 | `resolve-library-id` \u002F `query-docs` |\n\nSee the `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill for the full `godig` command reference, and the `samber\u002Fcc-skills-golang@golang-security` skill for the whole-tree `govulncheck` remediation workflow.\n\n## Categories at a glance\n\nFull catalog with \"use when\" hooks: [by-category.md](references\u002Fby-category.md)\n\n| Category | Skills |\n| --- | --- |\n| Code Quality | `golang-code-style` `golang-documentation` `golang-error-handling` `golang-lint` `golang-naming` `golang-safety` `golang-security` `golang-structs-interfaces` |\n| Architecture & Design | `golang-concurrency` `golang-context` `golang-data-structures` `golang-database` `golang-dependency-injection` `golang-design-patterns` `golang-modernize` `golang-refactoring` |\n| QA & Performance | `golang-benchmark` `golang-observability` `golang-performance` `golang-testing` `golang-troubleshooting` |\n| Project Setup | `golang-cli` `golang-continuous-integration` `golang-dependency-management` `golang-gopls` `golang-pkg-go-dev` `golang-popular-libraries` `golang-project-layout` `golang-stay-updated` |\n| APIs | `golang-graphql` `golang-grpc` `golang-swagger` |\n| Dependency Injection | `golang-dependency-injection` `golang-google-wire` `golang-uber-dig` `golang-uber-fx` `golang-samber-do` |\n| Frameworks | `golang-spf13-cobra` `golang-spf13-viper` |\n| samber\u002F\\* | `golang-samber-do` `golang-samber-hot` `golang-samber-lo` `golang-samber-mo` `golang-samber-oops` `golang-samber-ro` `golang-samber-slog` |\n| Testing | `golang-stretchr-testify` `golang-testing` |\n\n## Competing clusters — boundary lines\n\nFull boundary tables with routing examples: [disambiguation.md](references\u002Fdisambiguation.md)\n\nKey clusters and their owners:\n\n- **Performance**: `golang-performance` (optimization patterns) · `golang-benchmark` (measurement) · `golang-troubleshooting` (root cause) · `golang-observability` (always-on production)\n- **DI**: `golang-dependency-injection` (concepts\u002Fdecision) · `golang-google-wire` (compile-time) · `golang-uber-dig` (runtime reflection) · `golang-uber-fx` (lifecycle framework) · `golang-samber-do` (type-safe container)\n- **samber\u002F\\***: `golang-samber-lo` (finite transforms) · `golang-samber-ro` (reactive streams) · `golang-samber-mo` (monadic types)\n- **Errors**: `golang-error-handling` (idioms) · `golang-samber-oops` (structured errors) · `golang-safety` (prevent panics)\n- **Style**: `golang-code-style` · `golang-naming` · `golang-lint` · `golang-documentation`\n- **CLI**: `golang-cli` (architecture) · `golang-spf13-cobra` (command tree) · `golang-spf13-viper` (config layering)\n- **Package lookup**: `golang-pkg-go-dev` (query pkg.go.dev for an existing path: versions\u002Fdocs\u002Fsymbols\u002Fimporters\u002FCVEs) · `golang-gopls` (navigate\u002Frefactor your locally resolved build) · `golang-popular-libraries` (which library to adopt) · `golang-dependency-management` (manage go.mod) · `golang-security` (whole-tree CVE scan)\n- **Gap — type vs arch**: `golang-structs-interfaces` (type design) vs `golang-design-patterns` (architectural patterns)\n- **Gap — goroutine vs cancel**: `golang-concurrency` + `golang-context` — load both when cancelling goroutines via context\n- **Gap — correctness vs threat**: `golang-safety` (internal bugs) vs `golang-security` (external threats)\n- **Gap — features vs rules**: `golang-modernize` (language adoption) vs `golang-lint` (static analysis config)\n- **Gap — process vs target rules**: `golang-refactoring` (the safe, staged, at-scale _process_ of changing existing code — planning, ordering, gopls-driven mechanics, staged PRs) vs `golang-naming`\u002F`golang-code-style`\u002F`golang-project-layout`\u002F`golang-design-patterns`\u002F`golang-modernize` (what the resulting code should look like) — load `golang-refactoring` alongside whichever of these owns the target shape\n\n## Configure mode\n\nWrite an always-load directive for `golang-how-to` itself to a project's `CLAUDE.md` or `AGENTS.md`, and optionally force-trigger specific secondary skills too.\n\n`samber\u002Fcc-skills-golang@golang-project-layout` writes the always-load directive automatically at project creation, with no user confirmation needed — it costs one skill description and never imposes project-specific choices. Running `\u002Fgolang-how-to configure` writes it too if missing, and additionally lets the user confirm a `## Required Go skills` block for skills that must always apply beyond routing. Follow [project-config.md](references\u002Fproject-config.md).\n\n---\n\nThis skill is not exhaustive. Refer to individual skill files and the official Go documentation for detailed guidance.\n\nIf you encounter a bug or unexpected behavior in this skill plugin, open an issue at \u003Chttps:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\u002Fissues>.\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":38,"compatibility":39,"user-invocable":40},{"author":25,"version":26,"openclaw":27},"samber","1.3.0",{"emoji":28,"install":29,"homepage":35,"requires":36},"🧭",[30],{"bins":31,"kind":33,"package":34},[32],"gopls","go","golang.org\u002Fx\u002Ftools\u002Fgopls@latest","https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":37},[33,32],"Read Edit Write Glob Grep Bash(go:*) Bash(git:*) Agent AskUserQuestion LSP Bash(gopls:*) mcp__gopls__*","Designed for Claude Code or similar AI coding agents. Requires git.",true,"main","a93764baed707eda5a68d91e19e5719368e6335e","skills-backup\u002Fskills\u002Fgolang-how-to",0,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation","https:\u002F\u002Fgithub.com\u002FCCH-HQ","https:\u002F\u002Fclaude-code-hub.app\u002F","2026-11-09 20:50:54",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":40},[51,54,57],{"tool":52,"command":53},"npx","npx skills add CCH-HQ\u002Fcchp-automation --skill golang-how-to",{"tool":55,"command":56},"bunx","bunx skills add CCH-HQ\u002Fcchp-automation --skill golang-how-to",{"tool":58,"command":59},"pnpm","pnpm dlx skills add CCH-HQ\u002Fcchp-automation --skill golang-how-to","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-how-to\u002FSKILL.md",[62,68,72],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fby-category.md","REFERENCE","参考文档",15968,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-how-to\u002Freferences\u002Fby-category.md",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fdisambiguation.md",19678,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-how-to\u002Freferences\u002Fdisambiguation.md",{"path":73,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fproject-config.md",7389,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-how-to\u002Freferences\u002Fproject-config.md",[77,84,91,98,105,112],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79B44RKSB6Z0GENGYFCCZYA","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M79B410BHDSNHZ7MKAYXWJHS","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M79B3XK29MCD5HGD50YGYXQZ","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M79B3TFQEXXM2KK5V44H64DV","wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M79B3Q3WTMJDM6NNGG1X4NYK","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M79B3GW8YCKT7W489HKWFMNC","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[]]