woocommerce-dev-cycle

woocommerce's avatarfrom woocommerce

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

⭐10.1kstars🔀10.7kforks📁View on GitHub🕐Updated Nov 25, 2025
[Testing and QA]

When & Why to Use This Skill

The WooCommerce Development Cycle skill is a specialized toolkit designed to streamline the development and quality assurance process for WooCommerce projects. It provides a structured workflow for running PHP and JavaScript tests, enforcing code style through linting, and ensuring internationalization (i18n) compliance. By automating these quality checks, it helps developers maintain high code standards, reduce bugs, and follow official development best practices efficiently.

Use Cases

  • 1. Automated Testing: Quickly execute PHP and JavaScript test suites (e.g., using pnpm) to verify that new code changes haven't introduced regressions.
  • 2. Code Quality Enforcement: Automatically run linting tools to identify and fix code style issues in PHP, JavaScript, and Markdown files to ensure project consistency.
  • 3. Internationalization (i18n) Checks: Validate JS/TS files for correct translatable string patterns and placeholder usage, ensuring the plugin remains translation-ready.
  • 4. Standardized Development Workflow: Guide developers through the complete cycle of making changes, testing, linting, and committing to ensure a high-quality codebase.
namewoocommerce-dev-cycle
descriptionRun tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow.

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 and code style fixes
  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/type checking: pnpm run lint:changes:branch:php
  4. Fix any issues: pnpm run lint:php:fix
  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