Verified:GitHub

cutover

... (we'll need to know what goes here before we can answer the rest of the prompt; luckily there are only two sentences and they are short. The rest of the prompt is just formatting noise. We'll ignore it.)

Updated Aug 27, 2026

Search Tags:#checklist #production #verification #migration #theme #go-live #cutover

Ready to run

npx skills add https://github.com/cfagerlin/theme-forge --skill cutover

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cutover
Source: https://github.com/cfagerlin/theme-forge/tree/main/cutover
Command: npx skills add https://github.com/cfagerlin/theme-forge --skill cutover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Display and manage the cutover checklist for production go-live. These items are surfaced automatically during pull-page and pull-section runs, helping teams coordinate the switch.

Core Features & Use Cases

Load and display the production cutover items generated by migration runs.
Verify item existence and syntax with a dedicated check, then group items by type for clear handoff.
Use during go-live planning to assign responsibilities and confirm readiness across templates, assets, and configurations.

Quick Start

Run the cutover command with --verify to validate items, then review the generated production checklist.

Frequently Asked Questions about cutover

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track production go-live cutover tasks for a theme migration?▼

To track production go-live cutover tasks, you need a checklist that loads items from a `.theme-forge/cutover.json` file. This file references valid resources generated during migration runs, allowing you to list and verify manual cutover actions.

What manual cutover actions are required for going live with a new theme?▼

Manual cutover actions for going live include template assignments, asset verifications, and section or page adjustments. These items are surfaced automatically during pull-page and pull-section runs to help coordinate the production switch.

How do I verify cutover checklist items before a production go-live?▼

You can verify cutover checklist items by running the cutover command with the `--verify` flag. This checks item existence and syntax, then groups items by type for clear handoff and readiness confirmation across templates and configurations.

Do I need a specific file to load the production cutover checklist?▼

Yes, you need the `.theme-forge/cutover.json` file to exist and reference valid resources. This file is a prerequisite for loading, displaying, and verifying the production cutover checklist generated by your migration runs.

Can I assign responsibilities for template and asset configurations during go-live planning?▼

Yes, you can assign responsibilities and confirm readiness across templates, assets, and configurations during go-live planning. The checklist groups verified cutover items by type, facilitating clear handoff and team coordination for the production switch.