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 li
Install
npx skills add jdevalk/skills --skill wp-github-actionsgit 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-actionsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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: 1. **Code quality** — WPCS/PHPCS checks, PHP linting, JS/CSS linting 2. **Testing** — PHPUnit with WordPress test library 3. **Static analysis** — PHPStan with WordPress extensions 4. **Dependency management** — Composer diff on PRs, security scanning 5. **Preview** — WordPress Playground PR previews 6. **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.
Details
- Skill name
wp-github-actions- Repository
- jdevalk/skills
- Path
wp-github-actions/SKILL.md- License
- MIT
- Repo updated
- 5 July 2026
FAQ
What does the Wp Github Actions skill do?
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 li
How do I install the Wp Github Actions skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jdevalk/skills --skill wp-github-actions. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Wp Github Actions popular?
It lives in jdevalk/skills, which has 110 GitHub stars and 10 forks.
Related skills
Emdash Github Actions
110jdevalk/skills
Sets up GitHub Actions CI/CD workflows for EmDash plugins — TypeScript type-checking, ESLint linting, Vitest testing, npm publishing, and automated releases. 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 an EmDash plugin — even if they don't use the exact phrase "GitHub Actions". This includes any request to: add automated type-checking or linting to an EmDash plugin repo; set up testing in CI for a plugin; auto-publish a plugin to npm from GitHub; add security scanning or dependency auditing to
Astro Github Actions
110jdevalk/skills
Sets up GitHub Actions CI/CD workflows for Astro sites — `astro check` (TypeScript + content schema), ESLint, Prettier, build verification, Vitest testing, Lighthouse CI, link checking, npm audit, and automated deployment to GitHub Pages, Cloudflare Pages, Netlify, or Vercel. 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 an Astro site — even if they don't use the exact phrase "GitHub Actions". This includes any request to: add automated type-checking or linting to an Astro repo; set up `astro ch
Astro SEO
110jdevalk/skills
Audits and improves SEO for Astro sites. Use when the user asks to audit, set up, or improve SEO on an Astro site, or mentions head metadata, structured data, JSON-LD, sitemaps, IndexNow, Open Graph images, schema endpoints, NLWeb, hreflang, or search engine indexing in an Astro project. Produces drop-in code routed through `@jdevalk/astro-seo-graph` and chains into `metadata-check` for generated SEO strings.
Concord Policy Audit
116CALLE-AI/awesome-phone-call-agents
Audit what your own branches tell callers by phone, judge each answer against written policy, and return a branch-level gap register that is deliberately unusable as a staff performance record.
Github Repo
110jdevalk/skills
Audits and improves GitHub repository quality — README structure, community health files, .github directory setup, issue/PR templates, metadata, releases, and branch hygiene. Use this skill whenever the user asks to improve, audit, review, or set up a GitHub repository, or when they mention things like "make my repo look professional", "add contributing guidelines", "set up issue templates", "improve my README", "clean up my repo", "prepare my repo for open source", or "make my GitHub project look good". Also trigger when working inside a git repository and the user asks about best practices f
App Store Changelog
213TerminalSkills/skills
Writes the App Store "What's New in This Version" text for an app update from the repository's commit history: finds the range since the last shipped version, separates changes users can notice from internal work, drafts plain-text notes within Apple's 4,000-character limit and review guidelines, and returns a trace from every sentence back to its commits. Use when someone asks to "write release notes for the App Store", "generate What's New from git", "summarize changes since the last tag for the store listing", or needs the same notes cut to Google Play's 500 characters.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.