worker-role-database

Coordinate safe schema changes and migrations across ArangoDB and PostgreSQL.

1|Updated Feb 6, 2026

Search Tags:#database #migrations #schema #prisma #backups #arangojs

Ready to run

npx skills add https://github.com/eron1703/claude-config-loader --skill worker-role-database

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worker-role-database
Source: https://github.com/eron1703/claude-config-loader/tree/main/skills/worker-role-database
Command: npx skills add https://github.com/eron1703/claude-config-loader --skill worker-role-database

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database teams often struggle with coordinating schema changes, migrations, and associated data operations across multiple databases. This skill provides a dedicated agent that enforces safety, traceability, and consistency during changes.

Core Features & Use Cases

Schema changes & migrations management: orchestrates safe migrations for PostgreSQL (via Prisma) and schema updates for other databases, with validation and rollback planning.
Data integrity & backups: requires backups before destructive actions and verifies results after every change.
Seed data & verification: supports seed data operations and post-change checks to ensure data correctness across environments.

Quick Start

Specify the target database, the migration details, and backup preferences to start a safe schema change.

Frequently Asked Questions about worker-role-database

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

FAQPage Schema

How do I coordinate database migrations across ArangoDB and PostgreSQL safely?▼

Database migrations across ArangoDB and PostgreSQL are coordinated by using arangojs for ArangoDB and Prisma for PostgreSQL. This approach enforces strict safety rules, requiring backups before destructive operations and verifying changes after execution to ensure data integrity.

What is the safest way to manage schema changes in a mixed database environment?▼

Safe schema changes in mixed database environments require automated validation, backup creation, and rollback planning. The process orchestrates migrations via Prisma, logs all actions for traceability, and conducts post-change checks to guarantee data correctness across different environments.

Does this database migration approach support seed data management and verification?▼

Yes, seed data management and verification are fully supported. The workflow applies seed data operations and executes post-change checks to ensure data correctness and consistency across all targeted database environments after migrations are completed.

Can I run raw SQL or AQL queries during schema evolution?▼

No, running raw queries is strictly prohibited unless explicitly instructed. The workflow mandates using arangojs for ArangoDB and Prisma for PostgreSQL to execute schema changes, ensuring all operations remain safe, traceable, and validated.

How do I back up data before performing destructive database operations?▼

Backups are automatically required before any destructive database operations are executed. The system enforces this safety rule by initiating backups prior to schema changes and validating the results after every modification to prevent data loss.

Why do I need Prisma and arangojs for database schema migrations?▼

Prisma and arangojs are required to enforce safe, automated schema changes for PostgreSQL and ArangoDB respectively. Using these dedicated clients prevents unsafe raw queries, ensures strict validation, and maintains traceability during data operations.