agent-db

Enforce database governance rules and generate SQL migration changesets.

1|Updated Aug 18, 2025
One-click install
npx skills add https://github.com/djb258/imo-creator --skill agent-db
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-db
Source: https://github.com/djb258/imo-creator/tree/main/skills/agent-db
Command: npx skills add https://github.com/djb258/imo-creator --skill agent-db

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the enforcement of database governance rules and the generation of database migration scripts, ensuring data integrity and compliance while reducing manual effort.

Core Features & Use Cases

  • Database Governance Enforcement: Validates schema changes against predefined rules (registry-first, cardinality, immutability, etc.).
  • Migration Generation: Creates ordered SQL migration files and rollback plans based on specified database targets.
  • Risk Classification: Assesses the risk level of database changes (LOW, MED, HIGH).
  • Drift Detection: Identifies discrepancies between the database state and the defined schema registry when fixing issues.
  • Use Case: When a new feature requires database schema modifications, this agent will analyze the proposed changes, ensure they comply with all governance policies, generate the necessary SQL migration scripts and a safe rollback plan, and classify the risk associated with the change before it's applied by another agent.

Quick Start

Use the agent-db skill to generate database migrations for the work packet with ID 'wp-12345' targeting the 'neon' database system.

Frequently Asked Questions about agent-db

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate database governance and schema migration generation?

Database governance automation validates schema changes against predefined rules like registry-first compliance and RAW immutability, then generates ordered SQL migration scripts and rollback plans to ensure data integrity.

What is database governance enforcement for SQL schema changes?

Database governance enforcement validates proposed SQL schema changes against predefined rules including cantonal cardinality, vendor JSON containment, and bridge versioning before generating any DB_CHANGESET artifacts.

How do I generate a database rollback plan for a high risk migration?

Generating a database rollback plan involves analyzing the proposed schema modifications, classifying the risk level as LOW, MED, or HIGH, and creating safe rollback scripts alongside the ordered SQL migration files.

Can I detect database schema drift against a defined registry?

Yes, drift detection identifies discrepancies between the current database state and the defined schema registry, allowing you to fix schema issues before generating compliant migration scripts.

What database governance rules are enforced before generating migrations?

Enforced governance rules include registry-first compliance, cantonal cardinality, RAW immutability, vendor JSON containment, and bridge versioning, all validated before any DB_CHANGESET artifacts are generated.

Do I need a specific work packet format to generate database migrations?

Yes, database migration generation operates on WORK_PACKETs requiring database changes, analyzing the proposed modifications and targeting specified database systems like neon to produce compliant changesets.