[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79ZXWQVFTF8QEVVWXTAPQND":3,"skill-same:01M79ZXWQVFTF8QEVVWXTAPQND":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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79ZXWQVFTF8QEVVWXTAPQND","go-naming",null,"Use when naming any Go identifier — packages, types, functions, methods, variables, constants, or receivers — to ensure idiomatic, clear names. Also use when a user is creating new types, packages, or exported APIs, even if they don't explicitly ask about naming conventions. Does not cover package organization (see go-packages).","kongnakornna\u002Fgolangapi","kongnakornna","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10528904?v=4","01M79Z5JQPPV5CWQHXS235Q9MD","Kongnakorn Jantakun","01M79Z5JRHJJJ6PR2DGQS4P985",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgolang-skills\u002Fskills\u002Fgo-naming\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: go-naming\ndescription: Use when naming any Go identifier — packages, types, functions, methods, variables, constants, or receivers — to ensure idiomatic, clear names. Also use when a user is creating new types, packages, or exported APIs, even if they don't explicitly ask about naming conventions. Does not cover package organization (see go-packages).\nallowed-tools: Bash(bash:*)\n---\n\n# Go Naming Conventions\n\n## Resource Routing\n\n- `scripts\u002Fcheck-naming.sh` - Run when checking SCREAMING_SNAKE_CASE constants, Get-prefixed getters, generic package names, or receivers named `this`\u002F`self`.\n- `references\u002FIDENTIFIERS.md` - Read when choosing names for initialisms, exported identifiers, or package-level symbols.\n- `references\u002FREPETITION.md` - Read when names repeat package, receiver, type, or local context.\n- `references\u002FVARIABLES.md` - Read when choosing local variable names, receiver names, or loop identifiers.\n\n## Core Principle\n\nNames should:\n- Not feel repetitive when used\n- Take context into consideration\n- Not repeat concepts that are already clear\n\nNaming is more art than science—Go names tend to be shorter than in other\nlanguages.\n\n---\n\n## Naming Decision Flow\n\n```\nWhat are you naming?\n├─ Package       → Short, lowercase, singular noun (no underscores, no mixedCaps)\n├─ Interface     → Method name + \"-er\" suffix when single-method (Reader, Writer)\n├─ Receiver      → 1-2 letter abbreviation of type (c for Client); consistent across methods\n├─ Constant      → MixedCaps; use iota for enums; no ALL_CAPS\n├─ Exported func → Verb or verb-phrase in MixedCaps; no Get prefix for getters\n├─ Variable      → Length proportional to scope distance\n│                  ├─ Tiny scope (1-7 lines) → single letter (i, n, r)\n│                  ├─ Medium scope           → short word (count, buf)\n│                  └─ Package-level \u002F wide   → descriptive (userAccountCount)\n└─ Any name      → Check: does it repeat package name or context? If yes, shorten it\n```\n\n---\n\n## MixedCaps (Required)\n\n> **Normative**: All Go identifiers must use MixedCaps.\n\nUnderscores are allowed only in: test functions (`TestFoo_InvalidInput`),\ngenerated code, and OS\u002Fcgo interop.\n\n---\n\n## Package Names\n\n> **Normative**: Packages must be lowercase with no underscores.\n\nShort, lowercase, singular nouns. Avoid generic names like `util`, `common`,\n`helper` — prefer specific names: `stringutil`, `httpauth`, `configloader`.\n\n```go\n\u002F\u002F Good: user, oauth2, tabwriter\n\u002F\u002F Bad:  user_service, UserService, count (shadows var)\n```\n\n---\n\n## Interface Names\n\n> **Advisory**: One-method interfaces use \"-er\" suffix.\n\nName one-method interfaces by the method plus `-er`: `Reader`, `Writer`,\n`Formatter`. Honor canonical method names (`Read`, `Write`, `Close`, `String`)\nand their signatures.\n\n---\n\n## Receiver Names\n\n> **Normative**: Receivers must be short abbreviations, used consistently.\n\nOne or two letters abbreviating the type, consistent across all methods:\n`func (c *Client) Connect()`, `func (c *Client) Send()`.\nNever use `this` or `self`.\n\n---\n\n## Constant Names\n\n> **Normative**: Constants use MixedCaps, never ALL_CAPS or K prefix.\n\nName constants by role, not value: `MaxRetries` not `Three`,\n`DefaultPort` not `Port8080`.\n\n```go\nconst MaxPacketSize = 512\nconst defaultTimeout = 30 * time.Second\n```\n\n---\n\n## Initialisms and Acronyms\n\n> **Normative**: Initialisms maintain consistent case throughout.\n\nInitialisms (URL, ID, HTTP, API) must be all uppercase or all lowercase:\n`HTTPClient`, `userID`, `ParseURL()` — not `HttpClient`, `orderId`, `ParseUrl()`.\n\n---\n\n## Function and Method Names\n\n> **Advisory**: No `Get` prefix for simple accessors; use verb-like names for actions.\n\nGetter for field `owner` is `Owner()`, not `GetOwner()`. Setter is\n`SetOwner()`. Use `Compute` or `Fetch` for expensive operations.\n\nWhen functions differ only by type, include type at the end:\n`ParseInt()`, `ParseInt64()`.\n\n---\n\n## Variable Names\n\nVariable naming balances brevity with clarity. Key principles:\n\n- **Scope-based length**: Short names (`i`, `v`) for small scopes; longer,\n  descriptive names for larger scopes\n- **Single-letter conventions**: Use familiar patterns (`i` for index,\n  `r`\u002F`w` for reader\u002Fwriter)\n- **Avoid type in name**: Use `users` not `userSlice`, `name` not `nameString`\n- **Prefix unexported globals**: Use `_` prefix for package-level unexported\n  vars\u002Fconsts to prevent shadowing\n\n```go\nfor i, v := range items { ... }           \u002F\u002F small scope\npendingOrders := filterPending(orders)    \u002F\u002F larger scope\nconst _defaultPort = 8080                 \u002F\u002F unexported global\n```\n\n---\n\n## Avoiding Repetition\n\nGo names should not feel repetitive when used. Consider the full context:\n\n- **Package + symbol**: `widget.New()` not `widget.NewWidget()`\n- **Receiver + method**: `p.Name()` not `p.ProjectName()`\n- **Context + type**: In package `sqldb`, use `Connection` not `DBConnection`\n\n---\n\n## Avoid Built-In Names\n\nNever shadow Go's predeclared identifiers (`error`, `string`, `len`, `cap`,\n`append`, `copy`, `new`, `make`, etc.) as variable, parameter, or type names.\n\n**For detailed guidance**: See `go-declarations` — \"Avoid Using Built-In Names\"\nsection.\n\n---\n\n## Quick Reference\n\n| Element | Rule | Example |\n|---------|------|---------|\n| Package | lowercase, no underscores | `package httputil` |\n| Exported | MixedCaps, starts uppercase | `func ParseURL()` |\n| Unexported | mixedCaps, starts lowercase | `func parseURL()` |\n| Receiver | 1-2 letter abbreviation | `func (c *Client)` |\n| Constant | MixedCaps, never ALL_CAPS | `const MaxSize = 100` |\n| Initialism | consistent case | `userID`, `XMLAPI` |\n| Variable | length ~ scope size | `i` (small), `userCount` (large) |\n| Built-in names | Never shadow predeclared identifiers | See `go-declarations` |\n\n> **Validation**: After renaming identifiers, run `bash scripts\u002Fcheck-naming.sh` to verify no naming anti-patterns remain. Then run `go build .\u002F...` to confirm the rename didn't break anything.\n\n## Related Skills\n\n- **Interface naming**: See [go-interfaces](..\u002Fgo-interfaces\u002FSKILL.md) when naming interfaces with the `-er` suffix or choosing receiver types\n- **Package naming**: See [go-packages](..\u002Fgo-packages\u002FSKILL.md) when naming packages, avoiding `util`\u002F`common`, or resolving import collisions\n- **Error naming**: See [go-error-handling](..\u002Fgo-error-handling\u002FSKILL.md) when naming sentinel errors (`ErrFoo`) or custom error types\n- **Declaration scope**: See [go-declarations](..\u002Fgo-declarations\u002FSKILL.md) when variable name length depends on scope or when avoiding built-in shadowing\n- **Style principles**: See [go-style-core](..\u002Fgo-style-core\u002FSKILL.md) when balancing clarity vs concision in identifier names\n","# Go Naming Conventions\n\n## Resource Routing\n\n- `scripts\u002Fcheck-naming.sh` - Run when checking SCREAMING_SNAKE_CASE constants, Get-prefixed getters, generic package names, or receivers named `this`\u002F`self`.\n- `references\u002FIDENTIFIERS.md` - Read when choosing names for initialisms, exported identifiers, or package-level symbols.\n- `references\u002FREPETITION.md` - Read when names repeat package, receiver, type, or local context.\n- `references\u002FVARIABLES.md` - Read when choosing local variable names, receiver names, or loop identifiers.\n\n## Core Principle\n\nNames should:\n- Not feel repetitive when used\n- Take context into consideration\n- Not repeat concepts that are already clear\n\nNaming is more art than science—Go names tend to be shorter than in other\nlanguages.\n\n---\n\n## Naming Decision Flow\n\n```\nWhat are you naming?\n├─ Package       → Short, lowercase, singular noun (no underscores, no mixedCaps)\n├─ Interface     → Method name + \"-er\" suffix when single-method (Reader, Writer)\n├─ Receiver      → 1-2 letter abbreviation of type (c for Client); consistent across methods\n├─ Constant      → MixedCaps; use iota for enums; no ALL_CAPS\n├─ Exported func → Verb or verb-phrase in MixedCaps; no Get prefix for getters\n├─ Variable      → Length proportional to scope distance\n│                  ├─ Tiny scope (1-7 lines) → single letter (i, n, r)\n│                  ├─ Medium scope           → short word (count, buf)\n│                  └─ Package-level \u002F wide   → descriptive (userAccountCount)\n└─ Any name      → Check: does it repeat package name or context? If yes, shorten it\n```\n\n---\n\n## MixedCaps (Required)\n\n> **Normative**: All Go identifiers must use MixedCaps.\n\nUnderscores are allowed only in: test functions (`TestFoo_InvalidInput`),\ngenerated code, and OS\u002Fcgo interop.\n\n---\n\n## Package Names\n\n> **Normative**: Packages must be lowercase with no underscores.\n\nShort, lowercase, singular nouns. Avoid generic names like `util`, `common`,\n`helper` — prefer specific names: `stringutil`, `httpauth`, `configloader`.\n\n```go\n\u002F\u002F Good: user, oauth2, tabwriter\n\u002F\u002F Bad:  user_service, UserService, count (shadows var)\n```\n\n---\n\n## Interface Names\n\n> **Advisory**: One-method interfaces use \"-er\" suffix.\n\nName one-method interfaces by the method plus `-er`: `Reader`, `Writer`,\n`Formatter`. Honor canonical method names (`Read`, `Write`, `Close`, `String`)\nand their signatures.\n\n---\n\n## Receiver Names\n\n> **Normative**: Receivers must be short abbreviations, used consistently.\n\nOne or two letters abbreviating the type, consistent across all methods:\n`func (c *Client) Connect()`, `func (c *Client) Send()`.\nNever use `this` or `self`.\n\n---\n\n## Constant Names\n\n> **Normative**: Constants use MixedCaps, never ALL_CAPS or K prefix.\n\nName constants by role, not value: `MaxRetries` not `Three`,\n`DefaultPort` not `Port8080`.\n\n```go\nconst MaxPacketSize = 512\nconst defaultTimeout = 30 * time.Second\n```\n\n---\n\n## Initialisms and Acronyms\n\n> **Normative**: Initialisms maintain consistent case throughout.\n\nInitialisms (URL, ID, HTTP, API) must be all uppercase or all lowercase:\n`HTTPClient`, `userID`, `ParseURL()` — not `HttpClient`, `orderId`, `ParseUrl()`.\n\n---\n\n## Function and Method Names\n\n> **Advisory**: No `Get` prefix for simple accessors; use verb-like names for actions.\n\nGetter for field `owner` is `Owner()`, not `GetOwner()`. Setter is\n`SetOwner()`. Use `Compute` or `Fetch` for expensive operations.\n\nWhen functions differ only by type, include type at the end:\n`ParseInt()`, `ParseInt64()`.\n\n---\n\n## Variable Names\n\nVariable naming balances brevity with clarity. Key principles:\n\n- **Scope-based length**: Short names (`i`, `v`) for small scopes; longer,\n  descriptive names for larger scopes\n- **Single-letter conventions**: Use familiar patterns (`i` for index,\n  `r`\u002F`w` for reader\u002Fwriter)\n- **Avoid type in name**: Use `users` not `userSlice`, `name` not `nameString`\n- **Prefix unexported globals**: Use `_` prefix for package-level unexported\n  vars\u002Fconsts to prevent shadowing\n\n```go\nfor i, v := range items { ... }           \u002F\u002F small scope\npendingOrders := filterPending(orders)    \u002F\u002F larger scope\nconst _defaultPort = 8080                 \u002F\u002F unexported global\n```\n\n---\n\n## Avoiding Repetition\n\nGo names should not feel repetitive when used. Consider the full context:\n\n- **Package + symbol**: `widget.New()` not `widget.NewWidget()`\n- **Receiver + method**: `p.Name()` not `p.ProjectName()`\n- **Context + type**: In package `sqldb`, use `Connection` not `DBConnection`\n\n---\n\n## Avoid Built-In Names\n\nNever shadow Go's predeclared identifiers (`error`, `string`, `len`, `cap`,\n`append`, `copy`, `new`, `make`, etc.) as variable, parameter, or type names.\n\n**For detailed guidance**: See `go-declarations` — \"Avoid Using Built-In Names\"\nsection.\n\n---\n\n## Quick Reference\n\n| Element | Rule | Example |\n|---------|------|---------|\n| Package | lowercase, no underscores | `package httputil` |\n| Exported | MixedCaps, starts uppercase | `func ParseURL()` |\n| Unexported | mixedCaps, starts lowercase | `func parseURL()` |\n| Receiver | 1-2 letter abbreviation | `func (c *Client)` |\n| Constant | MixedCaps, never ALL_CAPS | `const MaxSize = 100` |\n| Initialism | consistent case | `userID`, `XMLAPI` |\n| Variable | length ~ scope size | `i` (small), `userCount` (large) |\n| Built-in names | Never shadow predeclared identifiers | See `go-declarations` |\n\n> **Validation**: After renaming identifiers, run `bash scripts\u002Fcheck-naming.sh` to verify no naming anti-patterns remain. Then run `go build .\u002F...` to confirm the rename didn't break anything.\n\n## Related Skills\n\n- **Interface naming**: See [go-interfaces](..\u002Fgo-interfaces\u002FSKILL.md) when naming interfaces with the `-er` suffix or choosing receiver types\n- **Package naming**: See [go-packages](..\u002Fgo-packages\u002FSKILL.md) when naming packages, avoiding `util`\u002F`common`, or resolving import collisions\n- **Error naming**: See [go-error-handling](..\u002Fgo-error-handling\u002FSKILL.md) when naming sentinel errors (`ErrFoo`) or custom error types\n- **Declaration scope**: See [go-declarations](..\u002Fgo-declarations\u002FSKILL.md) when variable name length depends on scope or when avoiding built-in shadowing\n- **Style principles**: See [go-style-core](..\u002Fgo-style-core\u002FSKILL.md) when balancing clarity vs concision in identifier names\n",{"name":5,"description":7,"allowed-tools":24},"Bash(bash:*)","main","19f4d52a98d557f3a645a2cfbbeb5bd54f28831d",".github\u002Fskills\u002Fgolang-skills\u002Fskills\u002Fgo-naming","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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add kongnakornna\u002Fgolangapi --skill go-naming",{"tool":39,"command":40},"bunx","bunx skills add kongnakornna\u002Fgolangapi --skill go-naming",{"tool":42,"command":43},"pnpm","pnpm dlx skills add kongnakornna\u002Fgolangapi --skill go-naming","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgolang-skills\u002Fskills\u002Fgo-naming\u002FSKILL.md",true,[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002FIDENTIFIERS.md","REFERENCE","参考文档",4607,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgolang-skills\u002Fskills\u002Fgo-naming\u002Freferences\u002FIDENTIFIERS.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002FREPETITION.md",2030,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgolang-skills\u002Fskills\u002Fgo-naming\u002Freferences\u002FREPETITION.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002FVARIABLES.md",2912,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgolang-skills\u002Fskills\u002Fgo-naming\u002Freferences\u002FVARIABLES.md",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"scripts\u002Fcheck-naming.sh","SCRIPT","脚本",8020,"https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fgolang-skills\u002Fskills\u002Fgo-naming\u002Fscripts\u002Fcheck-naming.sh",[68,75,82,89,96,103],{"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":19},"01M7A0M9RJJ3383VEFYKABWV15","tb-writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fkongnakornna\u002Fgolangapi\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftb-writing-plans\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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",[],[]]