pull-section

Automate live-vs-dev extraction, variance computation, fixes, and verification for a Shopify theme section.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Execute an end-to-end visual migration workflow for a single Shopify theme section.

Core Features & Use Cases

  • End-to-end workflow: capture live and dev references, compute variances, apply fixes, and verify results.
  • Supports debugging with transcripts, step-by-step logs, and a structured learning system to retain migrator knowledge.
  • Use Case: migrate a single section like the header or hero, ensuring pixel alignment between live and development themes.

Quick Start

Run the pull-section command to start the full compare→fix→verify loop for a specific section on a chosen template.

Frequently Asked Questions about pull-section

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

FAQPage Schema
How do I automate Shopify theme section migration between live and dev environments?

Shopify theme section migration is automated by extracting live and dev references, computing visual variances, applying fixes, and verifying pixel alignment in a repeatable loop.

What is the best way to debug visual variance in a Shopify theme section?

Debugging visual variance in a Shopify theme section is handled by computing differences between live and dev references, applying CSS overrides, and retaining migrator knowledge in structured step-by-step logs.

How do I ensure pixel alignment for a single section during a Shopify visual migration?

Pixel alignment for a single section is ensured by running an end-to-end compare, fix, and verify loop that targets a specific section within a documented template JSON.

Do I need access to both live and target themes to automate section matching?

Yes, section matching requires access to both the live and target themes, a documented section in the target template JSON, and the theme-forge pull-section invocation to execute the workflow.

How does variance tracking work when migrating a Shopify header or hero section?

Variance tracking works by capturing live and dev references for the specific section, computing the visual differences, and storing the verified results in a per-section report.

Can I use this visual migration workflow for an entire Shopify template page at once?

No, the visual migration workflow is designed to execute end-to-end matching for a single Shopify theme section on a defined template page, rather than migrating the entire page simultaneously.