Write a migration, run it against the dev database, and confirm the schema matches.
/goal GOAL: Complete Dev Database Migration Proof for a data-backed backend service: Write a migration, run it against the dev database, and confirm the schema matches. CONTEXT: - Before editing, read the nearest AGENTS.md/CLAUDE.md, current issue or PLAN.md, and any failing logs already in the repo. - Inspect schema files, migrations, models, repositories, and data tests. - Establish a baseline by running or locating evidence for: `migration applied to dev DB and schema comparison`. CONSTRAINTS: - Keep the scope limited to this goal; do not expand into unrelated cleanup. - Do not weaken tests, delete assertions, or mask errors to make verification pass. - Respect the repository's AGENTS.md/CLAUDE.md instructions and existing patterns. - Do not destroy or rewrite data without a dry-run, rollback, and row-count/checksum evidence. - Do not hide database errors behind warnings or silent fallbacks. DONE WHEN: - The implementation or documentation directly satisfies: Write a migration, run it against the dev database, and confirm the schema matches. - The verification command or evidence path succeeds: `migration applied to dev DB and schema comparison`. - The final diff is scoped to the relevant files and has no unrelated formatting churn. VERIFY: - Run `migration applied to dev DB and schema comparison` or the closest repo-local equivalent if the exact command is not available. - Capture before/after evidence for the behavior, metric, report, or artifact involved. - If verification cannot run locally, stop and report the missing dependency instead of guessing success. OUTPUT: - Summarize changed files, key decisions, verification output, and remaining risks. - Include any follow-up that is required for production rollout or human review. STOP RULES: - Pause if secrets, production access, stakeholder decisions, or destructive data operations are required. - Pause after three failed fix attempts on the same symptom and challenge the root-cause hypothesis. - Do not mark the goal complete until the current repository state has been audited against DONE WHEN.
原始来源: Claude Code prompt library
证据摘要: write the migration, run it against the dev database, and confirm the schema matches; source: Claude Code prompt library; type: official-agent-task; verification: migration applied to dev DB and schema comparison