Golang Database Patterns
CheckedHelps with Go, database, patterns as part of developing backend services and APIs workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add bobmatnyc/claude-mpm-skills --skill golang-database-patterns -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
bobmatnyc
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned bobmatnyc/claude-mpm-skills at 718070a7d6.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 718070a7d6
- Scanned
- 2 files, 1,249 lines
About this skill
What it does
This skill provides guidance and support for developing backend services and APIs using Go and interacting with SQL databases. It covers various database integration techniques, from the standard database/sql package to specialized libraries like sqlx and pgx, along with patterns such as the Repository Pattern and schema migrations. The goal is to help developers build robust, performant, and testable data access layers.
When to use it
This skill is helpful when:
- Building CRUD (Create, Read, Update, Delete) operations with type safety in Go.
- Implementing data access layers for web services.
- Managing database schema evolution across different environments.
- Optimizing database connection pooling for production deployments.
- Testing database code using mock repositories.
- Migrating from ORMs (Object-Relational Mappers) to a more SQL-first approach.
Key capabilities
database/sql: The standard Go interface for interacting with any SQL database.sqlx: Provides convenience methods like struct scanning and named queries, reducing boilerplate code.pgx: A PostgreSQL-native driver optimized for maximum performance.- Repository Pattern: Enables testability through interface-based data access.
- Migrations: Manages database schema versioning using
golang-migrate. - Connection Pooling: Provides production-ready connection management to improve efficiency and resource utilization.
- Transaction Safety: Handles transactions in a context-aware manner.
Example prompts
- "Show me an example of how to use the Repository Pattern with Go and database/sql."
- "What are the benefits of using pgx over lib/pq for PostgreSQL?"
- "How do I configure connection pooling when using database/sql?"
Tips & gotchas
- Consider your specific database needs when choosing between
database/sql,sqlx, andpgx.pgxis only suitable for PostgreSQL. - For maximum performance with PostgreSQL,
pgxcan be significantly faster (30-50%) than the standardlib/pqdriver. - Familiarize yourself with connection pooling settings (
SetMaxOpenConns,SetMaxIdleConns, etc.) to optimize resource usage in production environments.