- Home
- Skills
- Data & Databases
- Repair Prisma Shadow Database Migration Diff
More screenshots
Works with the AI Agents you already use
Repair Prisma Shadow Database Migration Diff
Investigate Prisma shadow database errors caused by privilege and schema divergence.
$1
Repair Prisma Shadow Database Migration Diff
Example session with this skill installed
Prisma migrate reports drift after a developer changes shadow database permissions.
Available evidence: Prisma migration folders and shadow database permissions (partial extracts only). Additional sources requested: migration engine logs and schema snapshots. Identify the checks that can be supported, deliver a useful bounded assessment, and list the exact remaining review gates without pretending to execute changes.
- Read your context and instructions
- Compiled the repair prisma shadow
Repair Prisma Shadow Database Migration Diff — EVIDENCE-LIMITED REVIEW
Scenario received
Prisma migrate reports drift after a developer changes shadow database permissions.
Evidence inventory
- S1: Prisma migration folders — partial extract described by the requester; original full source not provided here.
- S2: shadow database permissions — partial extract described by the requester; original full source not provided here.
- S3: migration engine logs — NOT PROVIDED; required to validate dependent findings.
- S4: schema snapshots — NOT PROVIDED; required to validate dependent findings.
Case-specific checks
Trace migration replay order. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
2.
Check shadow schema access. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
3.
Identify branch specific drift. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
4.
Validate a disposable database replay. INCOMPLETE until matching source anchors can be examined; document the observable facts, counterexamples and decision gate.
Deliverables
Migration inconsistency inventory. Create an evidence-linked section with observations, missing data, owner and next validation step.
Permission repair outline. Create an evidence-linked section with observations, missing data, owner and next validation step.
Clean replay test plan. Create an evidence-linked section with observations, missing data, owner and next validation step.
Acceptance gate
No production schema reset is suggested without verified backup and explicit approval. Do not label this gate passed until supplied source records actually demonstrate it.
Verdict and next action
INCOMPLETE — evidence required. Request S3 and S4 from the authorized owner, reconcile them with S1 and S2, then repeat the four checks and log remaining conflicts. No production change, approval, communication, or test run is claimed.
Connects securely to your tools. The creator never sees your data.
About this skill
Prisma migration failures often stem from shadow database privilege issues or schema divergence that halts development workflows. This skill investigates these errors by tracing migration replay orders and identifying drift between branches. It provides a structured path to resolve permission blocks and schema inconsistencies without risking production data.
What it does
- Trace migration order by citing evidence from migration folders and engine logs.
- Audit shadow permissions to identify missing privileges that block shadow database creation.
- Identify branch drift by comparing schema snapshots against migration history.
- Validate replays via disposable database test plans to ensure clean migration execution.
How it works
- Source analysis involves mapping migration folders and schema snapshots into an evidence register.
- Permission auditing checks shadow database access logs against required Prisma engine capabilities.
- Drift detection isolates specific SQL changes causing divergence in the shadow environment.
- Repair planning generates an inconsistency inventory and a permission repair outline for human review.
Frameworks & tools
Specifically designed for the Prisma ORM ecosystem, including Prisma Migrate and the Prisma Schema Language (PSL). It operates on migration engine logs, schema.prisma files, and SQL migration snapshots.
Why this beats prompting it yourself
Generic prompts often suggest a full production reset which is dangerous and unnecessary. This skill enforces a strict evidence register and decision gates, ensuring no resolution is proposed without citing specific log entries or permission gaps.
Use cases
- Resolve "shadow database could not be created" errors in CI/CD pipelines.
- Fix migration drift after merging branches with conflicting schema changes.
- Debug permission denied errors when the Prisma engine lacks
CREATE DATABASErights.
Known limitations
Requires actual migration logs and schema snapshots to function. It cannot perform automated database repairs or schema resets and requires qualified human review for all proposed changes.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Data & Databases.
No direct verification of inaccessible production systems, external services or private accounts. Partial or conflicting inputs result in INCOMPLETE / CONFLICT findings rather than invented conclusions. Domain-sensitive decisions require qualified owner review.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 26 days ago
Permissions
Provide only materials you are authorized to share. Use a reviewed environment for proposed changes; keep deployment, production modifications, and third-party communication under explicit human approval.