update-openmls
Update openmls native library version. Use when checking for updates, upgrading openmls, bumping version, or updating native dependencies.
Update openmls native library version. Use when checking for updates, upgrading openmls, bumping version, or updating native dependencies.
Add a new database migration to EncryptedDb. Use when changing storage schema, data format, or serialization in the native library.
Use when working with JPA/Hibernate entities, repositories, or database operations to avoid N+1 queries, manage lazy loading, transactions, and entity relationships.
Use when investigating slow queries, analyzing execution plans, or optimizing database performance. Invoke for index design, query rewrites, configuration tuning, partitioning strategies, lock contention resolution. Українською: Оптимізуй базу, повільний запит, план виконання, індекси, N+1, кешування запитів, профілювання, блокування, партиціювання, перепиши запит, аналіз продуктивності.
Safely handle Prisma migration drift on existing databases without data loss. Use when: (1) "prisma migrate dev" shows "Drift detected: Your database schema is not in sync", (2) Prisma asks "We need to reset the schema. All data will be lost. Do you want to continue?", (3) Database was created via Supabase, direct SQL, or another ORM before adopting Prisma, (4) Adding schema changes to a production database that wasn't initialized with Prisma migrations. Covers baselining existing databases and applying incremental changes safely.
ALWAYS trigger for ANY task involving Supabase, Supabase Auth, Supabase Database, Supabase Storage, Supabase Edge Functions, Supabase Realtime, Row Level Security (RLS), PostgreSQL policies, Supabase CLI, self-hosted Supabase, database migrations, or Firebase-to-Supabase migration. This includes schema design, RLS policies, Edge Functions (Deno), auth flows, file uploads, and realtime subscriptions.
Use when continuing the active migration or rewrite after `docs/progress/MASTER.md` already exists and execution should resume from the current phase instead of recreating the planning workflow.
Use tauri-plugin-libsql for SQLite database access in Tauri apps with Drizzle ORM, browser-safe migrations, optional AES-256-CBC encryption, and Turso embedded replica sync. Use when working on this plugin's source, writing apps that consume it, adding schema changes, debugging migration or query errors, configuring encryption, or setting up Turso remote sync.
Repo cleanup workflow for dead code removal, stale comment cleanup, naming consistency, redundant code reduction, and safe maintainability improvements. USE FOR: requests like "clean up", maintenance passes, removing unused imports or variables, pruning TODOs, and replacing inappropriate production print statements. DO NOT USE FOR: speculative rewrites, major architecture changes, or broad dependency upgrades.
This skill should be used when the user asks to "add server action", "implement Supabase query", "connect to backend", "add database integration", "implement RLS", "use server actions", "add data mutation", "implement CRUD operations", "revalidate path", "add authentication check", or needs guidance on server-side integration, defense-in-depth security, or type-safe database queries with Supabase.
This skill should be used when the user asks to "start supabase locally", "set up local supabase", "run supabase dev", "initialize supabase project", "configure local database", "start local postgres", "use supabase CLI", "generate database types", or needs guidance on local Supabase development, Docker setup, environment configuration, or database migrations.
Manage database migrations and schema versioning. Use when planning migrations, version control, rollback strategies, or data transformations for any database paradigm.
Add a Layer 3 service-layer guard to an existing service. The guard reads the DB and throws before any mutation. Arguments: "<ServiceName> <operation-method> <precondition-description>"
Use this agent when you need to review database migrations, data models, or any code that manipulates persistent data. Use data-migration-expert for ID mapping validation; use deployment-verification-agent for deploy checklists.
SQL and database migration best practices: Flyway/Liquibase, query optimization, indexing. Use when working with SQL queries or database migrations.
Use this agent when a PR touches production data, migrations, or behavior that could silently discard or duplicate records. Produces a pre/post-deploy checklist with SQL verification queries and rollback procedures. Use data-integrity-guardian to review the migration code; use this agent to produce the deploy-day checklist.
Database migration: schema changes, column cleanup, Alembic
Reactive JPA persistence with Hibernate Reactive 7, Vert.x 5 SQL clients, and Mutiny sessions inside GuicedEE: DatabaseModule setup, persistence.xml configuration, multi-database support, @EntityManager scoping, and environment variable resolution. Use when adding database persistence, configuring Hibernate Reactive, creating DatabaseModule subclasses, wiring Mutiny.SessionFactory, or managing multiple persistence units.
Use this agent when you need to review database migrations, data models, or any code that manipulates persistent data. This includes checking migration safety, validating data constraints, ensuring transaction boundaries are correct, and verifying that referential integrity and privacy requirements are maintained.
How to create and use our alembic database migration tool. Use when making changes to models.py.