| name | database-v2 |
| slug | database-v2 |
| description | Database Workflow Bundle workflow skill. Use this skill when the user needs database development and operations workflow covering SQL, NoSQL, database design, migrations, optimization, and data engineering, while preserving upstream workflow context, copied support files, and provenance before merge or handoff. |
| version | 0.0.1 |
| category | backend |
| tags | ["database-v2","database","sql","nosql","migrations","performance","schema-review","operations","omni-enhanced"] |
| complexity | intermediate |
| risk | caution |
| tools | ["codex-cli","claude-code","cursor","gemini-cli","opencode"] |
| source | omni-team |
| author | Omni Skills Team |
| license | Unknown |
| date_added | 2026-04-16 |
| date_updated | 2026-05-10 |
| source_type | omni-curated |
| maintainer | Omni Skills Team |
| family_id | database-v2 |
| family_name | Database Workflow Bundle |
| variant_id | omni |
| variant_label | Omni Curated |
| is_default_variant | true |
| derived_from | skills/database-v2 |
| upstream_skill | skills/database-v2 |
| upstream_author | sickn33 |
| upstream_source | community |
| upstream_pr | 271 |
| upstream_head_repo | diegosouzapw/awesome-omni-skills |
| upstream_head_sha | 93ab394af5645f7127d5003ee02c9566ae5353cd |
| curation_surface | skills_omni |
| enhanced_origin | omni-skills-private |
| source_repo | diegosouzapw/awesome-omni-skills |
| replaces | ["database-v2"] |
Database Workflow Bundle
Overview
Use this skill to review, plan, or guide database work that may affect:
- data correctness
- schema compatibility
- migration safety
- query performance
- operational reliability
- backup and restore readiness
- stateful runtime behavior in containers or Kubernetes
This skill is for database change analysis and operational review, not for blind execution. Use it when the task requires judgment across application code, schema or model changes, migration order, runtime behavior, and rollback risk.
If this copy came from an imported upstream workflow, preserve provenance markers, copied support files, and origin notes unless the user explicitly asks for cleanup.
When to Use
Activate this skill when the request includes one or more of the following:
- SQL schema changes, indexes, constraints, views, or query rewrites
- NoSQL collection or document model changes
- migration creation, ordering, rollback, or drift review
- slow query investigation or execution-plan review
- backup, restore, retention, or recovery-readiness checks
- database deployment in Docker, Kubernetes, or other stateful runtimes
- data pipeline or batch-load changes that can affect integrity or performance
Do not use this skill as the primary workflow when the task is only:
- basic CRUD application coding with no schema or runtime impact
- generic infrastructure work unrelated to persistence
- pure analytics or BI interpretation with no database design or operations decision
Activation Boundary
Before doing deep review, confirm these inputs:
- Engine and version: PostgreSQL, MySQL-compatible, MongoDB, or another named engine.
- Change type: schema/model, migration, query, operational config, restore, or performance issue.
- Execution context: local dev, CI, production, managed service, container, or Kubernetes.
- Risk surface: destructive DDL, backfill, lock risk, storage change, credential handling, or restore dependency.
- Evidence available: migration files, schema diff, EXPLAIN output, logs, manifests, backup procedure, or incident symptoms.
If the request does not provide these, ask for them before approving or proposing high-risk changes.
Workflow
-
Classify the database task
