[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E5CM90RC78TQ90YV97QSD2":3,"skill-same:01M7E5CM90RC78TQ90YV97QSD2":70},{"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":39,"commitSha":40,"skillDirectory":41,"forksCount":14,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":45,"updatedAt":46,"install":47,"resources":59},"01M7E5CM90RC78TQ90YV97QSD2","golang-code-style",null,"Write or review Go declarations, control flow, formatting, and comments for clarity. Follow existing repository style and formatter configuration; avoid unrelated cosmetic rewrites.","w0rxbend\u002Fdot-agents","w0rxbend","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F8176996?v=4","01M7E4XY3Y871Z2NFBXF3H3T8F","Oleksandr B.","01M7E4XY51E6NSG05FXR36H9RV",0,"MIT","https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents\u002Fblob\u002Fmain\u002Fskills\u002Fgo\u002Fgolang-code-style\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: golang-code-style\ndescription: \"Write or review Go declarations, control flow, formatting, and comments for clarity. Follow existing repository style and formatter configuration; avoid unrelated cosmetic rewrites.\"\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code, Codex or similar harness, and for projects using Golang.\nmetadata:\n  author: samber\n  version: \"1.3.0\"\n  openclaw:\n    emoji: \"🎨\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\n    requires:\n      bins:\n        - go\n    install: []\nallowed-tools: Read Edit Write Glob Grep Bash(gofmt:*) Bash(go build:*) Bash(go vet:*) Bash(golangci-lint run:*) Bash(git status:*) Bash(git diff:*) Bash(git log:*) Bash(git show:*) Agent\npaths:\n  - \"**\u002F*.go\"\n---\n\n> **Community default.** Company skill explicitly superseding `samber\u002Fcc-skills-golang@golang-code-style` skill wins.\n\n# Go Code Style\n\nStyle rules needing human judgment. Linters handle formatting; this skill handles clarity.\n\n> \"Clear is better than clever.\" — Go Proverbs\n\nWhen ignoring a rule, add a code comment.\n\n## Line Length & Breaking\n\nNo rigid limit, but lines over ~120 characters MUST break, at **semantic boundaries**, not arbitrary columns. Calls with 4+ arguments SHOULD go one argument per line when otherwise long and repository already formats them so. If user explicitly asks for single-line code, comply:\n\n```go\n\u002F\u002F Good — each argument on its own line, closing paren separate\nmux.HandleFunc(\"\u002Fapi\u002Fusers\", func(w http.ResponseWriter, r *http.Request) {\n    handleUsers(\n        w,\n        r,\n        serviceName,\n        cfg,\n        logger,\n        authMiddleware,\n    )\n})\n```\n\nSignature too long: real fix often **fewer parameters** (options struct), not better wrapping. Multi-line signatures: one parameter per line.\n\n## Variable Declarations\n\nSHOULD use `:=` for non-zero values, `var` for zero-value initialization. Form signals intent: `var` means \"this starts at zero.\"\n\n```go\nvar count int              \u002F\u002F zero value, set later\nname := \"default\"          \u002F\u002F non-zero, := is appropriate\nvar buf bytes.Buffer       \u002F\u002F zero value is ready to use\n```\n\n### Slice & Map Initialization\n\nInitialize maps before writes; nil maps panic on write. Nil slice (`var s []T`) is idiomatic zero value; `len`, `append` and `range` work on it (Go Code Review Comments prefers it). Initialize slices explicitly (`[]T{}` or `make`) where difference is observable: JSON encoding (nil encodes as `null`, empty as `[]`), APIs whose callers distinguish nil from empty, or existing repository practice.\n\n```go\nvar users []User                        \u002F\u002F nil slice: fine for internal use\nusers := []User{}                       \u002F\u002F empty, encodes as [] in JSON\nm := map[string]int{}                   \u002F\u002F maps must be initialized before writes\nusers := make([]User, 0, len(ids))      \u002F\u002F preallocate when capacity is known\nm := make(map[string]int, len(items))   \u002F\u002F preallocate when size is known\n```\n\nDo not preallocate speculatively: `make([]T, 0, 1000)` wastes memory when common case is 10 items.\n\n### Composite Literals\n\nComposite literals MUST use field names — positional fields break when type adds or reorders fields:\n\n```go\nsrv := &http.Server{\n    Addr:         \":8080\",\n    ReadTimeout:  5 * time.Second,\n    WriteTimeout: 10 * time.Second,\n}\n```\n\n## Control Flow\n\n### Reduce Nesting\n\nMUST handle errors and edge cases first (early return). Happy path stays at minimal indentation:\n\n```go\nfunc process(data []byte) (*Result, error) {\n    if len(data) == 0 {\n        return nil, errors.New(\"empty data\")\n    }\n\n    parsed, err := parse(data)\n    if err != nil {\n        return nil, fmt.Errorf(\"parsing: %w\", err)\n    }\n\n    return transform(parsed), nil\n}\n```\n\n### Eliminate Unnecessary `else`\n\nIf `if` body ends with `return`\u002F`break`\u002F`continue`, MUST drop `else`. Simple assignments: default-then-override (assign default, override via independent conditions or `switch`):\n\n```go\n\u002F\u002F Good — default-then-override with switch (cleanest for mutually exclusive overrides)\nlevel := slog.LevelInfo\nswitch {\ncase debug:\n    level = slog.LevelDebug\ncase verbose:\n    level = slog.LevelWarn\n}\n\n\u002F\u002F Bad — else-if chain hides that there's a default\nif debug {\n    level = slog.LevelDebug\n} else if verbose {\n    level = slog.LevelWarn\n} else {\n    level = slog.LevelInfo\n}\n```\n\n### Complex Conditions & Init Scope\n\n`if` with 3+ operands: MUST extract named booleans. Wall of `||` is unreadable, hides business logic. Keep expensive checks inline (short-circuit). [Details](.\u002Freferences\u002Fdetails.md)\n\n```go\n\u002F\u002F Good — named booleans make intent clear\nisAdmin := user.Role == RoleAdmin\nisOwner := resource.OwnerID == user.ID\nisPublicVerified := resource.IsPublic && user.IsVerified\nif isAdmin || isOwner || isPublicVerified || permissions.Contains(PermOverride) {\n    allow()\n}\n```\n\nScope variables to `if` when only check needs them:\n\n```go\nif err := validate(input); err != nil {\n    return err\n}\n```\n\n### Switch Over If-Else Chains\n\nSame variable compared repeatedly: prefer `switch`:\n\n```go\nswitch status {\ncase StatusActive:\n    activate()\ncase StatusInactive:\n    deactivate()\ndefault:\n    panic(fmt.Sprintf(\"unexpected status: %d\", status))\n}\n```\n\n## Function Design\n\n- Functions SHOULD be **short and focused**: one function, one job.\n- Functions SHOULD have **≤4 parameters**; beyond that, options struct (see `samber\u002Fcc-skills-golang@golang-design-patterns` skill).\n- **Parameter order**: `context.Context` first, then inputs, then output destinations.\n- Naked returns help in very short functions (1-3 lines) with obvious return values. Longer functions: name returns explicitly, else readers scroll to find what's returned.\n\n```go\nfunc FetchUser(ctx context.Context, id string) (*User, error)\nfunc SendEmail(ctx context.Context, msg EmailMessage) error  \u002F\u002F grouped into struct\n```\n\n### Prefer `range` for Iteration\n\nSHOULD use `range` over index-based loops. `range n` (Go 1.22+) for simple counting.\n\n```go\nfor _, user := range users {\n    process(user)\n}\n```\n\n## Value vs Pointer Arguments\n\nPass small types (`string`, `int`, `bool`, `time.Time`) by value. Pointers for mutation, large structs (~128+ bytes), or meaningful nil. [Details](.\u002Freferences\u002Fdetails.md)\n\n## Code Organization Within Files\n\n- **Group related declarations**: type, constructor, methods together\n- **Order**: package doc, imports, constants, types, constructors, methods, helpers\n- **One primary type per file** when it has significant methods\n- **Blank imports** (`_ \"pkg\"`) register side effects (init functions). Restrict to `main` and test packages so side effects show at application root, not hidden in library code\n- **Dot imports** pollute namespace and hide where a name comes from — never use in library code\n- **Unexport aggressively** — can always export later; unexporting is a breaking change. Unexport safely with `samber\u002Fcc-skills-golang@golang-gopls` skill: its rename updates every call site atomically and refuses when lowercasing a method would break interface satisfaction, a breakage grep\u002Fsed silently ships.\n\n## String Handling\n\nUse `strconv` for simple conversions (faster), `fmt.Sprintf` for complex formatting. Use `%q` in error messages to show string boundaries. `strings.Builder` in loops, `+` for simple concatenation.\n\n## Type Conversions\n\nPrefer explicit, narrow conversions. Generics over `any` when concrete type will do:\n\n```go\nfunc Contains[T comparable](slice []T, target T) bool  \u002F\u002F not []any\n```\n\n## Philosophy\n\n- **\"A little copying is better than a little dependency\"**\n- **Use `slices` and `maps` standard packages**; for filter\u002Fgroup-by\u002Fchunk, use `github.com\u002Fsamber\u002Flo`\n- **\"Reflection is never clear\"** — avoid `reflect` unless necessary\n- **Don't abstract prematurely** — extract once pattern is stable\n- **Minimize public surface** — every exported name is a commitment\n\n## Parallelizing Code Style Reviews\n\nFor large-codebase style review, use up to 5 parallel sub-agents, one per independent concern (e.g. control flow, function design, variable declarations, string handling, code organization); merge findings.\n\n## Enforce with Linters\n\nLinters enforce many rules: `gofmt`, `gofumpt`, `goimports`, `gocritic`, `revive`, `wsl_v5`. See `samber\u002Fcc-skills-golang@golang-lint` skill.\n\n## Cross-References\n\n- `samber\u002Fcc-skills-golang@golang-naming` skill: identifier naming conventions\n- `samber\u002Fcc-skills-golang@golang-structs-interfaces` skill: pointer vs value receivers, interface design\n- `samber\u002Fcc-skills-golang@golang-design-patterns` skill: functional options, builders, constructors\n- `samber\u002Fcc-skills-golang@golang-continuous-integration` skill: automated AI-driven code review in CI using these guidelines\n- `samber\u002Fcc-skills-golang@golang-refactoring` skill: mechanically, safely applying guard-clause conversion, function extraction and options-struct migration across many call sites once review finds violations at scale\n","> **Community default.** Company skill explicitly superseding `samber\u002Fcc-skills-golang@golang-code-style` skill wins.\n\n# Go Code Style\n\nStyle rules needing human judgment. Linters handle formatting; this skill handles clarity.\n\n> \"Clear is better than clever.\" — Go Proverbs\n\nWhen ignoring a rule, add a code comment.\n\n## Line Length & Breaking\n\nNo rigid limit, but lines over ~120 characters MUST break, at **semantic boundaries**, not arbitrary columns. Calls with 4+ arguments SHOULD go one argument per line when otherwise long and repository already formats them so. If user explicitly asks for single-line code, comply:\n\n```go\n\u002F\u002F Good — each argument on its own line, closing paren separate\nmux.HandleFunc(\"\u002Fapi\u002Fusers\", func(w http.ResponseWriter, r *http.Request) {\n    handleUsers(\n        w,\n        r,\n        serviceName,\n        cfg,\n        logger,\n        authMiddleware,\n    )\n})\n```\n\nSignature too long: real fix often **fewer parameters** (options struct), not better wrapping. Multi-line signatures: one parameter per line.\n\n## Variable Declarations\n\nSHOULD use `:=` for non-zero values, `var` for zero-value initialization. Form signals intent: `var` means \"this starts at zero.\"\n\n```go\nvar count int              \u002F\u002F zero value, set later\nname := \"default\"          \u002F\u002F non-zero, := is appropriate\nvar buf bytes.Buffer       \u002F\u002F zero value is ready to use\n```\n\n### Slice & Map Initialization\n\nInitialize maps before writes; nil maps panic on write. Nil slice (`var s []T`) is idiomatic zero value; `len`, `append` and `range` work on it (Go Code Review Comments prefers it). Initialize slices explicitly (`[]T{}` or `make`) where difference is observable: JSON encoding (nil encodes as `null`, empty as `[]`), APIs whose callers distinguish nil from empty, or existing repository practice.\n\n```go\nvar users []User                        \u002F\u002F nil slice: fine for internal use\nusers := []User{}                       \u002F\u002F empty, encodes as [] in JSON\nm := map[string]int{}                   \u002F\u002F maps must be initialized before writes\nusers := make([]User, 0, len(ids))      \u002F\u002F preallocate when capacity is known\nm := make(map[string]int, len(items))   \u002F\u002F preallocate when size is known\n```\n\nDo not preallocate speculatively: `make([]T, 0, 1000)` wastes memory when common case is 10 items.\n\n### Composite Literals\n\nComposite literals MUST use field names — positional fields break when type adds or reorders fields:\n\n```go\nsrv := &http.Server{\n    Addr:         \":8080\",\n    ReadTimeout:  5 * time.Second,\n    WriteTimeout: 10 * time.Second,\n}\n```\n\n## Control Flow\n\n### Reduce Nesting\n\nMUST handle errors and edge cases first (early return). Happy path stays at minimal indentation:\n\n```go\nfunc process(data []byte) (*Result, error) {\n    if len(data) == 0 {\n        return nil, errors.New(\"empty data\")\n    }\n\n    parsed, err := parse(data)\n    if err != nil {\n        return nil, fmt.Errorf(\"parsing: %w\", err)\n    }\n\n    return transform(parsed), nil\n}\n```\n\n### Eliminate Unnecessary `else`\n\nIf `if` body ends with `return`\u002F`break`\u002F`continue`, MUST drop `else`. Simple assignments: default-then-override (assign default, override via independent conditions or `switch`):\n\n```go\n\u002F\u002F Good — default-then-override with switch (cleanest for mutually exclusive overrides)\nlevel := slog.LevelInfo\nswitch {\ncase debug:\n    level = slog.LevelDebug\ncase verbose:\n    level = slog.LevelWarn\n}\n\n\u002F\u002F Bad — else-if chain hides that there's a default\nif debug {\n    level = slog.LevelDebug\n} else if verbose {\n    level = slog.LevelWarn\n} else {\n    level = slog.LevelInfo\n}\n```\n\n### Complex Conditions & Init Scope\n\n`if` with 3+ operands: MUST extract named booleans. Wall of `||` is unreadable, hides business logic. Keep expensive checks inline (short-circuit). [Details](.\u002Freferences\u002Fdetails.md)\n\n```go\n\u002F\u002F Good — named booleans make intent clear\nisAdmin := user.Role == RoleAdmin\nisOwner := resource.OwnerID == user.ID\nisPublicVerified := resource.IsPublic && user.IsVerified\nif isAdmin || isOwner || isPublicVerified || permissions.Contains(PermOverride) {\n    allow()\n}\n```\n\nScope variables to `if` when only check needs them:\n\n```go\nif err := validate(input); err != nil {\n    return err\n}\n```\n\n### Switch Over If-Else Chains\n\nSame variable compared repeatedly: prefer `switch`:\n\n```go\nswitch status {\ncase StatusActive:\n    activate()\ncase StatusInactive:\n    deactivate()\ndefault:\n    panic(fmt.Sprintf(\"unexpected status: %d\", status))\n}\n```\n\n## Function Design\n\n- Functions SHOULD be **short and focused**: one function, one job.\n- Functions SHOULD have **≤4 parameters**; beyond that, options struct (see `samber\u002Fcc-skills-golang@golang-design-patterns` skill).\n- **Parameter order**: `context.Context` first, then inputs, then output destinations.\n- Naked returns help in very short functions (1-3 lines) with obvious return values. Longer functions: name returns explicitly, else readers scroll to find what's returned.\n\n```go\nfunc FetchUser(ctx context.Context, id string) (*User, error)\nfunc SendEmail(ctx context.Context, msg EmailMessage) error  \u002F\u002F grouped into struct\n```\n\n### Prefer `range` for Iteration\n\nSHOULD use `range` over index-based loops. `range n` (Go 1.22+) for simple counting.\n\n```go\nfor _, user := range users {\n    process(user)\n}\n```\n\n## Value vs Pointer Arguments\n\nPass small types (`string`, `int`, `bool`, `time.Time`) by value. Pointers for mutation, large structs (~128+ bytes), or meaningful nil. [Details](.\u002Freferences\u002Fdetails.md)\n\n## Code Organization Within Files\n\n- **Group related declarations**: type, constructor, methods together\n- **Order**: package doc, imports, constants, types, constructors, methods, helpers\n- **One primary type per file** when it has significant methods\n- **Blank imports** (`_ \"pkg\"`) register side effects (init functions). Restrict to `main` and test packages so side effects show at application root, not hidden in library code\n- **Dot imports** pollute namespace and hide where a name comes from — never use in library code\n- **Unexport aggressively** — can always export later; unexporting is a breaking change. Unexport safely with `samber\u002Fcc-skills-golang@golang-gopls` skill: its rename updates every call site atomically and refuses when lowercasing a method would break interface satisfaction, a breakage grep\u002Fsed silently ships.\n\n## String Handling\n\nUse `strconv` for simple conversions (faster), `fmt.Sprintf` for complex formatting. Use `%q` in error messages to show string boundaries. `strings.Builder` in loops, `+` for simple concatenation.\n\n## Type Conversions\n\nPrefer explicit, narrow conversions. Generics over `any` when concrete type will do:\n\n```go\nfunc Contains[T comparable](slice []T, target T) bool  \u002F\u002F not []any\n```\n\n## Philosophy\n\n- **\"A little copying is better than a little dependency\"**\n- **Use `slices` and `maps` standard packages**; for filter\u002Fgroup-by\u002Fchunk, use `github.com\u002Fsamber\u002Flo`\n- **\"Reflection is never clear\"** — avoid `reflect` unless necessary\n- **Don't abstract prematurely** — extract once pattern is stable\n- **Minimize public surface** — every exported name is a commitment\n\n## Parallelizing Code Style Reviews\n\nFor large-codebase style review, use up to 5 parallel sub-agents, one per independent concern (e.g. control flow, function design, variable declarations, string handling, code organization); merge findings.\n\n## Enforce with Linters\n\nLinters enforce many rules: `gofmt`, `gofumpt`, `goimports`, `gocritic`, `revive`, `wsl_v5`. See `samber\u002Fcc-skills-golang@golang-lint` skill.\n\n## Cross-References\n\n- `samber\u002Fcc-skills-golang@golang-naming` skill: identifier naming conventions\n- `samber\u002Fcc-skills-golang@golang-structs-interfaces` skill: pointer vs value receivers, interface design\n- `samber\u002Fcc-skills-golang@golang-design-patterns` skill: functional options, builders, constructors\n- `samber\u002Fcc-skills-golang@golang-continuous-integration` skill: automated AI-driven code review in CI using these guidelines\n- `samber\u002Fcc-skills-golang@golang-refactoring` skill: mechanically, safely applying guard-clause conversion, function extraction and options-struct migration across many call sites once review finds violations at scale\n",{"name":5,"paths":24,"license":15,"metadata":26,"description":7,"allowed-tools":36,"compatibility":37,"user-invocable":38},[25],"**\u002F*.go",{"author":27,"version":28,"openclaw":29},"samber","1.3.0",{"emoji":30,"install":31,"homepage":32,"requires":33},"🎨",[],"https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":34},[35],"go","Read Edit Write Glob Grep Bash(gofmt:*) Bash(go build:*) Bash(go vet:*) Bash(golangci-lint run:*) Bash(git status:*) Bash(git diff:*) Bash(git log:*) Bash(git show:*) Agent","Designed for Claude Code, Codex or similar harness, and for projects using Golang.",true,"main","101d0f67250256ca5d80dc3f95767cad7b541457","skills\u002Fgo\u002Fgolang-code-style","https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents","https:\u002F\u002Fgithub.com\u002Fw0rxbend","https:\u002F\u002Freadme.worxbend.com\u002F","Fluent in Backend-ese (microservices, distributed systems, you know the drill)\r\nFunctional Programming Fanatic...","2026-11-14 14:44:12",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":38},[49,52,55],{"tool":50,"command":51},"npx","npx skills add w0rxbend\u002Fdot-agents --skill golang-code-style",{"tool":53,"command":54},"bunx","bunx skills add w0rxbend\u002Fdot-agents --skill golang-code-style",{"tool":56,"command":57},"pnpm","pnpm dlx skills add w0rxbend\u002Fdot-agents --skill golang-code-style","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents\u002Fblob\u002Fmain\u002Fskills\u002Fgo\u002Fgolang-code-style\u002FSKILL.md",[60,66],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"evals\u002Fevals.json","REFERENCE","参考文档",35853,"https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents\u002Fblob\u002Fmain\u002Fskills\u002Fgo\u002Fgolang-code-style\u002Fevals\u002Fevals.json",{"path":67,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fdetails.md",2481,"https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents\u002Fblob\u002Fmain\u002Fskills\u002Fgo\u002Fgolang-code-style\u002Freferences\u002Fdetails.md",[71,78,85,93,100,107],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7E6TS1SW1ZSXN748N0RBGHT","wiki-builder","Create and maintain a local Markdown research wiki (sources with provenance, compiled concept\u002Fsource pages, index, maintenance log) driven by a per-wiki config. Use when the user wants to start a wiki or knowledge base, ingest sources into one, or query and update it; use wiki-page-writer for a single code deep-dive page.","https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fwiki-builder\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7E6S8ARS0VQR85H4FEC390B","refactoring-guru","Diagnose a named code smell and apply the smallest behavior-preserving refactoring, with verification before and after and an explicit stop condition. Use for structural refactors (extract, move, consolidate, change ownership), not for feature or bug work; for readability cleanup of recent changes use code-simplification.","https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Frefactoring-guru\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7E6RRXCYGSHA0ZBFX3YZP7Y","legacy-seams","When changing untested legacy code, pin the observed results with characterization tests and open the smallest seam that substitutes only the blocking dependency, separate from any later logic change. Use when a clock, random source, I\u002FO, global, or hidden constructor blocks a test or a safe edit. Use test-driven-development for a new behavior or a bug, refactoring-guru for one named structural refactor after the seam exists, and code-refactoring-tech-debt to choose which legacy to replace.","https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Flegacy-seams\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Flegacy-seams\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7E6QZ11XWSNHCBGYK8HH97C","idea-refine","Refine a raw idea into a one-page brief (problem statement, recommended direction, assumptions to validate, MVP scope, not-doing list) through divergent then convergent thinking. Use when an idea is still vague or you want options and a stress test before committing; use interview-me when the goal itself is unclear and spec-driven-development once the direction is chosen.","https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fidea-refine\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7E6N2N7BYW7BA5XGM0QD3B4","code-review-and-quality","Review rubric and approval standard for any change before merge, including code written by you, another agent, or a human: five axes (correctness, readability, architecture, security, performance), change sizing, structural remedies, severity labels, and feedback technique. Use to judge whether a change is fit to merge; use code-review to run a PR or diff review end to end.","https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fcode-review-and-quality\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":19},"01M7E6MNCZPTRD77Z419X755HQ","code-perfection","Smell and style gate for code you write or change. Bans known code smells (long method, large class, primitive obsession, long parameter list, data clumps, duplicate code, dead code, feature envy, shotgun surgery, flag arguments, message chains) and enforces behavior-preserving structure. On Scala files, enforces worxbend style. Use while implementing, reviewing a diff for smells, or when a smell or style violation is suspected. Routine construction stays with code-complete. SOLID and DRY stay with clean-code-guard. One named structural refactor stays with refactoring-guru.","https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fcode-perfection\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fw0rxbend\u002Fdot-agents\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow\u002Fcode-perfection\u002FSKILL.md",[],[]]