SQLx Migration

Use the SQLx CLI to create migration files instead of manually creating timestamped files.

Identify the project or crate root where SQLx migrations should live.
- Prefer the directory that contains an existing migrations/ directory.
- If there are multiple crates/projects, ask the user which one unless the target is obvious.
Convert the requested migration description to a short snake_case name, for example create_users_table.
Run just setup_test_envs from the project root
Run the SQLx CLI from crates/macro_db_client folder:
```
cargo sqlx migrate add name_of_migration
```
Replace name_of_migration with the actual snake_case migration name.
Do not manually add timestamps or hand-create migration filenames; sqlx migrate add generates the correct timestamped file.
After the command succeeds, read the generated migration file and add the requested SQL changes there.
If sqlx is not installed or not on PATH, stop and tell the user to install sqlx-cli rather than manually creating the migration file.

Third-party checks

No alerts28d3 checks · Risk SAFE

Gen Agent Trust Hub28d
The skill provides a workflow for creating database migrations using the SQLx CLI. It uses standard development tools like cargo and just to manage the migration process within the macro-inc project structure. A minor risk is noted regarding indirect prompt injection since user-provided input is used in shell commands, though the instruction to format input as snake_case serves as a basic security measure.
Socket28d
No alerts
Snyk28d
Risk: LOW · No issues

/sqlx-migration