agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/golang/SKILL.md

golang

Skill4 starsChanged 11 days agoMITView on GitHub

Apply evidence-backed Go rules for bounds, APIs, errors, concurrency, Temporal, tests, rollout, and controllers. Use when changing Go services, handlers, workflows, or tests.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use clean-code.

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.
  • xenitV1Skill

    clean-code

    Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Use optional only for semantic presence.

    line 16
  2. Very specific:

    Prefer positive config booleans, except negative disabled when the zero value must fail closed.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 12 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

This core routes to domain guidance; /golang-review owns the aggregate rule catalog. /aip owns resource design; this skill owns Go implementation.

Non-negotiables

  • Bound tenant-controlled memory, cardinality, fan-out, concurrency, and response size.
  • Traverse protos with generated getters: a.GetB().GetC().
  • Proto annotations own field contracts; do not duplicate handler validation.
  • Use optional only for semantic presence; update intent belongs in masks.
  • Collections are paginated, filterable List; Get returns one resource.
  • At API boundaries, log internal causes and return structured Connect/gRPC errors with stable reasons and public paths. Preserve upstream per-item granularity.
  • Security fails closed; secrets are references, never plaintext input, storage, output, or logs.
  • Bound retry/backoff inside the owning timeout.
  • Reuse semantic config types, not strings or bool sets.
  • Feature-flag risky mixed-version rollout and remove flags after convergence.
  • Bootstrap files wire; packages own behavior.
  • Integration tests cross real boundaries; tests assert stable behavior, not paths or incidental text.

Contextual tensions

  • Prefer positive config booleans, except negative disabled when the zero value must fail closed.
  • Exhaustive enum switches reject unknowns; intentional subsets document ignored values.
  • gRPC keepalive depends on every intermediary.
  • New AIP surfaces use bounded filter strings; preserve established typed filters for compatibility.
  • Fakes suit unit tests, never claims of protocol, role, provider, or container compatibility.

Load by task

WorkRead
Protos, handlers, Connect/gRPC, public errorsPROTO-API.md
Goroutines, caches, shutdown, shared stateCONCURRENCY.md
Errors, logging, metricsERRORS.md
Tests and CITESTING.md
TemporalTEMPORAL.md
Tenant input, egress, authz, secrets, destructive opsSECURITY.md
Flags, deprecation, schema removalROLLOUT.md
Packages, storage, interfacesSTRUCTURE.md
Operators and reconcilersCONTROLLERS.md
Go 1.27 APIs and leak profilesGO-1.27.md

Hooks warn on unreserved shipped proto removals and floating test images. Review diffs with /golang-review.

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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