メニュー
Run database migrations against the target environment. Use when applying schema changes, running pending migrations, or checking migration status. Do NOT use for seed data insertion or database backups.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Improve a SKILL.md file by applying missing or weak skill-authoring patterns (17 patterns across 7 categories). Use when a skill needs strengthening, after running skill:check to identify gaps, or when creating a new skill from scratch. Do NOT use for prompt-level improvements (use prompt:enhance instead) or for evaluation only (use skill:check instead).
Run a baseline-enhance-reeval loop on a SKILL.md to measure improvement. Generates targeted test cases for enhanced patterns to ensure the comparison reflects actual improvement in changed areas. Use when testing whether skill:enhance actually improves eval scores, measuring skill quality before and after changes, or automating the measure-enhance-measure workflow. Do NOT use for evaluation only (use /eval-run instead), for enhancement only (use skill:enhance instead), or for setting up eval infrastructure (use /eval-analyze and /eval-dataset instead).
Evaluate a SKILL.md file using three-layer linting: schema validation, 17 skill-authoring patterns, and optional substance review (--deep). Use when reviewing skill quality, checking pattern coverage, testing activation metadata, or assessing a skill before sharing. Add --deep for qualitative substance review. Do NOT use for prompt-level analysis (use prompt:skill-checker instead) or for enhancing/rewriting skills (use skill:enhance instead).
Deploy a service to the staging environment with health checks and rollback. Use when asked to deploy, push to staging, release to staging, or test a deployment. Do NOT use for production deployments (use deploy:production instead) or for CI/CD pipeline configuration.
Format source code files
Analyze project dependencies for security vulnerabilities, license compliance, and staleness. Use when auditing dependencies, checking for CVEs, reviewing license obligations, or assessing upgrade risk. Not for actually upgrading packages (use update:deps instead).
| name | db:migrate |
| description | Run database migrations against the target environment. Use when applying schema changes, running pending migrations, or checking migration status. Do NOT use for seed data insertion or database backups. |
| argument-hint | <environment> [--status] [--rollback <N>] |
| user-invocable | true |
Apply pending database migrations to a target environment (dev, staging, production) using Alembic.
Read the environment argument. Valid values: dev, staging, production.
If production is specified, require confirmation via AskUserQuestion before proceeding:
"You are about to run migrations against PRODUCTION. This cannot be undone automatically. Continue?"
alembic --config config/${env}.ini current
alembic --config config/${env}.ini heads
If --status flag is set, display current revision and pending migrations, then stop.
alembic --config config/${env}.ini upgrade head
Report the number of migrations applied and the new current revision.
Run the schema validation script:
python scripts/verify_schema.py --env ${env}
Report any discrepancies between the expected schema and the actual database state.
If --rollback <N> is specified, roll back N migrations instead of applying:
alembic --config config/${env}.ini downgrade -${N}