| name | poocommerce-dev-cycle |
| description | Run tests, linting, and quality checks for PooCommerce development. Use when running tests, fixing code style, or following the development workflow. |
PooCommerce Development Cycle
This skill provides guidance for the PooCommerce development workflow, including running tests, code quality checks, and troubleshooting.
Instructions
Follow these guidelines for PooCommerce 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
- JS/TS i18n patterns: See js-i18n-patterns.md for translatable string patterns and placeholder usage
- 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
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/PooCommerce setup automatically
