wordpress-theme-auto-update

Automate WordPress theme releases and updates via GitHub Actions and Cloudflare R2.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/hifisaputra/wordpress-skills --skill wordpress-theme-auto-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wordpress-theme-auto-update
Source: https://github.com/hifisaputra/wordpress-skills/tree/main/wordpress-theme-auto-update
Command: npx skills add https://github.com/hifisaputra/wordpress-skills --skill wordpress-theme-auto-update

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Automates the end-to-end release and in-theme update flow for a WordPress theme, enabling a GitHub Actions-driven deployment to Cloudflare R2 and a PHP updater that signals WordPress to surface new versions in the Update screen.

Core Features & Use Cases

  • Automated release pipeline: on push to main reads Version from style.css, builds a ZIP of the theme, and uploads both the ZIP and an info.json to Cloudflare R2.
  • In-theme updater: inc/updater.php fetches info.json from R2, caches it, and injects updates into WordPress so users see an "Update Now" option.
  • Wiring & secrets guidance: provides guidance for editing functions.php, configuring repository secrets (R2 keys, bucket, public URL), and validating Theme URI and Version headers.
  • Use Case: bootstrap a new custom theme and publish it to multiple client sites with a single release process.

Quick Start

Follow the prompts to configure R2, bump Version in style.css, and push to main to trigger the release workflow.

Frequently Asked Questions about wordpress-theme-auto-update

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

FAQPage Schema
How do I auto-update a custom WordPress theme using GitHub Actions and Cloudflare R2?

You can auto-update a custom WordPress theme by using GitHub Actions to deploy versioned ZIP files and an info.json manifest to Cloudflare R2, which an in-theme PHP updater then fetches to surface new versions in the WordPress dashboard.

How does an in-theme updater inject update notifications into WordPress?

An in-theme updater fetches a remote info.json file from Cloudflare R2, caches it locally, and hooks into WordPress update mechanisms to compare versions and display the Update Now option in the dashboard.

Do I need to configure repository secrets to deploy WordPress themes to Cloudflare R2?

Yes, you must configure GitHub repository secrets for your Cloudflare R2 access keys, bucket name, and public URL to authenticate the deployment workflow and securely host the theme ZIP and info.json files.

What is the best way to manage WordPress theme releases for multiple client sites?

The best way to manage theme releases across multiple client sites is a centralized release pipeline that bumps the Version header in style.css, builds a ZIP via GitHub Actions, and serves it from Cloudflare R2.

How does the release pipeline determine the new version of a WordPress theme?

The release pipeline determines the new version by reading the Version header directly from the theme's style.css file during the GitHub Actions build process when a push to main is triggered.

What limitations exist when using GitHub Actions to deploy WordPress themes to R2?

This deployment approach requires correctly validating the Theme URI and Version headers in style.css and properly editing functions.php to include the updater, or the WordPress update screen will fail to display new versions.