Skills woocommerce-dev-cycle

📦

woocommerce-dev-cycle

Name: woocommerce-dev-cycle
Author: woocommerce

Content revision r2 Safe 🌐 Network access⚙️ External commands

Streamline WooCommerce Development Checks

WooCommerce contributors need project-specific commands for testing and code quality. This skill provides focused workflows for tests, linting, formatting, and troubleshooting.

Supports: Claude Codex Code(CC)

🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "woocommerce-dev-cycle" from https://skillstore.io/skills/woocommerce-woocommerce-dev-cycle.md and its manifest at https://skillstore.io/api/skills/woocommerce-woocommerce-dev-cycle/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/woocommerce-woocommerce-dev-cycle.md Signed manifest GET /api/skills/woocommerce-woocommerce-dev-cycle/manifest Signed lockfile GET /api/skills/woocommerce-woocommerce-dev-cycle/lockfile

Test it

Using "woocommerce-dev-cycle". I changed one payment test class. What should I run?

Expected outcome:

Run the PHP test environment with a filter for the changed class.
Run branch-scoped PHP linting after the test passes.
Review automatic fixes and rerun the focused test before committing.

Using "woocommerce-dev-cycle". My translated React string contains a link and a brand name.

Expected outcome:

Use a placeholder for the brand name.
Use an interpolated element for the link.
Add a translator comment directly before the translation call.
Run ESLint only on the relevant file.

Using "woocommerce-dev-cycle". Markdown linting reports fence and line-length errors.

Expected outcome:

Run the repository-configured automatic fix first. Then add language labels, wrap prose, verify spacing, and rerun the targeted check.

Security Audit

Safe

v9 • 7/24/2026 Open versioned report

All 19 static findings are false positives caused by documentation examples, ordinary identifiers, or Markdown command formatting. No semantic evidence of prompt injection, data exfiltration, or malicious intent was found.

Files scanned

1,379

Lines analyzed

Review items

False positives ignored

Risk Factors

🌐 Network access (1)

js-i18n-patterns.md:207

⚙️ External commands (3)

SKILL.md:25 SKILL.md:26 SKILL.md:27

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/woocommerce-woocommerce-dev-cycle/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/woocommerce-woocommerce-dev-cycle/security.svg)](https://skillstore.io/skills/woocommerce-woocommerce-dev-cycle?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/woocommerce-woocommerce-dev-cycle?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/woocommerce-woocommerce-dev-cycle/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/woocommerce-woocommerce-dev-cycle.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

woocommerce. (2026). woocommerce-dev-cycle security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/woocommerce-woocommerce-dev-cycle/audits/9

BibTeX citation

@techreport{woocommerce-woocommerce-woocommerce-dev-cycle-2026,
  author = {woocommerce},
  title = {woocommerce-dev-cycle security audit report (audit version 9)},
  institution = {Skillstore},
  year = {2026},
  number = {9},
  url = {https://skillstore.io/skills/woocommerce-woocommerce-dev-cycle/audits/9},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "woocommerce-dev-cycle security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
  - name: "woocommerce"
date-released: "2026-07-24"
url: "https://skillstore.io/skills/woocommerce-woocommerce-dev-cycle/audits/9"
identifiers:
  - type: other
    value: "skillstore:woocommerce-woocommerce-dev-cycle:audit:9"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Validate a PHP change

Choose focused unit tests, run branch-level PHP linting, and review failures before committing.

Check localized interface text

Review placeholders, plural forms, translator comments, linked text, and relevant JavaScript lint commands.

Prepare documentation updates

Run repository-aware Markdown checks and fix code fences, line length, spacing, and encoding issues.

Try These Prompts

Run one PHP test

Show the command to run the WooCommerce PHP test class [class name]. Explain how to read a failure.

Check changed files

Create a WooCommerce quality check sequence for my changed [PHP or JavaScript] files. Include tests, branch-scoped linting, and review steps.

Fix localization lint errors

Review this localization issue: [error and surrounding text]. Recommend the correct placeholders, translator comments, plural handling, and targeted lint command.

Diagnose a failing development cycle

Analyze this WooCommerce test and lint output: [output]. Separate root causes, propose focused commands, and order fixes to minimize unrelated changes.

Best Practices

Run the smallest relevant test set during development, then broaden validation before committing.
Use branch-scoped or file-specific lint commands to avoid unrelated changes.
Review every automatic fix and rerun affected tests and checks.

Avoid

Do not lint the entire repository when only branch changes require validation.
Do not commit automatic formatting changes without reviewing the diff.
Do not hardcode translatable brand names or interpolate variables without translator context.