[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BQDRS36WFNPVPCX3DHN459":3,"skill-same:01M7BQDRS36WFNPVPCX3DHN459":59},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7BQDRS36WFNPVPCX3DHN459","go-packages",null,"Use when creating or splitting Go packages, organizing imports or dependencies, or structuring a new Go project. Individual identifier naming belongs to go-naming.","h0rn3t\u002Fgolang-skills","h0rn3t","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1213719?v=4","01M7BQBDJ8D4P5W7EQHBD464BX","Eugene Shershen","01M7BQBDJXMTCKNCEDKVEYDRGA",7,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fh0rn3t\u002Fgolang-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgo-packages\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: go-packages\ndescription: Use when creating or splitting Go packages, organizing imports or dependencies, or structuring a new Go project. Individual identifier naming belongs to go-naming.\n---\n\n# Go Packages and Imports\n\n> Compatibility: Baseline Go 1.27 (see [COMPATIBILITY.md](..\u002Fgo-style-core\u002Freferences\u002FCOMPATIBILITY.md)). The `tool`\n> directive requires Go 1.24+; stdlib `uuid` and `encoding\u002Fjson\u002Fv2` Go 1.27+.\n\n## Resource Routing\n\n- `references\u002FIMPORTS.md` - Read when grouping imports, using blank imports, dot imports, or import aliases.\n- `references\u002FPACKAGE-SIZE.md` - Read when splitting packages, avoiding `init`, structuring `main`, or designing CLI flags\u002Fsubcommands.\n- `references\u002FDEPENDENCIES.md` - Read when running `go mod init` or setting the `go` directive, adding a module, using `replace` or `exclude`, pinning a tool, tidying, or scanning before a release.\n\n## Dependency Ladder\n\n> **Normative**: Before adding a module to `go.mod`, check the stdlib. Go 1.27\n> absorbed several of the most-added dependencies.\n\nStop at the first rung that works:\n\n1. **Standard library** — check `go doc \u003Cpkg>` before assuming it is missing\n2. **A module already in `go.mod`** — reuse a suitable supported API\n3. **A new module**, including `golang.org\u002Fx\u002F...` — when the above do not meet\n   the contract or would require materially more implementation and maintenance\n\nJudge suitability by required semantics, supported versions, and maintenance,\nnot line count alone. Existing project conventions take precedence; this ladder\ndoes not require replacing a working dependency in neighboring code. A\ndependency is a convention; a standard-library idiom is not\n([Write Current Go](..\u002Fgo-style-core\u002FSKILL.md#write-current-go)).\n\nCommonly added modules the standard library now covers:\n\n| Was | Use instead | Since |\n|---|---|---|\n| `github.com\u002Fgoogle\u002Fuuid` | `uuid` — `New`\u002F`NewV4`\u002F`NewV7`, `Parse`\u002F`MustParse`, `Nil`\u002F`Max`, `Compare`, text marshaling | 1.27 |\n| A third-party JSON library kept for speed | `encoding\u002Fjson`, which runs on the v2 implementation (unmarshal faster, marshal slower than on 1.26); `encoding\u002Fjson\u002Fv2` + `encoding\u002Fjson\u002Fjsontext` for v2 semantics or streaming | 1.27 |\n| `github.com\u002Fsirupsen\u002Flogrus`, `go.uber.org\u002Fzap` | `log\u002Fslog` (see [go-logging](..\u002Fgo-logging\u002FSKILL.md)) | 1.21 |\n| `github.com\u002Fpkg\u002Ferrors` | `fmt.Errorf` with `%w`, `errors.Is`, `errors.AsType` | 1.13 \u002F 1.26 |\n| `golang.org\u002Fx\u002Fexp\u002Fslices`, `...\u002Fmaps` | `slices`, `maps` | 1.21 |\n| A CSPRNG string helper | `crypto\u002Frand.Text` | 1.24 |\n\n`encoding\u002Fjson\u002Fv2` is not a drop-in replacement for `encoding\u002Fjson`: it changes\n`omitempty`, case-matching, and error semantics. Keep v1 for existing wire\nformats; reach for v2 for new code or when you need `jsontext` streaming. Both\nship in the toolchain — no build tag or `GOEXPERIMENT` needed on Go 1.27.\nFor I\u002FO forms and compatibility options, read\n[JSON v2 at API boundaries](..\u002Fgo-http\u002Freferences\u002FJSON-V2.md).\n\n`github.com\u002Fgoogle\u002Fuuid` stays justified for the algorithms stdlib `uuid` does\nnot have (v1, v3, v5, custom sources).\n\n---\n\n## Adding and Auditing Dependencies\n\n- **Upgrade one module per change** — `go get \u003Cmodule>@\u003Cversion>`, not\n  `go get -u .\u002F...` — so a failure names its cause and the revert is one line;\n  modules that release together count as one. A minor bump needs its release\n  notes read, a major one its migration notes, and a `v0` minor may break.\n  Minimal version selection raises the indirect requirements the new version\n  declares: the `\u002F\u002F indirect` and `go.sum` lines are part of the diff, and\n  `go mod graph | grep \u003Cmodule>@` names who pulled a surprise version. Tests\n  run before and after; `govulncheck` covers the new versions.\n- **A checksum mismatch is a finding.** `SECURITY ERROR` from the `go` command\n  means the bytes differ from `go.sum` or the checksum database: report the\n  module, version, and both hashes. Never edit `go.sum` or set `GOSUMDB`,\n  `GONOSUMDB`, or `GOPRIVATE` to get past it; `go clean -modcache` fixes only\n  what `go mod verify` reports as `dir has been modified`.\n\n`go mod init` and the `go` directive, the pre-add check, `replace` and\n`exclude`, tool pinning, tidy, and the release scan:\n[DEPENDENCIES.md](references\u002FDEPENDENCIES.md).\n\n---\n\n## Package Organization\n\n### Layout\n\n- `cmd\u002F\u003Cbinary>` holds each `main` package; everything it imports lives\n  elsewhere.\n- `internal\u002F` holds packages that are not API. Use it for anything you do not\n  want to support; do not wrap the whole module in `internal\u002Fpkg`. A layer tree\n  (`internal\u002Fhandlers`, `internal\u002Fservices`, `internal\u002Frepositories`,\n  `internal\u002Fmodels`) fits one cohesive service; once several domains change\n  independently, the same layer names move under `internal\u002F\u003Cmodule>\u002F`.\n- Restructuring an existing module — a god package, a global layer tree\n  several domains share, a monolith heading for modules — is\n  [go-code-refactor's ARCHITECTURE.md](..\u002Fgo-code-refactor\u002Freferences\u002FARCHITECTURE.md):\n  the import-graph audit, the target shapes, the staged move, and the\n  boundary test. This skill decides where a *new* package goes.\n- A package with a generic name (`util`, `helper`, `common`, `shared`, `lib`)\n  is a finding: [go-naming](..\u002Fgo-naming\u002Freferences\u002FIDENTIFIERS.md#avoid-uninformative-names)\n  owns the rule and the list.\n\n### Package Size\n\n**Don't split** just because a file is long, to create single-type packages, or\nif it would create circular dependencies.\n\n---\n\n## Imports\n\n| Rule | Guidance |\n|------|----------|\n| Blank imports (`import _`) | Only in `main` packages or tests |\n| `import _ \"embed\"` | Any package, in the file whose `\u002F\u002Fgo:embed` fills a `string` or `[]byte` — the compiler requires it |\n\n---\n\n## Avoid init()\n\nAvoid `init()` where possible. When unavoidable, it must be:\n\n1. Completely deterministic\n2. Independent of other `init()` ordering\n3. Free of environment state and I\u002FO\n\n---\n\n## Exit in Main\n\nCall `os.Exit` or `log.Fatal*` **only in `main()`**. All other functions should\nreturn errors.\n\n**Why**: Non-obvious control flow, untestable, `defer` statements skipped.\n\n**Best practice**: Use the `run()` pattern — extract logic into a `run` that\nreturns an error, called from `main()` with a single exit point:\n\n```go\nfunc main() {\n    if err := run(os.Args[1:], os.Stdout, os.Stderr); err != nil {\n        fmt.Fprintln(os.Stderr, err)\n        os.Exit(1)\n    }\n}\n```\n\nA CLI's `run` takes `args []string, stdout, stderr io.Writer` and builds its\nflag set or command tree inside: a package-level `FlagSet` or cobra root keeps\nflags and state from one test to the next.\n\n---\n\n## Command-Line Flags\n\n> **Advisory**: Define flags only in `package main`.\n\n- Follow the project's flag naming convention; this pack defaults to\n  `snake_case` (`--output_dir`) when none exists.\n- Libraries should accept configuration as parameters, not read flags directly —\n  this keeps them testable and reusable\n- Prefer the standard `flag` package, which already accepts `-v` and `--v` as\n  the same flag; use `pflag` only when POSIX\u002FGNU conventions are required —\n  grouped single-letter flags (`-xvf`) or short\u002Flong pairs (`-v`\u002F`--verbose`)\n\n---\n\n## Build Constraints and Embedded Files\n\n- Platform-specific code lives in `_linux.go` \u002F `_windows.go` suffix files or\n  behind `\u002F\u002Fgo:build linux`; a runtime `if runtime.GOOS == ...` switch is the\n  last resort. Every constrained file needs a fallback so the package still\n  compiles under `go vet .\u002F...` on any GOOS.\n- Static assets (templates, SQL, schemas) ship via `\u002F\u002Fgo:embed` in the package\n  that uses them — never by reading a relative path at runtime, which breaks\n  as soon as the binary runs from another directory.\n\n```go\n\u002F\u002Fgo:embed schema\u002F*.sql\nvar schemaFS embed.FS\n```\n\n---\n\n## Related Skills\n\n- [go-naming](..\u002Fgo-naming\u002FSKILL.md): package names, stuttering, exported symbols.\n- [go-error-handling](..\u002Fgo-error-handling\u002FSKILL.md): `%w` versus `%v` at package boundaries.\n- [go-linting](..\u002Fgo-linting\u002FSKILL.md): goimports local prefixes, import grouping.\n- [go-defensive](..\u002Fgo-defensive\u002FSKILL.md): replacing `init()`, mutable globals.\n","# Go Packages and Imports\n\n> Compatibility: Baseline Go 1.27 (see [COMPATIBILITY.md](..\u002Fgo-style-core\u002Freferences\u002FCOMPATIBILITY.md)). The `tool`\n> directive requires Go 1.24+; stdlib `uuid` and `encoding\u002Fjson\u002Fv2` Go 1.27+.\n\n## Resource Routing\n\n- `references\u002FIMPORTS.md` - Read when grouping imports, using blank imports, dot imports, or import aliases.\n- `references\u002FPACKAGE-SIZE.md` - Read when splitting packages, avoiding `init`, structuring `main`, or designing CLI flags\u002Fsubcommands.\n- `references\u002FDEPENDENCIES.md` - Read when running `go mod init` or setting the `go` directive, adding a module, using `replace` or `exclude`, pinning a tool, tidying, or scanning before a release.\n\n## Dependency Ladder\n\n> **Normative**: Before adding a module to `go.mod`, check the stdlib. Go 1.27\n> absorbed several of the most-added dependencies.\n\nStop at the first rung that works:\n\n1. **Standard library** — check `go doc \u003Cpkg>` before assuming it is missing\n2. **A module already in `go.mod`** — reuse a suitable supported API\n3. **A new module**, including `golang.org\u002Fx\u002F...` — when the above do not meet\n   the contract or would require materially more implementation and maintenance\n\nJudge suitability by required semantics, supported versions, and maintenance,\nnot line count alone. Existing project conventions take precedence; this ladder\ndoes not require replacing a working dependency in neighboring code. A\ndependency is a convention; a standard-library idiom is not\n([Write Current Go](..\u002Fgo-style-core\u002FSKILL.md#write-current-go)).\n\nCommonly added modules the standard library now covers:\n\n| Was | Use instead | Since |\n|---|---|---|\n| `github.com\u002Fgoogle\u002Fuuid` | `uuid` — `New`\u002F`NewV4`\u002F`NewV7`, `Parse`\u002F`MustParse`, `Nil`\u002F`Max`, `Compare`, text marshaling | 1.27 |\n| A third-party JSON library kept for speed | `encoding\u002Fjson`, which runs on the v2 implementation (unmarshal faster, marshal slower than on 1.26); `encoding\u002Fjson\u002Fv2` + `encoding\u002Fjson\u002Fjsontext` for v2 semantics or streaming | 1.27 |\n| `github.com\u002Fsirupsen\u002Flogrus`, `go.uber.org\u002Fzap` | `log\u002Fslog` (see [go-logging](..\u002Fgo-logging\u002FSKILL.md)) | 1.21 |\n| `github.com\u002Fpkg\u002Ferrors` | `fmt.Errorf` with `%w`, `errors.Is`, `errors.AsType` | 1.13 \u002F 1.26 |\n| `golang.org\u002Fx\u002Fexp\u002Fslices`, `...\u002Fmaps` | `slices`, `maps` | 1.21 |\n| A CSPRNG string helper | `crypto\u002Frand.Text` | 1.24 |\n\n`encoding\u002Fjson\u002Fv2` is not a drop-in replacement for `encoding\u002Fjson`: it changes\n`omitempty`, case-matching, and error semantics. Keep v1 for existing wire\nformats; reach for v2 for new code or when you need `jsontext` streaming. Both\nship in the toolchain — no build tag or `GOEXPERIMENT` needed on Go 1.27.\nFor I\u002FO forms and compatibility options, read\n[JSON v2 at API boundaries](..\u002Fgo-http\u002Freferences\u002FJSON-V2.md).\n\n`github.com\u002Fgoogle\u002Fuuid` stays justified for the algorithms stdlib `uuid` does\nnot have (v1, v3, v5, custom sources).\n\n---\n\n## Adding and Auditing Dependencies\n\n- **Upgrade one module per change** — `go get \u003Cmodule>@\u003Cversion>`, not\n  `go get -u .\u002F...` — so a failure names its cause and the revert is one line;\n  modules that release together count as one. A minor bump needs its release\n  notes read, a major one its migration notes, and a `v0` minor may break.\n  Minimal version selection raises the indirect requirements the new version\n  declares: the `\u002F\u002F indirect` and `go.sum` lines are part of the diff, and\n  `go mod graph | grep \u003Cmodule>@` names who pulled a surprise version. Tests\n  run before and after; `govulncheck` covers the new versions.\n- **A checksum mismatch is a finding.** `SECURITY ERROR` from the `go` command\n  means the bytes differ from `go.sum` or the checksum database: report the\n  module, version, and both hashes. Never edit `go.sum` or set `GOSUMDB`,\n  `GONOSUMDB`, or `GOPRIVATE` to get past it; `go clean -modcache` fixes only\n  what `go mod verify` reports as `dir has been modified`.\n\n`go mod init` and the `go` directive, the pre-add check, `replace` and\n`exclude`, tool pinning, tidy, and the release scan:\n[DEPENDENCIES.md](references\u002FDEPENDENCIES.md).\n\n---\n\n## Package Organization\n\n### Layout\n\n- `cmd\u002F\u003Cbinary>` holds each `main` package; everything it imports lives\n  elsewhere.\n- `internal\u002F` holds packages that are not API. Use it for anything you do not\n  want to support; do not wrap the whole module in `internal\u002Fpkg`. A layer tree\n  (`internal\u002Fhandlers`, `internal\u002Fservices`, `internal\u002Frepositories`,\n  `internal\u002Fmodels`) fits one cohesive service; once several domains change\n  independently, the same layer names move under `internal\u002F\u003Cmodule>\u002F`.\n- Restructuring an existing module — a god package, a global layer tree\n  several domains share, a monolith heading for modules — is\n  [go-code-refactor's ARCHITECTURE.md](..\u002Fgo-code-refactor\u002Freferences\u002FARCHITECTURE.md):\n  the import-graph audit, the target shapes, the staged move, and the\n  boundary test. This skill decides where a *new* package goes.\n- A package with a generic name (`util`, `helper`, `common`, `shared`, `lib`)\n  is a finding: [go-naming](..\u002Fgo-naming\u002Freferences\u002FIDENTIFIERS.md#avoid-uninformative-names)\n  owns the rule and the list.\n\n### Package Size\n\n**Don't split** just because a file is long, to create single-type packages, or\nif it would create circular dependencies.\n\n---\n\n## Imports\n\n| Rule | Guidance |\n|------|----------|\n| Blank imports (`import _`) | Only in `main` packages or tests |\n| `import _ \"embed\"` | Any package, in the file whose `\u002F\u002Fgo:embed` fills a `string` or `[]byte` — the compiler requires it |\n\n---\n\n## Avoid init()\n\nAvoid `init()` where possible. When unavoidable, it must be:\n\n1. Completely deterministic\n2. Independent of other `init()` ordering\n3. Free of environment state and I\u002FO\n\n---\n\n## Exit in Main\n\nCall `os.Exit` or `log.Fatal*` **only in `main()`**. All other functions should\nreturn errors.\n\n**Why**: Non-obvious control flow, untestable, `defer` statements skipped.\n\n**Best practice**: Use the `run()` pattern — extract logic into a `run` that\nreturns an error, called from `main()` with a single exit point:\n\n```go\nfunc main() {\n    if err := run(os.Args[1:], os.Stdout, os.Stderr); err != nil {\n        fmt.Fprintln(os.Stderr, err)\n        os.Exit(1)\n    }\n}\n```\n\nA CLI's `run` takes `args []string, stdout, stderr io.Writer` and builds its\nflag set or command tree inside: a package-level `FlagSet` or cobra root keeps\nflags and state from one test to the next.\n\n---\n\n## Command-Line Flags\n\n> **Advisory**: Define flags only in `package main`.\n\n- Follow the project's flag naming convention; this pack defaults to\n  `snake_case` (`--output_dir`) when none exists.\n- Libraries should accept configuration as parameters, not read flags directly —\n  this keeps them testable and reusable\n- Prefer the standard `flag` package, which already accepts `-v` and `--v` as\n  the same flag; use `pflag` only when POSIX\u002FGNU conventions are required —\n  grouped single-letter flags (`-xvf`) or short\u002Flong pairs (`-v`\u002F`--verbose`)\n\n---\n\n## Build Constraints and Embedded Files\n\n- Platform-specific code lives in `_linux.go` \u002F `_windows.go` suffix files or\n  behind `\u002F\u002Fgo:build linux`; a runtime `if runtime.GOOS == ...` switch is the\n  last resort. Every constrained file needs a fallback so the package still\n  compiles under `go vet .\u002F...` on any GOOS.\n- Static assets (templates, SQL, schemas) ship via `\u002F\u002Fgo:embed` in the package\n  that uses them — never by reading a relative path at runtime, which breaks\n  as soon as the binary runs from another directory.\n\n```go\n\u002F\u002Fgo:embed schema\u002F*.sql\nvar schemaFS embed.FS\n```\n\n---\n\n## Related Skills\n\n- [go-naming](..\u002Fgo-naming\u002FSKILL.md): package names, stuttering, exported symbols.\n- [go-error-handling](..\u002Fgo-error-handling\u002FSKILL.md): `%w` versus `%v` at package boundaries.\n- [go-linting](..\u002Fgo-linting\u002FSKILL.md): goimports local prefixes, import grouping.\n- [go-defensive](..\u002Fgo-defensive\u002FSKILL.md): replacing `init()`, mutable globals.\n",{"name":5,"description":7},"main","59ac8ac7a0dd394878aaa0a7a7ecbc227356739f","skills\u002Fgo-packages",2,"https:\u002F\u002Fgithub.com\u002Fh0rn3t\u002Fgolang-skills","https:\u002F\u002Fgithub.com\u002Fh0rn3t","2026-11-14 04:23:12",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add h0rn3t\u002Fgolang-skills --skill go-packages",{"tool":37,"command":38},"bunx","bunx skills add h0rn3t\u002Fgolang-skills --skill go-packages",{"tool":40,"command":41},"pnpm","pnpm dlx skills add h0rn3t\u002Fgolang-skills --skill go-packages","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fh0rn3t\u002Fgolang-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgo-packages\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002FDEPENDENCIES.md","REFERENCE","参考文档",2747,"https:\u002F\u002Fgithub.com\u002Fh0rn3t\u002Fgolang-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgo-packages\u002Freferences\u002FDEPENDENCIES.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002FIMPORTS.md",2302,"https:\u002F\u002Fgithub.com\u002Fh0rn3t\u002Fgolang-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgo-packages\u002Freferences\u002FIMPORTS.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002FPACKAGE-SIZE.md",3588,"https:\u002F\u002Fgithub.com\u002Fh0rn3t\u002Fgolang-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgo-packages\u002Freferences\u002FPACKAGE-SIZE.md",[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7BQEMJBPJWY6CCGVKW27SH0","go-troubleshooting","Use when investigating a bug or ticket in a Go service whose cause is unknown — wrong or missing results, tenant-specific behavior, a regression, stage\u002Fprod\u002FCI differences, a panic, hang, deadlock, leak, unexplained CPU\u002FRSS growth, or a flaky test. Also use for pasted stack traces, profiles, logs, or requests to find a Go issue's root cause, even without the word debug. Does not cover rewriting ticket text, implementing an already-diagnosed fix alone (use its topic skill), or optimizing a known bottleneck (see go-performance).","https:\u002F\u002Fgithub.com\u002Fh0rn3t\u002Fgolang-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgo-troubleshooting\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7BQEFVSRHNDND750SB69WD8","go-testing","Use when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff. Also use when a user asks to write a test for a Go function, even if they don't mention specific patterns like table-driven tests or subtests. Does not cover benchmark performance testing (see go-performance).","https:\u002F\u002Fgithub.com\u002Fh0rn3t\u002Fgolang-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgo-testing\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7BQEA2DRH6H6WFYNJYJJRQQ","go-style-core","Use when resolving Go style or language mechanics such as formatting, nesting, declarations, initialization, scope, shadowing, loops, switches, or enum zero values. API design, naming, errors, and tests have specialized skills.","https:\u002F\u002Fgithub.com\u002Fh0rn3t\u002Fgolang-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgo-style-core\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7BQE3D1H45ANCXAWCS55CDK","go-security","Use when writing or reviewing Go code that touches untrusted input, secrets, or credentials — SQL, shell, or template injection, path traversal, SSRF, cookies and security headers, password hashing, TLS settings, token comparison, or what may appear in a log line. Also use when a handler accepts a file name, URL, or command argument from a client, or when asked to find \"vulnerabilities\", even if the user never says \"security\". Does not cover the os.Root and crypto\u002Frand mechanics (see go-defensive) or the dependency CVE scan in the gate (see go-linting).","https:\u002F\u002Fgithub.com\u002Fh0rn3t\u002Fgolang-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgo-security\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":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7BQDZYHG2YRJA3J26HFPKR7","go-resilience","Use when handling Go dependency failures or overload with retries, backoff\u002Fjitter, budgets, idempotency, duplicate delivery, circuit breakers, bulkheads, rate limits, backpressure, or degradation. Unknown root causes belong to go-troubleshooting.","https:\u002F\u002Fgithub.com\u002Fh0rn3t\u002Fgolang-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgo-resilience\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":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7BQDVG7DH2G9Z97Y8H3P3E9","go-performance","Use when optimizing slow or performance-critical Go code, allocations, string concatenation in loops, or benchmarks. Also use when writing or reviewing a cache, including implementing one from a stub — its key, its expiry, and how a miss loads. Concurrent code patterns belong to go-concurrency.","https:\u002F\u002Fgithub.com\u002Fh0rn3t\u002Fgolang-skills\u002Fblob\u002Fmain\u002Fskills\u002Fgo-performance\u002FSKILL.md",[],[]]