multiAI Summary Pending
woocommerce-dev-cycle
Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow.
231 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/woocommerce-dev-cycle/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/woocommerce/woocommerce-dev-cycle/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/woocommerce-dev-cycle/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How woocommerce-dev-cycle Compares
| Feature / Agent | woocommerce-dev-cycle | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 ## 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