Description — what to implement and the why/impact.
Add a convenient npm script to check Prisma migration status without applying changes, aiding local development and CI troubleshooting.
Context & Requirements — background, constraints, design references, edge cases;
Developers need a quick way to inspect pending database migrations. Adding prisma:status to package.json standardizes this workflow.
Acceptance Criteria — a checklist ("- [ ] ...") of specific, testable conditions that define "done".
Implementation Guidance — likely files/modules to touch (use real paths from the repo context)
Testing & Validation — how the contributor should prove it works
- Run
npm run prisma:status (or dry-run equivalent) to verify it executes correctly.
Submission Guidelines — must open a PR that includes "Closes #"; assignment is required before starting.
Wave complexity: Trivial
Description — what to implement and the why/impact.
Add a convenient npm script to check Prisma migration status without applying changes, aiding local development and CI troubleshooting.
Context & Requirements — background, constraints, design references, edge cases;
Developers need a quick way to inspect pending database migrations. Adding
prisma:statustopackage.jsonstandardizes this workflow.Acceptance Criteria — a checklist ("- [ ] ...") of specific, testable conditions that define "done".
"prisma:status": "prisma migrate status"script topackage.json.Implementation Guidance — likely files/modules to touch (use real paths from the repo context)
package.jsonTesting & Validation — how the contributor should prove it works
npm run prisma:status(or dry-run equivalent) to verify it executes correctly.Submission Guidelines — must open a PR that includes "Closes #"; assignment is required before starting.
Wave complexity: Trivial