Enforce CRUD repository patterns with tenant scoping and pagination in Go.
npx skills add https://github.com/ArtisanCloud/PowerX --skill crud-repository
Please help me install this Agent Skill. Skill: crud-repository Source: https://github.com/ArtisanCloud/PowerX/tree/main/.codex/skills/crud/repository Command: npx skills add https://github.com/ArtisanCloud/PowerX --skill crud-repository
Enforces consistent repository patterns to prevent scattered, insecure, or inconsistent data access implementations by establishing BaseRepository conventions, tenant scoping, pagination, and unified error semantics so services remain testable and transaction-safe.
Validate the repository files under internal/repository and pkg/corex/db/persistence/repository against the crud_repository rules and report any violations.
High-intent search queries and answers about installing and using this skill.
To enforce multi-tenant CRUD repository patterns in Go, you can apply standardized linting rules that validate method signatures and ensure tenant_id is present in all queries. This prevents scattered, insecure data access by establishing consistent BaseRepository conventions.
The best way to standardize soft deletes and pagination across GORM repositories is to use declarative rules and ready-to-use templates. This enforces predictable behavior and ensures list endpoints consistently support paging through dedicated Paginate helpers.
To migrate ad-hoc Go data access code into a BaseRepository pattern, apply interface and implementation templates that validate method signatures include context.Context and *gorm.DB. This ensures transaction propagation and unified error semantics for testable services.
This repository validation approach requires Go code structured under internal/repository and pkg/corex/db/persistence/repository. It specifically validates GORM usage by checking that method signatures include *gorm.DB and context.Context to ensure proper transaction support.
To map repository errors to HTTP semantics in a service-repo layer, establish unified error semantics during CRUD operations. This allows services to translate predictable repository errors into appropriate HTTP responses while maintaining transaction safety.
liuridaRetrieve the underlying *sql.DB* object from a GORM *gorm.DB* instance.
OlegHQWrap Go errors with contextual paths across repository, service, and handler layers.
liuridaEncapsulate GORM query logic into reusable scope functions.
greyhaven-aiEnforce Grey Haven database conventions across multi-tenant schemas.
