Smithery Logo
MCPsSkillsDocsPricing
Login
Smithery Logo

Accelerating the Agent Economy

Resources

DocumentationPrivacy PolicySystem Status

Company

PricingAboutBlog

Connect

© 2026 Smithery. All rights reserved.

    Microck

    woocommerce-dev-cycle

    Microck/woocommerce-dev-cycle
    DevOps
    116
    1 installs

    About

    SKILL.md

    Install

    Install via Skills CLI

    or add to your agent
    • Claude Code
      Claude Code
    • Codex
      Codex
    • OpenClaw
      OpenClaw
    • Cursor
      Cursor
    • Amp
      Amp
    • GitHub Copilot
      GitHub Copilot
    • Gemini CLI
      Gemini CLI
    • Kilo Code
      Kilo Code
    • Junie
      Junie
    • Replit
      Replit
    • Windsurf
      Windsurf
    • Cline
      Cline
    • Continue
      Continue
    • OpenCode
      OpenCode
    • OpenHands
      OpenHands
    • Roo Code
      Roo Code
    • Augment
      Augment
    • Goose
      Goose
    • Trae
      Trae
    • Zencoder
      Zencoder
    • Antigravity
      Antigravity
    ├─
    ├─
    └─

    About

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

    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 for PHP and JavaScript test commands, test environment setup, and troubleshooting
    2. Code quality: See code-quality.md for linting and code style fixes
    3. PHP linting patterns: See php-linting-patterns.md for common PHP linting issues and fixes
    4. Markdown linting: See 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
    Recommended Servers
    vastlint - IAB XML VAST validator and linter
    vastlint - IAB XML VAST validator and linter
    PostHog
    PostHog
    Vercel Grep
    Vercel Grep
    Repository
    microck/ordinary-claude-skills
    Files