woocommerce-dev-cycle — quality + safety report
In the Skillier index (secondsky__woocommerce-dev-cycle) · scanned 2026-06-03 · engine: builtin+triage
✓ Clean — no heuristic safety flags surfaced.
Heuristic flags from the builtin scanner, which is known to over-flag (it trips on legitimate env-reading integrations, security skills, and library .eval calls). This is NOT an authoritative malicious verdict — re-scan with SkillSpector for the authoritative result. Run the authoritative scan →
📇 This skill is in the Skillier index (curated · deduped · quality-filtered). Install Skillier to route & load it into your AI client.
Quality notes
About 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.
📄 Read the 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 **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
Want a live grade + an embeddable README badge? Run your skill through the free scanner.
Graded independently by Skillproof — nothing to sell the author. Quality is mechanical + corpus-grounded; safety flags are heuristic (builtin+triage), not a malicious verdict.