Receber por email
← Voltar para o catálogo

woocommerce-dev-cycle

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

239estrelas
Atualizado há 6 meses

Ver no GitHub ↗ Licença: NOASSERTION

Como adicionar

/plugin marketplace add Microck/ordinary-claude-skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/woocommerce-dev-cycle/svg)](https://www.skillteca.com.br/skills/woocommerce-dev-cycle)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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
Compartilhar X LinkedIn