Use `db.QueryContext()` in a Go repository. Why: - It accepts `context.Context`, so request deadlines, cancellation, and tracing propagate into the DB call. - It prevents queries from ignoring timeout/cancel signals. - It matches good repository design where every query path is context-aware. Typical pattern: ```go rows, err := db.QueryContext(ctx, query, args...) if err != nil { return nil, err } defer rows.Close() ``` Also check `rows.Err()` after iteration. Use plain `db.Query()` only if y...
Scanned 9/5/2026
Install to Claude Code
npx -y skills add HoangNguyen0403/agent-skills-standard --skill golang-database --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Golang Database?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-golang-database-0c94db6d)More formats (shields.io, HTML) on the badges page.
Use `db.QueryContext()` in a Go repository.
Why:
- It accepts `context.Context`, so request deadlines, cancellation, and tracing propagate into the DB call.
- It prevents queries from ignoring timeout/cancel signals.
- It matches good repository design where every query path is context-aware.
Typical pattern:
```go
rows, err := db.QueryContext(ctx, query, args...)
if err != nil {
return nil, err
}
defer rows.Close()
```
Also check `rows.Err()` after iteration.
Use plain `db.Query()` only if you truly have no context to propagate, which is usually not what you want in application code.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.