mcpField
W
woocommerce-dev-cycle

woocommerce-dev-cycle

github.com/woocommerceTesting & quality10.6k293 installsUpdated today
Repository

About woocommerce-dev-cycle

A development workflow skill for WooCommerce contributors. It organizes guidance for tests, code quality, PHP linting, JavaScript and TypeScript internationalization, and Markdown checks.

Key features

  1. 01PHP and JavaScript test guidance
  2. 02Code quality and linting procedures
  3. 03PHP lint issue patterns
  4. 04JS/TS i18n guidance
  5. 05Markdown linting guidance

Use cases

  1. 01Run focused WooCommerce tests during development
  2. 02Check branch changes before committing
  3. 03Fix PHP lint issues and i18n patterns

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/woocommerce/woocommerce --skill woocommerce-dev-cycle

After installing, type/woocommerce-dev-cyclein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

code-quality.md
js-i18n-patterns.md
markdown-linting.md
php-linting-patterns.md
running-tests.md

Details

From the project README

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 for PHP and JavaScript test commands, test environment setup, and troubleshooting
  2. Code quality: See code-quality.md for linting, code style fixes, and the lockfile procedure for dependency changes
  3. PHP linting patterns: See php-linting-patterns.md for common PHP linting issues and fixes
  4. JS/TS i18n patterns: See js-i18n-patterns.md for translatable string patterns and placeholder usage
  5. Markdown linting: See 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: pnpm --filter=@woocommerce/plugin-woocommerce lint:changes:branch (PHP and JS, the command CI's Lint job runs; git add new files first, since untracked files are skipped; for a PR that does not target trunk, append its fetched base, such as origin/release/X.Y)
  4. Fix any issues: PHP with pnpm --filter=@woocommerce/plugin-woocommerce lint:php:fix; there is no branch fixer for JS, so fix JS by hand (see code-quality.md)
  5. Commit changes only after tests pass

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

Comments

Markdown supported