forge

Name: forge
Availability: InStock
Author: nanathan13

Execute WordPress Gutenberg plans and verify UI states via Playwright.

Updated May 5, 2026

Search Tags:#automation #workflow #qa #playwright #wordpress #gutenberg

Ready to run

npx skills add https://github.com/NaNathan13/cool-fse-claude-workflow --skill forge-nanathan13

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: forge
Source: https://github.com/NaNathan13/cool-fse-claude-workflow/tree/main/kit/.claude/skills/forge
Command: npx skills add https://github.com/NaNathan13/cool-fse-claude-workflow --skill forge-nanathan13

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of loading, executing, and verifying plans within the cool-fse WordPress workflow, reducing manual oversight and ensuring consistency.

Core Features & Use Cases

Load and execute plans: Reads plans from .claude/plans/active/ and runs UI verification through Playwright.
Workflow orchestration: Confirms plan status, surfaces blockers, verifies dev server availability, and scripts the build steps.
Use Case: A developer wants to automate the testing of a new Gutenberg block by loading the relevant plan, executing it, capturing screenshots, and verifying the site stability.

Quick Start

Use the forge skill to load and run the current plan, then verify the UI states as specified in the plan.

Frequently Asked Questions about forge

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

FAQPage Schema

How do I automate WordPress Gutenberg block testing and plan execution?▼

Automate WordPress Gutenberg block testing by loading execution plans from `.claude/plans/active/` and running UI verification through Playwright to capture screenshots and confirm site stability. This workflow reduces manual oversight and ensures consistent plan adherence.

What is automated workflow orchestration for WordPress theme updates?▼

Automated workflow orchestration for WordPress theme updates is the process of confirming plan status, surfacing blockers, verifying dev server availability, and scripting build steps. It ensures consistent adherence to project plans and prevents missed steps during complex block or theme deployments.

Does this automation workflow require Playwright for UI verification?▼

Yes, this automation workflow requires Playwright for UI verification. It uses Playwright to execute UI verification steps specified in the loaded plan, capture screenshots of Gutenberg blocks, and verify that the site remains stable throughout the deployment process.

Can I use this workflow to manage QA validation for complex WordPress deployments?▼

Yes, you can use this workflow to manage QA validation for complex WordPress deployments. It is designed for developers and QA teams managing complex theme or block updates, providing step-by-step validation to prevent missed steps and errors during deployment.

How do I load and execute a development plan from the active directory?▼

Load and execute a development plan by reading files from the `.claude/plans/active/` directory. The workflow confirms the plan status, surfaces any blockers, verifies dev server availability, and scripts the necessary build steps to run the plan automatically.

What are the limitations of automating UI verification for Gutenberg development?▼

Limitations of automating UI verification for Gutenberg development include dependency on a running dev server and properly formatted plans in `.claude/plans/active/`. The workflow cannot execute if the dev server is unavailable or if the plan structure is missing required verification steps.