shopsys

Shopsys commit conventions — atomic functional units (tests with code, lockfiles and migrations with their cause), message format (lowercase, no period, present tense for behaviour / past tense for code changes, area and ClassName prefixes, no "fix:", never…

Interactive commit workflow — analyzes all uncommitted changes, proposes atomic, logically grouped commits with messages following commit-conventions, and executes them only after the user approves the groups. Use when the user asks to commit their current…

Triage of a failed nightly verification run — fix-first. Diagnoses every failed target and attempts a fix for each real failure: deterministic fixers run inside the failing run's own CI images take precedence in their domain; everything else gets a minimal…

Coding principles and conventions for the Shopsys monorepo — DRY/KISS/reuse, comment and docblock quality, test-code rules, the per-folder visibility/typing rules (packages vs project-base vs utils), and documentation best practices. Read it before writing or…

This skill MUST be used when the user asks to write tests, add tests, create test cases, run/execute/re-run/debug tests, test a specific class or method, or when working on any *Test.php file in this Shopsys application. Applies codebase-specific best…

This skill MUST be used when the user asks to write tests, add tests, create test cases, run/execute/re-run/debug tests, test a specific class or method, or when working on any *Test.php file in this Shopsys application. Applies codebase-specific best…

Finishes a failed coding-standards check: the pipeline has already run `phing standards-fix`, so this fixes by hand what the fixer could not (phpstan, phplint, twig-lint, leftover ecs), then packages everything as fixup! commits targeting the PR commits that…

Fixes the violations reported by a failed coding-standards check (ecs, phpstan, phplint, twig-lint, markdown, yaml, eslint) by editing the source directly from the check's log, then packages the fixes as fixup! commits targeting the commits that introduced…

Fan-out code review of multiple/all open PRs - one parallel worktree-isolated agent per PR, each following the review-pr skill protocol, then cross-PR verification, cleanup and summary. Use when asked to review all open PRs or several PRs at once; a single PR…

Detailed code review of ONE pull request - scope vs its (possibly stacked) base, verification-first findings (render + tests + web research), posting a GitHub review with anchored inline comments signed "Claude Agent (CR)". Use when asked to review a specific…

Conventions for creating GitHub issues in this repository - body structure, title prefixes, the label taxonomy and cross-linking rules. Use whenever filing new issues or turning analysis/review findings into backlog items.

Diagnosing a failed deploy on a real cluster - identifying which phase failed from the end states, where the logs are, recovery commands, and what must NOT be done. Use when a helmfile/wrapper deploy fails or behaves unexpectedly.

Helm and Kubernetes best practices plus this repository's hard-won gotchas (template pitfalls, hook lifecycle, secrets patterns, determinism rules). Read BEFORE writing or modifying any chart template, values file or hook.

Lifecycle of implementing a backlog issue - triage, scope decisions, the PR flow and the closing retrospective comment. Use when asked to implement an issue from the tracker.

End-to-end workflow for preparing a pull request in this repository - branching, implementation checklist, the full verification suite, commit/PR conventions and stacked-PR handling. Use whenever implementing an issue or any change that will become a PR.

Porting changes from the legacy shopsys/deployment package (upstream PRs, manifest fixes) into these charts. Use when asked to review/port upstream deployment PRs or to check what changed upstream.

Use PROACTIVELY when you investigate, analyze, debug, or review performance issues using Blackfire.io profiles. Triggers on: 'blackfire profile', 'performance analysis', 'investigate slow', 'profile URL', app.blackfire.io URLs, slow requests, high CPU/IO, N+1…

Use PROACTIVELY when you implement, review, audit, debug, or optimize bulk operations (imports, mass edits, variant creation, batch updates) in Doctrine/Shopsys codebases. Triggers on: slow batch operations, 'Doctrine CPU spiral', N+1 queries in loops,…