How do I install the Trigger Migration skill?

Run npx skillmds@latest add majiayu000/trigger-migration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Trigger Migration safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Trigger Migration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Trigger Migration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Trigger Migration?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Trigger Migration by majiayu000 — Agent Skill

Name: Trigger Migration
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Trigger Migration Lambda

Manually triggers database migrations in deployed environments.

When to Use

After manual SST deployment (without CI/CD)
To re-run failed migrations
Emergency migration fixes

Commands

Development

aws lambda invoke --function-name template-saas-api-migrate-lambda-dev /dev/null

Production

aws lambda invoke --function-name template-saas-api-migrate-lambda-prod /dev/null

Prerequisites

AWS CLI configured with correct profile/credentials
Lambda function deployed (via SST)
Database accessible from Lambda

How It Works

The Migration Lambda:

Connects to PostgreSQL using DbConnStr secret
Runs Alembic migrations via migration.sh
Returns success/failure status

Lambda Naming Convention

{project}-api-migrate-lambda-{stage}

For this project: template-saas-api-migrate-lambda-{dev|prod}

Checking Migration Status

View Lambda Logs

aws logs tail /aws/lambda/template-saas-api-migrate-lambda-dev --follow

Check Current Migration

# Via Docker locally
docker compose exec back uv run alembic current

# In production, check Lambda logs

CI/CD Integration

Normally, migrations run automatically in CI/CD:

Backend deploy job completes
Migrate job triggers Migration Lambda
Pipeline fails if migration fails

See .github/workflows/deploy-backend.yml.

Manual Production Migration

For production migrations outside of CI/CD:

Use .github/workflows/migrate-production.yml
Requires typing "migrate-production" to confirm
Creates audit trail in GitHub Actions

Troubleshooting

Lambda Timeout

Check database connectivity
Verify DbConnStr secret is set
Check Lambda has VPC access if needed

Migration Errors

Check Lambda CloudWatch logs
Verify migration files are correct
Test locally first with Docker

---name: trigger-migrationdescription: Manually triggers the migration Lambda for deployed environments. Use when migrations need to be run outside of CI/CD.--- # Trigger Migration Lambda Manually triggers database migrations in deployed environments. ## When to Use - After manual SST deployment (without CI/CD) - To re-run failed migrations - Emergency migration fixes ## Commands ### Development ```bash aws lambda invoke --function-name template-saas-api-migrate-lambda-dev /dev/null ``` ### Production ```bash aws lambda invoke --function-name template-saas-api-migrate-lambda-prod /dev/null ``` ## Prerequisites 1. AWS CLI configured with correct profile/credentials 2. Lambda function deployed (via SST) 3. Database accessible from Lambda ## How It Works The Migration Lambda: 1. Connects to PostgreSQL using `DbConnStr` secret 2. Runs Alembic migrations via `migration.sh` 3. Returns success/failure status ## Lambda Naming Convention `{project}-api-migrate-lambda-{stage}` For this project: `template-saas-api-migrate-lambda-{dev|prod}` ## Checking Migration Status ### View Lambda Logs ```bash aws logs tail /aws/lambda/template-saas-api-migrate-lambda-dev --follow ``` ### Check Current Migration ```bash # Via Docker locally docker compose exec back uv run alembic current # In production, check Lambda logs ``` ## CI/CD Integration Normally, migrations run automatically in CI/CD: 1. Backend deploy job completes 2. Migrate job triggers Migration Lambda 3. Pipeline fails if migration fails See `.github/workflows/deploy-backend.yml`. ## Manual Production Migration For production migrations outside of CI/CD: - Use `.github/workflows/migrate-production.yml` - Requires typing "migrate-production" to confirm - Creates audit trail in GitHub Actions ## Troubleshooting ### Lambda Timeout - Check database connectivity - Verify `DbConnStr` secret is set - Check Lambda has VPC access if needed ### Migration Errors - Check Lambda CloudWatch logs - Verify migration files are correct - Test locally first with Docker

Frequently asked questions

Trigger Migration