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.
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.
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.
Use this agent when reviewing PRs that touch database migrations, data backfills, or any code that transforms production data. This agent validates ID mappings against production reality, checks for swapped values, verifies rollback safety, and ensures data integrity during schema changes. Essential for any migration that involves ID mappings, column renames, or data transformations.
Keep a feature branch up to date with the main branch using rebase. Use this skill whenever the user wants to sync, update, or rebase their feature branch onto main (or master), after another PR has merged, when they are getting behind on main, or when they want to avoid merge conflicts before opening or updating a PR. Trigger on phrases like "sync my branch", "rebase onto main", "pull main into my branch", "update my branch", "I'm behind main", or "pull after the PR merged".
Run and test the example-app against a local PostgreSQL database. USE FOR: starting Postgres via Docker Compose, running SQL migrations, building with code generation, running the example app, verifying generated queries work end-to-end. DO NOT USE FOR: writing unit tests, CI/CD pipeline setup.
Manage database migrations and schema versioning. Use when planning migrations, version control, rollback strategies, or data transformations for any database paradigm.
Manage database migrations and schema versioning. Use when planning migrations, version control, rollback strategies, or data transformations for any database paradigm.
Design PostgreSQL, MongoDB, or Redis schemas with entities, relationships, indexes, constraints, migrations, query optimization, and backward-compatible schema evolution
Provision database infrastructure, initialize migration framework, configure environments, and verify connectivity/migration gates
Aplica ingenieria de software moderna para query optimization practice con foco en robustez, mantenibilidad y excelencia operacional.
Generate database migrations with up/down scripts — Alembic, Flyway, Liquibase, and framework-native migrations.
Create and run database migrations for fancai. Use when changing database schema, adding columns, creating tables, or modifying SQLAlchemy models.
Expert Elasticsearch guide covering index design (mappings, analyzers, sharding), query DSL (full-text, filters, aggregations, fuzzy), indexing patterns (bulk API, ingest pipelines), performance (query profiling, caching, segment management), and operational best practices. Use when building search features, log analytics, or autocomplete with Elasticsearch or OpenSearch.
