woocommerce-dev-cycle
This skill provides guidance for the WooCommerce development workflow, including running tests, performing code quality checks, and troubleshooting to ensure code changes are properly validated and follow project standards.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install secondsky-claude-skills-woocommerce-dev-cycle
Repository
Skill path: plugins/woocommerce-dev-cycle/skills/woocommerce-dev-cycle
This skill provides guidance for the WooCommerce development workflow, including running tests, performing code quality checks, and troubleshooting to ensure code changes are properly validated and follow project standards.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack, Testing.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: secondsky.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install woocommerce-dev-cycle into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/secondsky/claude-skills before adding woocommerce-dev-cycle to shared team environments
- Use woocommerce-dev-cycle for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
--- 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. --- # 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