Skip to main content
skill CX Codex

woocommerce-dev-cycle — Claude Code skill for WooCommerce tests

A skill that walks you through the WooCommerce dev cycle: run tests, fix code style, sort out linting errors.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add secondsky/claude-skills --skill woocommerce-dev-cycle -a claude-code
Open on GitHub

What woocommerce-dev-cycle does

The skill lays out the WooCommerce development workflow and points to four reference files: running-tests.md for PHP and JavaScript test commands, code-quality.md for linting and style fixes, php-linting-patterns.md for common PHP issues, and markdown-linting.md for markdown files.

The loop is short. Make your changes, run the relevant tests with pnpm run test:php:env -- --filter YourTestClass, then pnpm run lint:changes:branch:php, and fix what comes up via pnpm run lint:php:fix. Commit only once tests pass. WooCommerce builds with pnpm; for other Node.js projects the skill suggests bun over npm or pnpm.

Linting covers only the code in your current branch, so unrelated warnings stay out of the report. The test environment sets up WordPress and WooCommerce on its own.

What it helps with

  • run a single PHP test by class name
  • clean up code style before committing
  • work out why PHP linting fails
  • format markdown files in the repo
  • see expected versus actual values in a failing test

Example prompts for the agent

  • run the tests for my class with pnpm run test:php:env -- --filter MyTestClass
  • lint the changes on my branch and show me what to fix
  • fix the PHP style errors with pnpm run lint:php:fix

How to install woocommerce-dev-cycle

1Skills CLI (Vercel)

npx skills add secondsky/claude-skills --skill woocommerce-dev-cycle -a claude-code

2Manually: put the files in place

~/.claude/skills/woocommerce-dev-cycle/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/woocommerce-dev-cycle/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about woocommerce-dev-cycle

How do I install woocommerce-dev-cycle in Claude?

Run npx skills add secondsky/claude-skills --skill woocommerce-dev-cycle -a claude-code. The skill lands at ~/.claude/skills/woocommerce-dev-cycle/SKILL.md.

What does woocommerce-dev-cycle do?

It guides you through the WooCommerce workflow: PHP and JavaScript tests, linting and style fixes, plus common PHP and markdown linting problems.

Do I need to set up WordPress and WooCommerce for tests?

No, the test environment handles that setup automatically. Linting, meanwhile, only checks code in your current branch.

Source text

SKILL.md · MIT
---
name: woocommerce-dev-cycle
description: Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow in WooCommerce projects.
license: MIT
---

# WooCommerce Development Cycle

This skill provides guidance for the WooCommerce development workflow, including running tests, code quality checks, and troubleshooting.

## Instructions

Follow these guidelines for WooCommerce development workflow:

1. **Running tests**: See [running-tests.md](running-tests.md) for PHP and JavaScript test commands, test environment setup, and troubleshooting
2. **Code quality**: See [code-quality.md](code-quality.md) for linting and code style fixes
3. **PHP linting patterns**: See [php-linting-patterns.md](php-linting-patterns.md) for common PHP linting issues and fixes
4. **Markdown linting**: See [markdown-linting.md](markdown-linting.md) for markdown file linting and formatting

## Development Workflow

The standard development workflow:

1. Make code changes
2. Run relevant tests: `pnpm run test:php:env -- --filter YourTestClass`
3. Run linting/type checking: `pnpm run lint:changes:branch:php`
4. Fix any issues: `pnpm run lint:php:fix`
5. Commit changes only after tests pass

**Note**: WooCommerce uses pnpm for its build system. For other Node.js projects, prefer bun over npm/pnpm.

## Key Principles

- Always run tests after making changes to verify functionality
- Use specific test filters to run relevant tests during development
- Fix linting errors solely for code in your current branch
- Test failures provide detailed output showing expected vs actual values
- The test environment handles WordPress/WooCommerce setup automatically

© secondsky · MIT · secondsky/claude-skills

Similar skills

Everything for Testing and QA →

From the same set89

cloudflare-agents A skill for building AI agents on Cloudflare Workers with tools, MCP and LLM providers. Useful when the agent runs inside a worker. CX Codex +1 378installs cloudflare-mcp-server A skill for building MCP servers on Cloudflare Workers: tools, resources, prompts and transport choices. Useful when you write your own server for an AI agent. CX Codex +1 375installs thesys-generative-ui A skill that teaches your agent to build React components from plain-language prompts with the Thesys SDK. Handy when you want a UI sketched out from a description. CX Codex +1 371installs maz-ui This skill teaches your agent Maz-UI v4: 50+ components, composables and directives for Vue 3 and Nuxt 3. Handy when you build forms, dialogs or data tables. CX Codex +1 369installs woocommerce-copy-guidelines A skill that sets the rules for user-facing text in WooCommerce: button labels, field names, messages and docs. Useful when more than one person writes the storefront strings. CX Codex +1 363installs cloudflare-workers-testing A skill for writing Cloudflare Workers tests with Vitest and real D1, KV, R2 and Durable Objects bindings. Useful when tests break on mocks or can't see the environment. CX Codex +1 325installs nuxt-seo A skill covering the eight Nuxt SEO v5 modules: robots.txt, sitemaps, OG images, Schema.org and meta tags. Useful when a Nuxt app needs SEO wired up. CX Codex +1 324installs cloudflare-workers-performance A Claude skill for Cloudflare Workers performance: CPU, memory, caching, bundle size. Useful when a worker is slow or hitting limits. CX Codex +1 315installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor