What is the primary purpose of the bake-site-compare skill?

It is designed to ensure that a static version of a website (a 'baked' site) is visually and functionally identical to its original WordPress production environment.

Does this skill help with bug tracking?

Yes, it is configured to create structured issues in Linear for any discrepancies found, including evidence like screenshots and console logs.

Can it detect issues specific to WordPress page builders?

Yes, it includes specific logic to check Elementor Pro frontend configurations, background images in inline styles, and lazy-loaded image attributes common in WordPress.

Which browser automation tools does this skill support?

The skill requires a browser automation MCP to be available, such as Playwright or the claude-in-chrome plugin.

Bake Site Comparison

Name: Bake Site Comparison
Author: coreyja

bycoreyja

•

Browser Automation

Compares production WordPress sites with static versions to detect visual discrepancies and functional errors.

About

Bake Site Comparison is a specialized quality assurance skill for developers migrating WordPress sites to static versions. It automates the validation process by performing side-by-side visual audits, network request analysis, and console error detection. The skill specifically targets common static site failure points such as broken lazy-loading, missing background images in CSS, and Elementor form misconfigurations, ensuring that your static 'baked' deployment is indistinguishable from the production source.

Key Features

Comprehensive network analysis to identify failed assets and 404 errors
Side-by-side visual comparison using browser automation screenshots
Direct integration with Linear for automated issue tracking and bug reporting
WordPress-specific validation for lazy-loaded images and FontAwesome icons
Automatic sitemap discovery to ensure all site pages are audited
12 GitHub stars

Use Cases

Regression testing for static deployments to catch missing CSS background images
Auditing complex Elementor form functionality on static hosting environments
Validating static site parity after a WordPress migration or 'bake' process

About

Key Features

Comprehensive network analysis to identify failed assets and 404 errors
Side-by-side visual comparison using browser automation screenshots
Direct integration with Linear for automated issue tracking and bug reporting
WordPress-specific validation for lazy-loaded images and FontAwesome icons
Automatic sitemap discovery to ensure all site pages are audited
12 GitHub stars

Use Cases

Regression testing for static deployments to catch missing CSS background images
Auditing complex Elementor form functionality on static hosting environments
Validating static site parity after a WordPress migration or 'bake' process