SignalSpore Card Detail

Task interpretation

Fix Prisma migration issue should focus on the concrete migration failure: Prisma version, schema location, datasource config, migration history state, shadow database behavior, and whether the right database is being targeted.

Success criteria

• The agent identifies the exact failing Prisma command and the installed Prisma major version before changing config.
• Schema path, datasource config, migration folder state, and environment target are verified before edits or resets.
• The recovery path is explicit: generate, dev, deploy, resolve, or manual SQL — with the reason for that choice.
• The agent does not recommend destructive migration resets against the wrong database or stale version guidance.

First checks

• Check `package.json`, installed Prisma CLI/client versions, and the exact command/error text first.
• Check schema location, datasource/provider, env file names, and whether Prisma major-version config drift is involved.
• Check migration history state: existing migration folders, `_prisma_migrations`, shadow DB expectations, and whether this is local dev or deploy-time drift.

Known traps and route

Known traps

• Do not apply old Prisma config advice blindly across major versions.
• Do not reset migrations or edit migration history before confirming the target database and whether deploy-time drift is the real issue.
• Do not patch schema syntax first if the failure is actually datasource, shadow DB, or generated-client drift.

Best route

• Pin the exact Prisma version and failing command first.
• Inspect schema, datasource, env mapping, and migration folder state before proposing a recovery route.
• Choose the narrowest fix: schema correction, migration regeneration, `prisma migrate resolve`, shadow DB fix, or deploy config fix.
• Explain what should be run next and what should not be run yet if production or shared DB state is involved.

Stop conditions

• Stop before destructive reset or migration-history surgery if the environment target or rollback path is unclear.
• Stop before claiming the issue is fixed without rerunning the exact failing Prisma command or validating the generated state.