find-variances

Extract computed styles from live and dev sites into variance reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract computed styles from live and dev sites, compare property-by-property, and write a structured variance array to the section report. Standalone or auto-invoked by pull-section.

Core Features & Use Cases

  • Extract computed styles across all breakpoints (desktop, tablet, mobile) and compare live vs dev values.
  • Support case-scoped extractions with anchor maps, merge variances into the section report, and auto-generate actionable test conditions.
  • Integrate with refine-section and verify-section workflows to guide fixes and regression checks.

Quick Start

Run /theme-forge find-variances <section-key> [--page <page>] to extract live and dev variances for a section.

Frequently Asked Questions about find-variances

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

FAQPage Schema
How do I automate computed style extraction and variance discovery for theme migrations?

Automated variance discovery extracts computed styles from live and dev sites, compares them property-by-property, and writes a structured variance array into the section report to streamline theme migrations.

How do I compare live site and dev site CSS variances across desktop, tablet, and mobile breakpoints?

Per-breakpoint computed style extraction compares live and dev values across desktop, tablet, and mobile breakpoints, merging the discovered variances into existing section report entries for comprehensive analysis.

Can I scope computed style extractions to specific cases and use anchor maps during a theme migration?

Case-aware scoping with optional anchor maps allows targeted extraction of computed styles for specific sections, ensuring variance comparisons remain focused on relevant elements during theme migrations.

Do I need Playwright and a theme-forge config to extract and compare computed styles?

Yes, the automated extraction relies on Playwright-based tooling and the theme-forge config to extract computed styles, compare variances, and output cached results into section reports.

What is the best way to generate actionable test conditions for CSS variances found between environments?

After extracting and comparing computed styles, the workflow auto-generates actionable test conditions for fixes and integrates with refine-section and verify-section workflows to guide regression checks.

Why are my computed style variances not merging into the section report correctly?

Variance merging requires proper section-key targeting and existing variance entries; the tool merges new computed style differences into existing report structures and caches results in .theme-forge/reports/sections.