smithery/microck

woocommerce-dev-cycle

Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow.

Installation

$ npx skills add smithery/microck --skill woocommerce-dev-cycle

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/microck · top by installs.

npx skills add smithery/microck

Browse all from smithery/microck

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,591 B
  • docs SUMMARY.md 178 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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