Error Handling (Unified Go & DB)
Expert-level review for error handling in Go services using GORM and PostgreSQL. Ensures errors are correctly identified, preserved via wrapping, mapped to domain errors, and retried where appropriate.
When to Apply
Use this skill when:
- Reviewing general Go error propagation and context usage
- Debugging database errors (e.g., duplicate keys, serialization failures)
- Auditing error wrapping with
%wvs%v - Ensuring correct use of
errors.Is/errors.As - Adding retry logic for serializable transactions or deadlocks
Rule Categories
| Priority | Count | Focus |
|---|---|---|
| CRITICAL | 6 | error chains, context leaks, PgError mapping, retries |
| HIGH | 6 | propagation, Is/As usage, RowsAffected, deadlock detection |
| MEDIUM | 2 | sentinel errors, structured logging |
Rules Covered (14 total)
Critical Issues (6)
critical-error-wrapping— Use%w, not%v, to preserve error chainscritical-context-leak— Alwaysdefer cancel()after context creationcritical-error-shadow— Don't shadowerrin nested scopescritical-errors-is-as— Useerrors.Is/Asfor DB and wrapped errorscritical-pg-error-mapping— Map Postgres codes to domain errors at repo boundarycritical-serialization-retry— Retry transactions on40001serialization failure
High-Impact Patterns (6)
high-context-propagation— Propagate context through the call chainhigh-error-is-as— Prescriptive rule for using Is/As over string matchinghigh-interface-nil— Check for nil in interfaces correctlyhigh-rows-affected— CheckRowsAffectedafter Update/Deletehigh-wrap-with-context— Wrap DB errors with operation contexthigh-deadlock-detection— Handle40P01deadlocks as retryable
Medium Improvements (2)
medium-sentinel-error-usage— Use sentinel errors for stable categoriesmedium-structured-logging— Log DB/Go errors with structured fields
Trigger Phrases
- "Review error handling"
- "Debug this DB error"
- "23505 / 40001 / 40P01"
- "Check for context leaks"
- "Review error chains"
- "Transaction retry"
- "ErrRecordNotFound"
Output Format
## Critical Issues Found: X
### [Rule ID] (Line Y)
**Issue**: Description
**Impact**: Context leak / Lost chain / Data inconsistency
**Fix**: Suggested code
**Example**:
```go
// Corrected code
## Related Skills
- [gorm-query-patterns](../gorm-query-patterns/SKILL.md) — For `.Error` check safety
- [concurrency-safety](../concurrency-safety/SKILL.md) — For context timeout patterns
---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/saifoelloh) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->