Wp Github Actions

Community

jdevalk

wp-github-actions

Sets up GitHub Actions CI/CD workflows for WordPress plugins — coding standards (WPCS/PHPCS), PHP/JS/CSS linting, PHPUnit testing, static analysis (PHPStan), Composer security scanning, WordPress Playground PR previews, and automated deployment to WordPress.org. ALWAYS use this skill when a user wants to create, add, set up, or configure GitHub Actions, CI/CD, automated checks, or deployment workflows for a WordPress plugin — even if they don't use the exact phrase "GitHub Actions". This includes any request to: add automated coding standards or PHPCS/WPCS checks to a WP plugin repo; set up linting (PHP, JS, CSS) for a WordPress plugin; configure PHPUnit testing in CI for a plugin; auto-deploy a plugin to WordPress.org from GitHub; add Playground previews to pull requests; add security scanning or static analysis to a plugin pipeline; or generally "add CI", "add automated checks", "set up workflows", or "automate" anything related to a WordPress plugin's GitHub repository. Also trigger when someone mentions wanting to stop doing manual SVN deploys, wants quality gates on PRs, or is setting up a new WordPress plugin repo and wants best practices for automation. If the user is inside a WordPress plugin repository and mentions anything about automated testing, code quality, deployment, or GitHub workflows, use this skill.

Overview

Publisher	jdevalk
Repository	`skills`
Skill name	`wp-github-actions`
Stars	109
Forks	10
Bundled files	2
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by jdevalk on GitHub. Read the source before you install it.

Installation

Install the Wp Github Actions AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/jdevalk/skills/tree/main/wp-github-actions
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/jdevalk/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/wp-github-actions .claude/skills/wp-github-actions

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Wp Github Actions in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Wp Github Actions on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Wp Github Actions is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

WordPress Plugin GitHub Actions

This skill helps you set up a comprehensive CI/CD pipeline for WordPress plugins using GitHub Actions. The goal is to help plugin authors ship higher-quality code with less manual effort.

What this skill covers

There are several categories of workflows that a healthy WordPress plugin should have. Not every plugin needs all of them — the right mix depends on the plugin's complexity, whether it has JavaScript/CSS assets, whether it uses Composer, etc. Your job is to figure out which ones are relevant and set them up.

The workflows fall into these categories:

Code quality — WPCS/PHPCS checks, PHP linting, JS/CSS linting
Testing — PHPUnit with WordPress test library
Static analysis — PHPStan with WordPress extensions
Dependency management — Composer diff on PRs, security scanning
Preview — WordPress Playground PR previews
Deployment — Automated deploy to WordPress.org on tag/release

Read references/workflows.md for the detailed configuration of each workflow, including ready-to-use YAML templates and configuration files.

How to approach a request

Step 1: Understand the plugin

Before writing any workflow files, figure out what you're working with:

Does the plugin use Composer? Check for composer.json. If yes, Composer-related workflows (diff, security, autoloading) are relevant.
Does it have JavaScript/CSS assets? Check for package.json, any JS/CSS source files, or a build process. If yes, JS/CSS linting and possibly a build step matter.
Does it have tests? Check for a tests/ directory, phpunit.xml, or phpunit.xml.dist. If yes, set up the PHPUnit workflow. If not, mention that adding tests would be valuable but don't force it.
Is it on WordPress.org? Check for a .wordpress-org directory or ask. If yes, the deploy workflow is relevant and you should also set up .distignore.
What PHP versions should it support? WordPress itself requires PHP 7.4+, but many plugins target 7.4, 8.0, 8.1, 8.2, and 8.3. Check the plugin's readme or ask.
What WordPress versions? Similarly, check what WP versions the plugin declares compatibility with.

Step 2: Recommend a set of workflows

Based on what you found, recommend which workflows to set up. A good default for most plugins:

WPCS check (almost always)
PHP lint (almost always — catches syntax errors across PHP versions)
PHPUnit tests (if tests exist)
Deploy to WordPress.org (if on WordPress.org)
Playground PR preview (nice to have for any plugin)

And conditionally:

JS/CSS linting (if the plugin has frontend assets)
Composer diff + security (if using Composer)
PHPStan (for plugins that want deeper static analysis)

Step 3: Create the workflow files

Create each workflow as a separate YAML file in .github/workflows/. Using separate files rather than one monolithic workflow gives clearer feedback in PRs (each check shows independently) and makes it easier to enable/disable individual checks.

Use the templates from references/workflows.md as starting points, but adapt them to the specific plugin. Common adaptations include adjusting PHP version matrices, changing the WPCS standard, adjusting file paths, and tweaking the deploy workflow for plugins with build steps.

Step 4: Create supporting config files

Depending on which workflows you set up, you may also need:

phpcs.xml.dist — Custom PHPCS ruleset (if the plugin needs rule exclusions or custom config)
.distignore — Files to exclude from WordPress.org deployment
phpstan.neon or phpstan.neon.dist — PHPStan configuration

Step 5: Set up secrets reminder

If you're adding the deploy workflow, remind the user that they need to configure two repository secrets in GitHub:

SVN_USERNAME — Their WordPress.org username
SVN_PASSWORD — Their WordPress.org password

Walk them through: Repository Settings > Secrets and variables > Actions > New repository secret.

Naming conventions

Use descriptive workflow file names that make it obvious what each one does:

wpcs.yml — WordPress Coding Standards
phpunit.yml — PHPUnit tests
lint-php.yml — PHP syntax linting
lint-js-css.yml — JavaScript and CSS linting
phpstan.yml — Static analysis
composer-diff.yml — Composer dependency diff on PRs
security.yml — Composer security scanning
playground-preview.yml — WordPress Playground PR preview
deploy.yml — Deploy to WordPress.org

Important details

Branch naming: Many WordPress plugin repos use trunk as the default branch (mirroring WordPress.org SVN conventions), while others use main or master. Always check the actual repo and use the correct branch name in workflow triggers.

PHP version matrix: WordPress 6.x requires PHP 7.4+. A good default matrix is ['7.4', '8.0', '8.1', '8.2', '8.3'] for PHPUnit, but use only the latest stable PHP for WPCS and linting (they don't need a matrix).

WordPress version matrix: For PHPUnit, test against at least latest and consider adding the previous major version. Some plugins also test against nightly to catch upcoming issues early.

The 10up ecosystem: 10up maintains a set of well-maintained GitHub Actions specifically for WordPress. Prefer these over generic alternatives when they exist — they handle WordPress-specific edge cases well. The key ones are 10up/wpcs-action for coding standards and 10up/action-wordpress-plugin-deploy for deployment.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

evals/evals.json6 KB
references/workflows.md16 KB

Frequently asked questions

What does the Wp Github Actions AI skill do?

Why use Wp Github Actions on TypingMind?

Because you install it once and use it with any model. Wp Github Actions is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Wp Github Actions in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jdevalk/skills/tree/main/wp-github-actions. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Wp Github Actions?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Wp Github Actions?

As many as you like. As long as a model supports skills, you can use Wp Github Actions with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Wp Github Actions AI skill free?

Yes. It is published on GitHub by jdevalk under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Refactor Docs

openclaw

OrganizationPopular

Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.

Openclaw Repair Sweep

openclaw

OrganizationPopular

Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

Openclaw Test Performance

openclaw

OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

Openclaw Testing

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

WordPress Plugin GitHub Actions

What this skill covers

How to approach a request

Step 1: Understand the plugin

Step 2: Recommend a set of workflows

Step 3: Create the workflow files

Step 4: Create supporting config files

Step 5: Set up secrets reminder

Naming conventions

Important details

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now