
Use Modern Go
- 713 installs
- 802 repo stars
- Updated July 30, 2026
- jetbrains/go-modern-guidelines
The use-modern-go skill encodes JetBrains Go modern guidelines for writing idiomatic Go in agent-assisted development.
About
The use-modern-go skill encodes JetBrains Go modern guidelines for writing idiomatic Go in agent-assisted development. Covers module layout, error wrapping with fmt.Errorf %w, context propagation, table-driven tests, generics usage where appropriate, and avoiding deprecated patterns flagged by modern linters. Agents audit existing packages against guideline checklists before refactors and prefer stdlib solutions over unnecessary dependencies. Use when upgrading legacy Go codebases or onboarding agents to team Go style standards.
- Idiomatic modules, errors, and context patterns.
- Table-driven tests and modern generics guidance.
- Linter-aligned avoidance of deprecated APIs.
- Stdlib-first dependency discipline.
- Checklist-driven package audits before refactors.
Use Modern Go by the numbers
- 713 all-time installs (skills.sh)
- +37 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #21 of 98 Go skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
use-modern-go capabilities & compatibility
- Capabilities
- idiomatic modules, errors, and context patterns. · table driven tests and modern generics guidance. · linter aligned avoidance of deprecated apis. · stdlib first dependency discipline.
- Use cases
- code review
npx skills add https://github.com/jetbrains/go-modern-guidelines --skill use-modern-goAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 713 |
|---|---|
| repo stars | ★ 802 |
| Last updated | July 30, 2026 |
| Repository | jetbrains/go-modern-guidelines ↗ |
How do I apply use-modern-go using the workflow in its SKILL.md?
Apply JetBrains Go modern guidelines for idiomatic modules, errors, testing, and concurrency patterns.
Who is it for?
Developers following the use-modern-go skill for the tasks it documents.
Skip if: Tasks outside the use-modern-go scope described in SKILL.md.
When should I use this skill?
User mentions use-modern-go or related triggers from the skill description.
What you get
Working use-modern-go setup aligned with the documented patterns and constraints.
- Version-aware Go source files
- Modernized refactors aligned to detected Go release
By the numbers
- Reads Go version from go.mod via a bundled grep-based detection command
Files
Modern Go Guidelines
Detected Go Version
!grep -rh "^go " --include="go.mod" . 2>/dev/null | cut -d' ' -f2 | sort | uniq -c | sort -nr | head -1 | xargs | cut -d' ' -f2 | grep . || echo unknown
How to Use This Skill
DO NOT search for go.mod files or try to detect the version yourself. Use ONLY the version shown above.
If version detected (not "unknown"):
- Say: "This project is using Go X.XX, so I’ll stick to modern Go best practices and freely use language features up to and including this version. If you’d prefer a different target version, just let me know."
- Do NOT list features, do NOT ask for confirmation
If version is "unknown":
- Say: "Could not detect Go version in this repository"
- Use AskUserQuestion: "Which Go version should I target?" → [1.23] / [1.24] / [1.25] / [1.26]
When writing Go code, use ALL features from this document up to the target version:
- Prefer modern built-ins and packages (
slices,maps,cmp) over legacy patterns - Never use features from newer Go versions than the target
- Never use outdated patterns when a modern alternative is available
---
Features by Go Version
Go 1.0+
time.Since:time.Since(start)instead oftime.Now().Sub(start)
Go 1.8+
time.Until:time.Until(deadline)instead ofdeadline.Sub(time.Now())
Go 1.13+
errors.Is:errors.Is(err, target)instead oferr == target(works with wrapped errors)
Go 1.18+
any: Useanyinstead ofinterface{}bytes.Cut:before, after, found := bytes.Cut(b, sep)instead of Index+slicestrings.Cut:before, after, found := strings.Cut(s, sep)
Go 1.19+
fmt.Appendf:buf = fmt.Appendf(buf, "x=%d", x)instead of[]byte(fmt.Sprintf(...))atomic.Bool/atomic.Int64/atomic.Pointer[T]: Type-safe atomics instead ofatomic.StoreInt32
var flag atomic.Bool
flag.Store(true)
if flag.Load() { ... }
var ptr atomic.Pointer[Config]
ptr.Store(cfg)Go 1.20+
strings.Clone:strings.Clone(s)to copy string without sharing memorybytes.Clone:bytes.Clone(b)to copy byte slicestrings.CutPrefix/CutSuffix:if rest, ok := strings.CutPrefix(s, "pre:"); ok { ... }errors.Join:errors.Join(err1, err2)to combine multiple errorscontext.WithCancelCause:ctx, cancel := context.WithCancelCause(parent)thencancel(err)context.Cause:context.Cause(ctx)to get the error that caused cancellation
Go 1.21+
Built-ins:
min/max:max(a, b)instead of if/else comparisonsclear:clear(m)to delete all map entries,clear(s)to zero slice elements
slices package:
slices.Contains:slices.Contains(items, x)instead of manual loopsslices.Index:slices.Index(items, x)returns index (-1 if not found)slices.IndexFunc:slices.IndexFunc(items, func(item T) bool { return item.ID == id })slices.SortFunc:slices.SortFunc(items, func(a, b T) int { return cmp.Compare(a.X, b.X) })slices.Sort:slices.Sort(items)for ordered typesslices.Max/slices.Min:slices.Max(items)instead of manual loopslices.Reverse:slices.Reverse(items)instead of manual swap loopslices.Compact:slices.Compact(items)removes consecutive duplicates in-placeslices.Clip:slices.Clip(s)removes unused capacityslices.Clone:slices.Clone(s)creates a copy
maps package:
maps.Clone:maps.Clone(m)instead of manual map iterationmaps.Copy:maps.Copy(dst, src)copies entries from src to dstmaps.DeleteFunc:maps.DeleteFunc(m, func(k K, v V) bool { return condition })
sync package:
sync.OnceFunc:f := sync.OnceFunc(func() { ... })instead ofsync.Once+ wrappersync.OnceValue:getter := sync.OnceValue(func() T { return computeValue() })
context package:
context.AfterFunc:stop := context.AfterFunc(ctx, cleanup)runs cleanup on cancellationcontext.WithTimeoutCause:ctx, cancel := context.WithTimeoutCause(parent, d, err)context.WithDeadlineCause: Similar with deadline instead of duration
Go 1.22+
Loops:
for i := range n:for i := range len(items)instead offor i := 0; i < len(items); i++- Loop variables are now safe to capture in goroutines (each iteration has its own copy)
cmp package:
cmp.Or:cmp.Or(flag, env, config, "default")returns first non-zero value
// Instead of:
name := os.Getenv("NAME")
if name == "" {
name = "default"
}
// Use:
name := cmp.Or(os.Getenv("NAME"), "default")reflect package:
reflect.TypeFor:reflect.TypeFor[T]()instead ofreflect.TypeOf((*T)(nil)).Elem()
net/http:
- Enhanced
http.ServeMuxpatterns:mux.HandleFunc("GET /api/{id}", handler)with method and path params r.PathValue("id")to get path parameters
Go 1.23+
maps.Keys(m)/maps.Values(m)return iteratorsslices.Collect(iter)not manual loop to build slice from iteratorslices.Sorted(iter)to collect and sort in one step
keys := slices.Collect(maps.Keys(m)) // not: for k := range m { keys = append(keys, k) }
sortedKeys := slices.Sorted(maps.Keys(m)) // collect + sort
for k := range maps.Keys(m) { process(k) } // iterate directlytime package
time.Tick: Usetime.Tickfreely — as of Go 1.23, the garbage collector can recover unreferenced tickers, even if they haven't been stopped. The Stop method is no longer necessary to help the garbage collector. There is no longer any reason to prefer NewTicker when Tick will do.
Go 1.24+
t.Context()notcontext.WithCancel(context.Background())in tests.
ALWAYS use t.Context() when a test function needs a context.
Before:
func TestFoo(t *testing.T) {
ctx, cancel := context.WithCancel(context.Background())
defer cancel()
result := doSomething(ctx)
}After:
func TestFoo(t *testing.T) {
ctx := t.Context()
result := doSomething(ctx)
}omitzeronotomitemptyin JSON struct tags.
ALWAYS use omitzero for time.Duration, time.Time, structs, slices, maps.
Before:
type Config struct {
Timeout time.Duration `json:"timeout,omitempty"` // doesn't work for Duration!
}After:
type Config struct {
Timeout time.Duration `json:"timeout,omitzero"`
}b.Loop()notfor i := 0; i < b.N; i++in benchmarks.
ALWAYS use b.Loop() for the main loop in benchmark functions.
Before:
func BenchmarkFoo(b *testing.B) {
for i := 0; i < b.N; i++ {
doWork()
}
}After:
func BenchmarkFoo(b *testing.B) {
for b.Loop() {
doWork()
}
}strings.SplitSeqnotstrings.Splitwhen iterating.
ALWAYS use SplitSeq/FieldsSeq when iterating over split results in a for-range loop.
Before:
for _, part := range strings.Split(s, ",") {
process(part)
}After:
for part := range strings.SplitSeq(s, ",") {
process(part)
}Also: strings.FieldsSeq, bytes.SplitSeq, bytes.FieldsSeq.
Go 1.25+
wg.Go(fn)notwg.Add(1)+go func() { defer wg.Done(); ... }().
ALWAYS use wg.Go() when spawning goroutines with sync.WaitGroup.
Before:
var wg sync.WaitGroup
for _, item := range items {
wg.Add(1)
go func() {
defer wg.Done()
process(item)
}()
}
wg.Wait()After:
var wg sync.WaitGroup
for _, item := range items {
wg.Go(func() {
process(item)
})
}
wg.Wait()Go 1.26+
new(val)notx := val; &x— returns pointer to any value.
Go 1.26 extends new() to accept expressions, not just types. Type is inferred: new(0) → int, new("s") → string, new(T{}) → *T. DO NOT use x := val; &x pattern — always use new(val) directly. DO NOT use redundant casts like new(int(0)) — just write new(0). Common use case: struct fields with pointer types.
Before:
timeout := 30
debug := true
cfg := Config{
Timeout: &timeout,
Debug: &debug,
}After:
cfg := Config{
Timeout: new(30), // *int
Debug: new(true), // *bool
}errors.AsType[T](err)noterrors.As(err, &target).
ALWAYS use errors.AsType when checking if error matches a specific type.
Before:
var pathErr *os.PathError
if errors.As(err, &pathErr) {
handle(pathErr)
}After:
if pathErr, ok := errors.AsType[*os.PathError](err); ok {
handle(pathErr)
}Related skills
How it compares
Choose use-modern-go over generic Go style guides when you need version-locked idioms tied to the repository's actual go.mod directive.
FAQ
What does use-modern-go do?
Apply JetBrains Go modern guidelines for idiomatic modules, errors, testing, and concurrency patterns.
When should I use use-modern-go?
Invoke when Apply JetBrains Go modern guidelines for idiomatic modules, errors, testing, and concurrency patterns.
Is use-modern-go safe to install?
Review the Security Audits panel on this page before installing in production.