mcpbeat

Woocommerce Dev Cycle

secondsky/woocommerce-dev-cycle

Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow in WooCommerce projects.

434 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
202
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/secondsky/claude-skills --skill woocommerce-dev-cycle

The instruction itself

4 sections, as written by the author

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:

  • Running tests: See running-tests.md for PHP and JavaScript test commands, test environment setup, and troubleshooting
  • Code quality: See code-quality.md for linting and code style fixes
  • PHP linting patterns: See php-linting-patterns.md for common PHP linting issues and fixes
  • Markdown linting: See markdown-linting.md for markdown file linting and formatting

Development Workflow

The standard development workflow:

  • Make code changes
  • Run relevant tests: pnpm run test:php:env -- --filter YourTestClass
  • Run linting/type checking: pnpm run lint:changes:branch:php
  • Fix any issues: pnpm run lint:php:fix
  • 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

How to use it

Copy the folder

Take secondsky/woocommerce-dev-cycle from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.