Skip to content
Dev MCP

Maintenance

The maintenance command handles ongoing project health — dependency updates, platform version upgrades, API version bumps, and configuration drift.

maintenance

Workflow

Section titled “Workflow”
  1. Assessment — reads package.json across all workspaces, runs pnpm outdated, checks platform versions against latest stable, runs security audit, checks configuration drift
  2. Maintenance plan — categorises updates by risk (security fixes, patch, minor, major, API version bumps). Presents for approval.
  3. Apply — applies updates incrementally in risk order (lowest first), validates between each tier
  4. Verification — full type check, lint, build, dev server start, playwright spot-check
  5. Summary — before/after versions table, security fixes, files modified, recommended follow-up

What It Checks

Section titled “What It Checks”
CheckDetails
Dependenciespnpm outdated --recursive across all workspaces
Platform versionCurrent framework version vs latest stable
API versionCurrent API version vs latest (e.g., Storefront API)
Securitypnpm audit for known vulnerabilities
Configuration.mcp.json against current standards, project structure alignment

When to Run

Section titled “When to Run”
  • After completing a major build phase (suggested automatically after audit)
  • Before starting new feature work on an existing project
  • When Shopify announces API deprecations or version changes
  • As part of regular project maintenance cycles