shopware

Triage a failing Shopware nightly / multi-job PHPUnit CI run (e.g. integration-major). Extract every failing test from the run's job logs, resolve each to its owning domain via #[Package] markers, cluster failures by error signature into root causes, verify opaque clusters with a local Docker reproduction, then file one GitHub issue per domain plus a parent tracking issue — routing collateral failures to the root-cause owner. Use when the user links a failing Actions run or job, asks to "identify all failing tests" from a nightly, asks to triage integration-major / a red nightly, or wants CI failures grouped into per-team issues.

Diagnose and fix a Shopware 6 GitHub issue, or improve an existing Bugfixer pull request after maintainer feedback. Use when the user asks to fix an issue, create a bugfix PR, handle a qi/sw-bugfixer issue, improve a Bugfixer PR, or react to /sw-bugfixer feedback.

Review a Shopware 6 GitHub pull request or local diff. Use when the user asks to review a PR, references a PR by number ("#16638"), asks for a focused security / architecture / code-style / UX / open-source review, or when a PR needs automated reviewer feedback.

Triage a Shopware 6 GitHub bug issue. Read the issue body, identify the affected code area via rg/git/gh, check for related fixes or duplicates, then emit a Markdown summary with disposition, severity, suggested domain labels, confidence, reasoning, and supporting evidence. Use when the user asks to triage, classify, label, or assess a Shopware issue, when they reference an issue by number (e.g. "#16599"), or when a new issue arrives that needs an initial dispositioning.

Apply Shopware PHP/server-side coding guidance. Use when editing PHP under src/Core, src/Administration, or src/Storefront — including migrations, API schema, deprecations, or BC-sensitive code.

Apply Shopware Administration JS/TS/Vue coding rules. Use when editing Admin UI code (.js/.ts/.vue) under src/Administration, including Jest specs and ACL-backed components.

Scope Shopware bug fixes, cleanups, and behavioral changes. Use when fixing an issue, applying review feedback, deciding whether to broaden a cleanup, or checking that the change addresses the root cause instead of one symptom.

Preserve Shopware knowledge for later. Use when the user asks to save, remember, preserve, document, or store information, rules, lessons learned, workflow knowledge, coding guidance, or agent instructions for future humans or agents.

Write or update Shopware PHPUnit tests. Use when adding or changing tests under tests/ (unit, integration, migration, BC) — including data providers, feature flags, and coverage annotations.

Prepare or update Shopware pull requests. Use when writing or editing a PR description or PR text (incl. "output a PR description"), choosing a PR title, responding to review feedback, or updating a PR after CI failures.

Decide and write Shopware developer-facing release documentation (RELEASE_INFO / UPGRADE / changelog entries). Use when a change may affect extension authors, API consumers, operators, or storefront/theme developers — public APIs, deprecations, removals, configuration, or upgrade steps.