golang-stay-updated

Provides resources to stay updated with Golang news, communities and people to follow. Use when seeking Go learning resources, discovering new libraries, finding community channels, or keeping up with Go language changes and releases.

npx skills add https://github.com/samber/cc-skills-golang --skill golang-stay-updated

Stay Updated with Go

A curated guide to keeping your finger on the pulse of the Go ecosystem.

Official Go Resources

ResourceURL
go.devOfficial Go website with tutorials and tools
pkg.go.devDiscover Go packages and documentation
tour.golang.orgInteractive Go tutorial
play.golang.orgGo playground for testing code
go.dev/blogOfficial Go blog

Newsletters

NewsletterDescriptionSubscribe
Golang WeeklyWeekly curated Go content, news, and articleshttps://golangweekly.com/
Awesome Go NewsletterUpdates on new Go libraries and toolshttps://go.libhunt.com/

Reddit & Communities

CommunityDescriptionURL
r/golangMain Go subreddit with 300K+ membershttps://www.reddit.com/r/golang
golang wikiOfficial wiki with resources and FAQshttps://go.dev/wiki/
gophers.slack.comOfficial Go Slack communityhttps://invite.slack.golangbridge.org
Go ForumOfficial Go discussion forumhttps://forum.golangbridge.org
Discuss GoOfficial Go team discussionhttps://groups.google.com/g/golang-nuts

Famous Go Developers

Follow these influential Go developers and contributors:

Core Go Team

NameGitHubTwitter/XLinkedInBluesky
Rob Pikerobpike
Ken Thompsonken
Russ Coxrsc@_rschttps://www.linkedin.com/in/swtchhttps://bsky.app/profile/swtch.com
Brad Fitzpatrickbradfitz@bradfitzhttps://www.linkedin.com/in/bradfitz/https://bsky.app/profile/bradfitz.com
Andrew Gerrandadg
Robert Griesemergriesemer
Dmitry Vyukovdvyukov@dvyukov

Go Tooling & Infrastructure

NameGitHubTwitter/XLinkedInBluesky
Sam Boyersdboyer@sdboyer
Daniel Theophaneskardianos@kardianos
Matt Butchertechnosophos
Jaana Doganrakyll@rakyllhttps://www.linkedin.com/in/rakyll/

Popular Go Authors & Educators

NameGitHubTwitter/XLinkedInBluesky
Mat Ryermatryer@matryerhttps://linkedin.com/in/matryer
Dave Cheneydavecheney@davecheneyhttps://linkedin.com/in/davecheney
Katherine Cox-Budaykat-cohttps://linkedin.com/in/katherinecoxbuday
Johnny Boursiquotjboursiquot@jboursiquothttps://linkedin.com/in/jboursiquot
Michał Łowickimlowicki@mlowickihttps://linkedin.com/in/michał-łowicki-a60402b

Library & Framework Authors

NameGitHubTwitter/XLinkedInBluesky
Steve Franciaspf13@spf13https://linkedin.com/in/spf13
Samuel Berthesamber@samuelberthehttps://linkedin.com/in/samuelberthehttps://bsky.app/profile/samber.bsky.social
Mitchell Hashimotomitchellh@mitchellhhttps://linkedin.com/in/mitchellhhttps://bsky.app/profile/mitchellh.com
Matt Holtmholt@mholt6
Tomás Senarttsenart@tsenarthttps://www.linkedin.com/in/tsenart/
Björn Rabensteinbeorn7

Conference Speakers & Community Leaders

NameGitHubTwitter/XLinkedInBluesky
Carlisia Camposcarlisia@carlisiahttps://linkedin.com/in/carlisia
Erik St. Martinerikstmartin@erikstmartin
Brian Ketelsenbketelsen@brian.dev

Must-Follow Blogs

BlogAuthorURL
The Go BlogGo Teamhttps://go.dev/blog
Rob Pike's BlogRob Pikehttps://commandcenter.blogspot.com
Dave CheneyDave Cheneyhttps://dave.cheney.net
Ardan Labs BlogBill Kennedyhttps://www.ardanlabs.com/blog

YouTube Channels

ChannelContentURL
GoOfficial Go teamhttps://www.youtube.com/@golang
Gopher AcademyTalks & tutorialshttps://www.youtube.com/@GopherAcademy
GopherCon EuropeEuropean conference talkshttps://www.youtube.com/@GopherConEurope
GopherCon UKUK conference talkshttps://www.youtube.com/@GopherConUK
Golang SingaporeSingapore meetup & conf talkshttps://www.youtube.com/@golangSG
Ardan LabsGo training & tipshttps://www.youtube.com/@ArdanLabs
Applied GoGo tutorialshttps://youtube.com/appliedgocode
Learn Go ProgrammingBeginner tutorialshttps://youtube.com/learn_goprogramming

Quick Tips for Staying Updated

  1. Subscribe to 1-2 newsletters - Don't overload yourself
  2. Follow 10-20 key people on X/Bluesky who post regularly
  3. Check Go.dev/blog weekly for official announcements
  4. Join Go Slack for real-time discussions
  5. Bookmark pkg.go.dev to discover new libraries
  6. Attend a GopherCon (virtual or in-person) yearly

Note: This guide is regularly updated. Suggest additions via GitHub issues.

More skills from samber

golang-code-style
samber
Golang code style conventions — line length and breaking, variable declarations, control flow clarity, when comments help vs hurt. Use when writing or reviewing Go code, asking about style or clarity, or establishing project coding standards. Not for naming conventions (→ See `samber/cc-skills-golang@golang-naming` skill), linter configuration (→ See `samber/cc-skills-golang@golang-lint` skill), or doc comments (→ See `samber/cc-skills-golang@golang-documentation` skill).
developmentcode-review
golang-testing
samber
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky/slow tests. For testify-specific APIs see `samber/cc-skills-golang@golang-stretchr-testify`; for measurement methodology see...
developmenttestingcode-review
golang-design-patterns
samber
Idiomatic Golang design patterns — functional options, constructors, error flow and cascading, resource management and lifecycle, graceful shutdown, resilience, architecture, dependency injection, data handling, streaming, and more. Apply when explicitly choosing between architectural patterns, implementing functional options, designing constructor APIs, setting up graceful shutdown, applying resilience patterns, or asking which idiomatic Go pattern fits a specific problem.
developmentdesigncode-review
golang-error-handling
samber
Idiomatic Golang error handling — creation, wrapping with %w, errors.Is/As, errors.Join, custom error types, sentinel errors, panic/recover, the single handling rule, structured logging with slog, HTTP request logging middleware, and samber/oops for production errors. Built to make logs usable at scale with log aggregation 3rd-party tools. Apply when creating, wrapping, inspecting, or logging errors in Go code. For samber/oops specifics → See `samber/cc-skills-golang@golang-samber-oops`...
developmentcode-review
golang-performance
samber
Golang performance optimization patterns and methodology - if X bottleneck, then apply Y. Covers allocation reduction, CPU efficiency, memory layout, GC tuning, pooling, caching, and hot-path optimization. Use when profiling or benchmarks have identified a bottleneck and you need the right optimization pattern to fix it. Also use when performing performance code review to suggest improvements or benchmarks that could help identify quick performance gains. Not for measurement methodology (→...
developmentcode-review
golang-security
samber
Security best practices and vulnerability prevention for Golang. Covers injection (SQL, command, XSS), cryptography, filesystem safety, network security, cookies, secrets management, memory safety, and logging. Apply when writing, reviewing, or auditing Go code for security, or when working on any risky code involving crypto, I/O, secrets management, user input handling, or authentication. Includes configuration of security tools.
securitycode-reviewdevelopment
golang-database
samber
Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling. Use when writing, reviewing, or debugging Golang code that interacts with PostgreSQL, MariaDB, MySQL, or SQLite; for database testing; or for questions about database/sql, sqlx, or pgx. Does NOT generate database schemas or migration SQL.
developmentdatabase
golang-lint
samber
Linting best practices and golangci-lint configuration for Golang projects — running linters, configuring .golangci.yml, suppressing warnings with nolint directives, interpreting lint output, and selecting linters. Use when configuring golangci-lint, asking about lint warnings or nolint suppressions, setting up code quality tooling, or choosing linters. Also use when the user mentions golangci-lint, go vet, staticcheck, or revive.
developmentcode-reviewtesting