agentleFS
Sign inStart free
jkeddarijkeddari/go-skills/skills/golang-concurrency/SKILL.md

golang-concurrency

Skill1 starsChanged 4 months agoMITView on GitHub

Golang concurrency and context guidance covering goroutine lifecycle, channels, mutexes, atomics, worker pools, cancellation, deadlines, request-scoped values, synchronization, races, deadlocks, and leak prevention. Use when writing, reviewing, testing, or debugging concurrent Go code or context propagation.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Test shutdown and error paths, then run focused tests with -race.

    line 29
  2. Distinctive:

    Never start a goroutine without defining how it stops.

    line 33
  3. Distinctive:

    Do not store request contexts for later reuse.

    line 35
  4. Distinctive:

    Do not use context values for optional function parameters or mutable business state.

    line 36
  5. Distinctive:

    Avoid copying values containing mutexes or atomics after first use.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Persona: You are a Go concurrency reviewer. Make ownership, termination, cancellation, and synchronization explicit before optimizing throughput.

Go Concurrency

Workflow

  1. Identify every goroutine owner, input, output, shared resource, and termination condition.
  2. Choose synchronization from the invariant: channels transfer ownership, mutexes protect shared state, atomics handle narrow lock-free state.
  3. Propagate context across blocking boundaries and honor cancellation in loops and retries.
  4. Bound fan-out, queues, retries, and external calls.
  5. Test shutdown and error paths, then run focused tests with -race.

Hard rules

  • Never start a goroutine without defining how it stops.
  • Let senders close channels; do not close channels merely to signal receivers unless ownership is clear.
  • Do not store request contexts for later reuse.
  • Do not use context values for optional function parameters or mutable business state.
  • Avoid copying values containing mutexes or atomics after first use.

Conditional references

  • Channels and select: channels-and-select.md
  • Mutexes, atomics, once, pools, and wait groups: sync-primitives.md
  • Worker pools and pipelines: pipelines.md
  • Cancellation and deadlines: context-cancellation.md
  • Context values and tracing: context-values-tracing.md
  • HTTP and service boundaries: context-http-services.md

→ See golang-troubleshooting for deadlocks and leaks, golang-testing for deterministic tests, and golang-performance for contention measurement.

Download now (ZIP)

  • Other versions15 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 15

    1. samber/cc-skills-golang★ 3.6ksame name
    2. unxed/f4★ 247same name
    3. klawisha012/agentsync★ 18same name
    4. alexastrum/skl★ 11same name
    5. tstapler/dotfiles★ 8same name
    6. poizoncoded/skills★ 2same name
    7. tquangkhai98/browser-profiles-manager★ 2same name
    8. rockcookies/skills★ 1same name
    9. VerifiedOrganic/onboard★ 1same name
    10. gccli/skills★ 0same name

    5 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use golang-samber-lo, golang-samber-ro and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • guynhsichngeodiecSkill

      golang-samber-lo

      Functional programming helpers for Golang using samber/lo — 500+ type-safe generic functions for slices, maps, channels, strings, math, tuples, and concurrency (Map, Filter, Reduce, GroupBy, Chunk, Flatten, Find, Uniq, etc.). Core immutable package (lo), concurrent variants (lo/parallel aka lop), in-place mutations (lo/mutable aka lom), lazy iterators (lo/it aka loi for Go 1.23+), and experimental SIMD (lo/exp/simd). Apply when using or adopting samber/lo, when the codebase imports github.com/samber/lo, or when implementing functional-style data transformations in Go. Not for streaming pipelines (→ See golang-samber-ro skill).

      Also in 10 projects that use this

    • guynhsichngeodiecSkill

      golang-samber-ro

      Reactive streams and event-driven programming in Golang using samber/ro — ReactiveX implementation with 150+ type-safe operators, cold/hot observables, 5 subject types (Publish, Behavior, Replay, Async, Unicast), declarative pipelines via Pipe, 40+ plugins (HTTP, cron, fsnotify, JSON, logging), automatic backpressure, error propagation, and Go context integration. Apply when using or adopting samber/ro, when the codebase imports github.com/samber/ro, or when building asynchronous event-driven pipelines, real-time data processing, streams, or reactive architectures in Go. Not for finite slice transforms (-> See golang-samber-lo skill).

      Also in 8 projects that use this

    • alexastrumSkill

      golang-swagger

      Golang OpenAPI/Swagger documentation with swaggo/swag — annotation comments (@Summary, @Param, @Success, @Router, @Security), swag init code generation, framework integrations (gin, echo, fiber, chi, net/http), security definitions (Bearer/JWT, OAuth2, API key), and struct tags (swaggertype, enums, example, swaggerignore). Apply when adding or maintaining Swagger/OpenAPI docs in a Go project, or when the codebase imports github.com/swaggo/swag, github.com/swaggo/gin-swagger, github.com/swaggo/echo-swagger, github.com/swaggo/http-swagger, or github.com/swaggo/files.

      Also in 7 projects that use this

    • +9 more from guynhsichngeodiec
  • In this repository14 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free