What problem does it solve?
Upgrading a downstream Open Mercato application from 0.6.6 to 0.6.7 involves breaking changes like moved pg-errors imports, flattened scheduler queue payloads, and removed scheduler metadata that are tedious and error-prone to fix by hand.
Core Features & Use Cases
- Automatic import migration: Rewrites the exact
@open-mercato/core/modules/communication_channels/lib/pg-errors module specifier to @open-mercato/shared/lib/db/pg-errors while preserving imported names and formatting.
- Proven scheduler payload unwrapping: Removes the redundant
.payload segment from <job>.payload.payload.<field> accesses only after proving the consumer handles a queue targeted by a scheduler registration in the same repository.
- Detect-and-report audits: Flags scheduler consumers reading removed metadata (
scheduleId, scheduleName, scopeType, triggeredAt) and query-index callbacks that swallow encryption errors, without inventing replacements.
- Use Case: After installing Open Mercato 0.6.7 in your downstream app, run this Skill with
--dry-run to preview every required change, then apply the bounded edits and verify with typecheck, tests, and build.
Quick Start
Ask the AI to upgrade your Open Mercato app from 0.6.6 to 0.6.7 using this skill, optionally with a dry run first to review the plan.