Pass contextual values into GORM hooks and migration statements.
npx skills add https://github.com/liurida/gorm-development-skill --skill gorm-settings
Please help me install this Agent Skill. Skill: gorm-settings Source: https://github.com/liurida/gorm-development-skill/tree/main/settings Command: npx skills add https://github.com/liurida/gorm-development-skill --skill gorm-settings
Provides a scoped, operation-level mechanism to pass metadata such as audit user IDs, tenant identifiers, or migration options into GORM operations and hooks so you do not rely on global state or ad-hoc context passing.
Set an audit_user using db.Set before creating a model so the BeforeCreate hook can read and record the audit_user.
High-intent search queries and answers about installing and using this skill.
To pass context data into GORM hooks for audit trails, use the Set method to propagate values like user IDs into all operations, including nested association hooks. This enables per-operation metadata without relying on global state.
Set propagates contextual values into all hooks including nested associations, while InstanceSet applies statement-scoped values that do not propagate to association hooks, making it useful for temporary per-model transformations.
To configure table options for GORM migrations across nested associations, set the gorm:table_options key with your desired string values. This allows you to specify database engines or table comments for MySQL and MariaDB.
Yes, you can achieve tenant isolation in GORM without global state by using Set to pass tenant identifiers into your operations. The values propagate through hooks, allowing you to enforce tenant boundaries on a per-operation basis.
Yes, this GORM settings approach works for skipping or toggling hook logic. By passing conditional flags via Set or InstanceSet, your hooks can read these values and dynamically alter their execution behavior per statement.
Use statement-scoped values via InstanceGet when you need temporary data for per-model transformations without affecting nested association hooks. Use propagated values via Get when metadata must cascade across all related operations.
liuridaDeclare GORM models with gorm.Model embedding and field tags.
liuridaIntercept GORM model lifecycle hooks to apply validation and transactional side effects.
liuridaGenerate GORM model definitions and perform CRUD operations in Go applications.
mgreenlyInject dependencies explicitly into C modules at startup.
