woocommerce-dev-cycle
Manages the WooCommerce development lifecycle by automating testing, linting, and internationalization tasks.
Install
mkdir -p .claude/skills/woocommerce-dev-cycle && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2039" && unzip -o skill.zip -d .claude/skills/woocommerce-dev-cycle && rm skill.zipInstalls to .claude/skills/woocommerce-dev-cycle
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow.Key capabilities
- →Execute PHP and JavaScript test suites
- →Perform PHP linting and style fixes
- →Verify JS/TS internationalization patterns
- →Validate markdown formatting
How it works
The skill provides a set of pnpm commands to run tests, lint code, and check internationalization patterns within the WooCommerce development environment.
Inputs & outputs
When to use woocommerce-dev-cycle
- →Execute PHP/JS test suites
- →Fix PHP linting errors
- →Verify translatable string patterns
- →Validate code style before commit
About this skill
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:
- 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/WooCommerce setup automatically
When not to use it
- →When working outside of the WooCommerce environment
Limitations
- →Specific to WooCommerce development workflow
How it compares
It standardizes the quality assurance workflow for WooCommerce instead of using generic WordPress testing tools.
Compared to similar skills
woocommerce-dev-cycle side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| woocommerce-dev-cycle (this skill) | 5 | 3mo | No flags | Intermediate |
| woocommerce-email-editor | 3 | 6mo | Review | Advanced |
| woocommerce-backend-dev | 7 | 3mo | No flags | Intermediate |
| payment-integration | 1 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by woocommerce
View all by woocommerce →You might also like
woocommerce-email-editor
woocommerce
Setup and develop the WooCommerce block email editor. Use when working on email templates, transactional emails, or the email editor feature.
woocommerce-backend-dev
woocommerce
Add or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.**
payment-integration
mrgoonie
Integrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
debug-cross-service-auth
J-Akiru5
Use when: diagnosing Supabase JWT handoff failures from Next.js frontend to Laravel backend including headers, CORS, issuer, audience, and secret mismatches.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
nestjs-expert
davila7
Nest.js framework expert specializing in module architecture, dependency injection, middleware, guards, interceptors, testing with Jest/Supertest, TypeORM/Mongoose integration, and Passport.js authentication. Use PROACTIVELY for any Nest.js application issues including architecture decisions, testing strategies, performance optimization, or debugging complex dependency injection problems. If a specialized expert is a better fit, I will recommend switching and stop.