mirrord-db-branching

1# Mirrord DB Branching Skill
2 
3## Purpose
4 
5Generate and validate `mirrord.json` configurations for database branching:
6- **Generate** valid `db_branches` configs from natural language descriptions
7- **Explain** copy modes, connection sources, schema migrations, IAM authentication, and branch management
8- **Validate** user-provided configs against schema requirements
9- **Troubleshoot** common DB branching issues
10 
11DB branching is a **Team / Enterprise** feature. It spins up an isolated branch of a remote database so developers (and AI agents) can run schema changes, migrations, and experiments without affecting teammates or shared environments.
12 
13## Security Boundaries
14 
15> **IMPORTANT:** Follow these security rules for all operations in this skill.
16 
17- **No hardcoded credentials:** Never put actual credentials, passwords, connection strings, or secret values in generated configurations. Point mirrord at where the value already lives (an env var name, a Kubernetes Secret, or Google Secret Manager) instead of inlining it. The only exception is the config's own `value` literal source, which the user must supply themselves — never invent one.
18- **Credential protection:** Never ask users to share database passwords or credentials with the agent. Instruct them to keep credentials in environment variables, Kubernetes Secrets, or Secret Manager.
19…