/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.
One skill from claude-skills.
shell
$ npx -y skills add secondsky/claude-skills --skill woocommerce-dev-cycle --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/woocommerce-dev-cycle
Context preview
The summary Claude sees to decide when to auto-load this skill.
Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow in WooCommerce projects.
Stats
Stars194
Forks29
LanguageTypeScript
LicenseMIT
Ships with claude-skills
SKILL.md
woocommerce-dev-cycle.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. license: MIT --- # 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
