status

Summarize Shopify theme migration progress from JSON state in .theme-forge/.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cfagerlin/theme-forge --skill status-cfagerlin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/cfagerlin/theme-forge/tree/main/status
Command: npx skills add https://github.com/cfagerlin/theme-forge --skill status-cfagerlin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read all JSON state in .theme-forge/ and produce a clear, human-readable progress report.

Core Features & Use Cases

  • Load and interpret project state from config.json, mapping files, and reports to compute per-section and per-page progress.
  • Summarize overall progress and flag pending, pulled, failed, and reviewed items for targeted action.
  • Provide a concise, actionable snapshot that teammates can reference during migration planning.

Quick Start

Onboard the project with /theme-forge onboard and then run /theme-forge status to view the migration progress.

Frequently Asked Questions about status

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

FAQPage Schema
How do I check Shopify theme migration progress from JSON state files?

The status report summarizes theme migration progress by reading JSON state from .theme-forge/ directories to compute per-section and per-page statuses. It generates a structured, human-readable report summarizing mapped, pulled, failed, and pending items.

How do I generate a human-readable report for pending and failed theme migration sections?

Generating a report for pending and failed sections requires running the status command after onboarding. It loads config.json, mapping files, and reports to flag pending, pulled, failed, and reviewed items for targeted action.

What is the best way to track what has been mapped or pulled during a theme migration?

Tracking mapped or pulled theme migration items is best done by computing progress from project state files. This approach interprets config.json and mapping data to provide a concise, actionable snapshot for migration planning.

Do I need to run onboarding before checking theme migration status?

Yes, onboarding the project with the theme-forge onboard command is required before checking status. Onboarding sets up the necessary .theme-forge/ directory structure and config.json state files required to compute progress.

Can I use this status report for projects not migrating Shopify themes?

No, this status report is designed specifically for Shopify theme migrations. It computes per-section and per-page progress by reading theme-forge config and plan data, applying only to projects migrating themes.