[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AD6DDF5QEW59ZDB4BSNKJ7":3,"skill-same:01M6AD6DDF5QEW59ZDB4BSNKJ7":67},{"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":26,"linkOnly":27,"markdownContent":28,"markdownBody":29,"frontMatter":30,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":38,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M6AD6DDF5QEW59ZDB4BSNKJ7","go-linters",null,"Add and validate custom Go analysis linters in gh-aw.","github\u002Fgh-aw","github","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9919?v=4","01M6AC83DS133TPXFSP1DHNCC6","GitHub","01M6AD3VCZ4WKQSFSRTPN7N9DN",5636,"MIT","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-linters\u002FSKILL.md",[],[19,20,21,22,23,24,25],"go","go linters","validate","analysis","gh","add","custom","2026-11-10 10:12:30",false,"---\nname: go-linters\ndescription: Add and validate custom Go analysis linters in gh-aw.\n---\n\n# Go Linters\n\nUse this guide when adding a new custom Go analysis linter in this repository.\n\nFor PR-driven linter generation (derive a rule from a specific pull request pattern), use `.github\u002Fskills\u002Fpr-to-go-linter\u002FSKILL.md`.\n\n## Where to add a new linter\n\n1. Create a new package under `pkg\u002Flinters\u002F\u003Clinter-name>\u002F`.\n2. Define an analyzer in that package (exported as `Analyzer`).\n3. Add tests in the same package using `analysistest` with fixtures under `testdata\u002Fsrc\u002F...`.\n4. Register the analyzer in `cmd\u002Flinters\u002Fmain.go` so it runs via the multichecker binary.\n\n## Build and test linters\n\n- Test only your linter package:\n  - `go test .\u002Fpkg\u002Flinters\u002F\u003Clinter-name>\u002F...`\n- Build the custom linter runner:\n  - `go build .\u002Fcmd\u002Flinters`\n- Run all custom linters across the repo:\n  - `make golint-custom`\n\n`make golint-custom` builds `cmd\u002Flinters` and runs it against `.\u002Fcmd\u002F...` and `.\u002Fpkg\u002F...`.\n\n## Common AST pitfalls\n\n### Unwrap parenthesized expressions\n\nExpressions wrapped in parentheses appear as `*ast.ParenExpr`. Unwrap expressions before\nasserting their AST type or comparing identifiers, so forms such as `(nil)` and `(err)` are\nhandled like `nil` and `err`. Use the shared helper:\n\n```go\nif ident, ok := astutil.UnwrapParenExpr(expr).(*ast.Ident); ok && ident.Name == \"nil\" {\n\t\u002F\u002F Handle nil.\n}\n```\n\n### Match all relevant statement shapes\n\nSemantically similar calls can appear in different statement nodes. A call that discards a\nresult may be a bare `*ast.ExprStmt` or part of an `*ast.AssignStmt`; filtering only for one\nshape misses the other. Include and handle each relevant node shape:\n\n```go\nnodeFilter := []ast.Node{(*ast.AssignStmt)(nil), (*ast.ExprStmt)(nil)}\nreturn analyzerutil.Preorder(pass, nodeFilter, func(n ast.Node) {\n\tswitch stmt := n.(type) {\n\tcase *ast.AssignStmt:\n\t\tanalyzeAssign(stmt)\n\tcase *ast.ExprStmt:\n\t\tanalyzeExpr(stmt)\n\t}\n})\n```\n\nBefore submitting a linter, check expression-shape assertions for parenthesis unwrapping and\nverify its node filter covers relevant equivalent syntax forms.\n\n## Coverage-aware perf gating\n\nFor linters that flag micro-optimizations (allocation\u002Fperf rules), only apply them on lines that\ntests actually exercise — \"hot paths\" — rather than on dead or rarely-executed code where the\noptimization brings no measurable benefit. Use the shared `pkg\u002Flinters\u002Finternal\u002Fcoverage` package:\n\n1. In your analyzer file, register a `-hot-threshold` flag in `init()` (not as a var initializer,\n   to avoid an `Analyzer`\u002F`run`\u002Fflag initialization cycle):\n\n   ```go\n   var hotThreshold *int\n\n   func init() {\n       hotThreshold = coverage.RegisterHotThresholdFlag(Analyzer)\n   }\n   ```\n\n2. Immediately before reporting a diagnostic, gate it with `coverage.ShouldApply`:\n\n   ```go\n   if !coverage.ShouldApply(pass, node.Pos(), *hotThreshold) {\n       return\n   }\n   ```\n\n`coverage.ShouldApply` is permissive by default: when no coverage profile is loaded via the\n`GH_AW_LINT_COVERAGE_PROFILE` environment variable, or when `hot-threshold` is `0`, it always\nreturns `true`, preserving pre-coverage-aware behavior. Only wire this into linters whose fix has\na genuine performance rationale (extra allocations, O(n²) behavior, etc.) — purely\nreadability\u002Fstyle linters should not be coverage-gated.\n\n### Generating the coverage profile\n\n```bash\ngo test -covermode=count -coverprofile=\u002Ftmp\u002Fcoverage.out .\u002F...\nexport GH_AW_LINT_COVERAGE_PROFILE=\u002Ftmp\u002Fcoverage.out\nmake golint-custom\n```\n\nThis profile is read once per linter-runner process. To lint only a specific subtree, scope\nthe `go test` and `golint-custom` commands to the same package path.\n","# Go Linters\n\nUse this guide when adding a new custom Go analysis linter in this repository.\n\nFor PR-driven linter generation (derive a rule from a specific pull request pattern), use `.github\u002Fskills\u002Fpr-to-go-linter\u002FSKILL.md`.\n\n## Where to add a new linter\n\n1. Create a new package under `pkg\u002Flinters\u002F\u003Clinter-name>\u002F`.\n2. Define an analyzer in that package (exported as `Analyzer`).\n3. Add tests in the same package using `analysistest` with fixtures under `testdata\u002Fsrc\u002F...`.\n4. Register the analyzer in `cmd\u002Flinters\u002Fmain.go` so it runs via the multichecker binary.\n\n## Build and test linters\n\n- Test only your linter package:\n  - `go test .\u002Fpkg\u002Flinters\u002F\u003Clinter-name>\u002F...`\n- Build the custom linter runner:\n  - `go build .\u002Fcmd\u002Flinters`\n- Run all custom linters across the repo:\n  - `make golint-custom`\n\n`make golint-custom` builds `cmd\u002Flinters` and runs it against `.\u002Fcmd\u002F...` and `.\u002Fpkg\u002F...`.\n\n## Common AST pitfalls\n\n### Unwrap parenthesized expressions\n\nExpressions wrapped in parentheses appear as `*ast.ParenExpr`. Unwrap expressions before\nasserting their AST type or comparing identifiers, so forms such as `(nil)` and `(err)` are\nhandled like `nil` and `err`. Use the shared helper:\n\n```go\nif ident, ok := astutil.UnwrapParenExpr(expr).(*ast.Ident); ok && ident.Name == \"nil\" {\n\t\u002F\u002F Handle nil.\n}\n```\n\n### Match all relevant statement shapes\n\nSemantically similar calls can appear in different statement nodes. A call that discards a\nresult may be a bare `*ast.ExprStmt` or part of an `*ast.AssignStmt`; filtering only for one\nshape misses the other. Include and handle each relevant node shape:\n\n```go\nnodeFilter := []ast.Node{(*ast.AssignStmt)(nil), (*ast.ExprStmt)(nil)}\nreturn analyzerutil.Preorder(pass, nodeFilter, func(n ast.Node) {\n\tswitch stmt := n.(type) {\n\tcase *ast.AssignStmt:\n\t\tanalyzeAssign(stmt)\n\tcase *ast.ExprStmt:\n\t\tanalyzeExpr(stmt)\n\t}\n})\n```\n\nBefore submitting a linter, check expression-shape assertions for parenthesis unwrapping and\nverify its node filter covers relevant equivalent syntax forms.\n\n## Coverage-aware perf gating\n\nFor linters that flag micro-optimizations (allocation\u002Fperf rules), only apply them on lines that\ntests actually exercise — \"hot paths\" — rather than on dead or rarely-executed code where the\noptimization brings no measurable benefit. Use the shared `pkg\u002Flinters\u002Finternal\u002Fcoverage` package:\n\n1. In your analyzer file, register a `-hot-threshold` flag in `init()` (not as a var initializer,\n   to avoid an `Analyzer`\u002F`run`\u002Fflag initialization cycle):\n\n   ```go\n   var hotThreshold *int\n\n   func init() {\n       hotThreshold = coverage.RegisterHotThresholdFlag(Analyzer)\n   }\n   ```\n\n2. Immediately before reporting a diagnostic, gate it with `coverage.ShouldApply`:\n\n   ```go\n   if !coverage.ShouldApply(pass, node.Pos(), *hotThreshold) {\n       return\n   }\n   ```\n\n`coverage.ShouldApply` is permissive by default: when no coverage profile is loaded via the\n`GH_AW_LINT_COVERAGE_PROFILE` environment variable, or when `hot-threshold` is `0`, it always\nreturns `true`, preserving pre-coverage-aware behavior. Only wire this into linters whose fix has\na genuine performance rationale (extra allocations, O(n²) behavior, etc.) — purely\nreadability\u002Fstyle linters should not be coverage-gated.\n\n### Generating the coverage profile\n\n```bash\ngo test -covermode=count -coverprofile=\u002Ftmp\u002Fcoverage.out .\u002F...\nexport GH_AW_LINT_COVERAGE_PROFILE=\u002Ftmp\u002Fcoverage.out\nmake golint-custom\n```\n\nThis profile is read once per linter-runner process. To lint only a specific subtree, scope\nthe `go test` and `golint-custom` commands to the same package path.\n",{"name":5,"description":7},"main","8541229759617347888641eba917d3b0ad66a984",".github\u002Fskills\u002Fgo-linters",626,"https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw","https:\u002F\u002Fgh.io\u002Fgh-aw","https:\u002F\u002Fgithub.com\u002Fgithub","https:\u002F\u002Fgithub.com\u002Fabout","How people build software.","2026-11-15 06:45:15",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add github\u002Fgh-aw --skill go-linters",{"tool":47,"command":48},"bunx","bunx skills add github\u002Fgh-aw --skill go-linters",{"tool":50,"command":51},"pnpm","pnpm dlx skills add github\u002Fgh-aw --skill go-linters","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgo-linters\u002FSKILL.md",true,[55,61],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fdecision-log-template.tsv","REFERENCE","参考文档",38,"https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002Fpstack\u002Fupstream\u002Fskills\u002Fshow-me-your-work\u002Freferences\u002Fdecision-log-template.tsv",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"scripts\u002Flog.sh","SCRIPT","脚本",1377,"https:\u002F\u002Fgithub.com\u002Fbnferguson\u002Fdotfiles\u002Fblob\u002Fmain\u002Fpstack\u002Fupstream\u002Fskills\u002Fshow-me-your-work\u002Fscripts\u002Flog.sh",[68,76,84,112,130,155],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":75},"01M7DQYVZ9W9DDXKQ9452SNP8J","cracktro","Edit, preview, and verify the standalone interactive talk deck in docs\u002Fpublic\u002Fcracktro (slides, SVG diagrams, transitions, WebAudio sound).","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcracktro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":83},"01M7612HQ4378TK8QZ5HPAF4KR","create-connector","Create or extend a declaration-only third-party connector, with narrow reads, separate safe outputs, optional protected triggers, and offline conformance evidence.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fcreate-connector\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"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":98,"publishedAt":26},"01M6ADC942STTXHFV410J4DH0X","GitHub Agentic Workflows","GitHub Agentic Workflows (`gh-aw`) is a GitHub CLI extension for writing Agentic Workflows in markdown and compiling them to GitHub Actions.","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002FSKILL.md",[90,95],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000023","Skill与智能体开发",[9,99,100,101,102,103,104,105,106,23,107,108,109,110,111],"github agentic workflows","agentic workflows","workflows","agentic","extension","markdown","github cli","cli","for","compiling","writing","github actions","actions",{"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":26},"01M6ADC6ZXSA46N9XD6VNAP1MS","windows-compatibility","Cross-platform path handling and command patterns","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fwindows-compatibility\u002FSKILL.md",[],[119,120,121,122,123,124,125,126,127,128,129],"windows","windows compatibility","compatibility","command","git","bugs","platform","high","patterns","cross-platform","path",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":26},"01M6ADC44957SVQF96R5YY247P","versioning-policy","Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Fversioning-policy\u002FSKILL.md",[],[137,138,139,140,141,106,142,143,144,145,146,147,148,149,107,150,151,152,153,154],"versioning","policy","versioning policy","gate","implementation","workspace","pr","sdk","release","ci","npm","semver","squad","incident","incidents","Rules","version","resolution",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":165,"publishedAt":26},"01M6ADC1PHMEAEVR87F8PDR89X","tiered-memory","Three-tier agent memory model (hot\u002Fcold\u002Fwiki) for context reduction per spawn","https:\u002F\u002Fgithub.com\u002Fgithub\u002Fgh-aw\u002Fblob\u002Fmain\u002F.squad\u002Ftemplates\u002Fskills\u002Ftiered-memory\u002FSKILL.md",[161,164],{"categoryNo":162,"categoryName":163,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":96,"categoryName":97,"taxonomyType":93,"taxonomyTypeDesc":94},[166,167,168,169,170,171,172,173,174,175,176,177,178,107,179,180],"tiered memory","memory","performance","design","agent memory","proposal","cold","model","wiki","spawn","memory-management","context","three","runtime","management"]