Shopware CLI skill
Official Shopware skills teaching an agent to run shopware-cli on projects and extensions: validation, builds, Docker, Store
- 125 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The skills steer the agent to run a CLI that creates projects, builds extensions and works with a Shopware account.
- Shop URLs and Admin API keys sit in the project config.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/shopware-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The skills steer the agent to run a CLI that creates projects, builds extensions and works with a Shopware account.
- Shop URLs and Admin API keys sit in the project config.
This is third-party code. Review the repository files before installing.
What it does
The `skills/` folder of the Shopware CLI repository holds four official skills. The `shopware-cli` skill walks an agent through the `project`, `extension` and `account` command groups: creating and configuring a project, validating, building, formatting and upgrading extensions, troubleshooting. It tells the agent to check the current `shopware-cli --help` output instead of recalling flags from memory. `shopware-cli-docker` routes commands into the right container and describes the Docker environment lifecycle. `shopware-cli-extension-store` reads an extension, sorts metadata, localization and asset findings against Shopware Store requirements and cites a source for each finding without changing anything. `shopware-cli-extension-anonymize` fills the `anonymize` section of `.config/shopware-extension.yml` so that a `project dump --anonymize` export covers the extension tables and secrets.
Who it is for. Developers of Shopware 6 shops and extensions who hand console routines to an agent.
Good fit when
- A new Shopware project starts from scratch and the agent has to walk through the install wizard.
- An extension is validated before release with json, junit, github or gitlab output for CI.
- Project commands run in Docker and the agent confuses the host with the container.
- Before submitting to Shopware Store you want to see which metadata, localization and asset findings remain.
- A database dump with `--anonymize` misses the tables of your own extension.
Not a fit when
- The project runs on another e-commerce platform.
- You need ready themes and storefront modules: the skills cover console commands only.
- Questions about Shopware core architecture belong to the official documentation, which the skills do not replace.
Example request
Check the extension in `custom/plugins/MyPlugin` for Store readiness and list findings on metadata and translations without changing anything.Limitations
The skills work only together with an installed `shopware-cli`: install the CLI first, for example with `go install github.com/shopware/shopware-cli@latest`, then the skills with `npx skills add shopware/shopware-cli`. The `extension add` generators target Shopware 6.7.13.0 and newer and fail before writing any file on older versions. The shop URL and Admin API access live in `.config/shopware-project.yml`, so keep production environments separate from `local`. The `shopware-cli-extension-store` skill only reads files, the other CLI commands change the project.
How to disable. Remove the `shopware-cli`, `shopware-cli-docker`, `shopware-cli-extension-store` and `shopware-cli-extension-anonymize` skills from the agent skills folder. Remove the CLI and the project configuration separately.
FAQ
How do I install the Shopware CLI skills?
Run `npx skills add shopware/shopware-cli`. The `shopware-cli` binary itself is installed separately, for example with `go install github.com/shopware/shopware-cli@latest`.
Which skills are in the set?
Four: `shopware-cli` for projects, extensions and the account, `shopware-cli-docker` for Docker environments, `shopware-cli-extension-store` for Store readiness and `shopware-cli-extension-anonymize` for dump anonymization settings.
Does the Store check change extension files?
No. The `shopware-cli-extension-store` skill only reads files and cites a re-checkable source for each finding.
What does the anonymization skill do?
It fills the `anonymize` section of `.config/shopware-extension.yml` from the extension tables and system config secrets. After that `project dump --anonymize` includes them in the export.
Does the set work with a Docker-based project?
Yes. The `shopware-cli-docker` skill routes commands into the right container and covers the environment lifecycle and Docker troubleshooting.
Discussion
No questions or reviews yet.
Related
SkillsA Claude Code plugin marketplace for Shopware: PHPStan, PHPUnit, ESLint, test generation and CI failure analysis
181 skills for online stores: payments, catalog, shipping, pricing and security on Shopify, WooCommerce and custom builds.
15 skills for Claude Code and Codex: Laravel, Docker, UI, debugging, tests and docs in four ready plugin bundles
Bagisto Agent Skills: Bagisto development
Bagisto Agent Skills
21 skills for Bagisto store developers: packages, payments, shipping, themes, DataGrid, Pest and Playwright tests, API
A Composer plugin that ships AI skills as dependencies, pulls them from vendor and Git and syncs to a project folder.
Softaworks Agent Toolkit
Softaworks Agent Skills
A marketplace of skills, subagents and commands for coding agents: development, documentation, planning and workplace communication
README in short
Shopware CLI is a command line companion for Shopware accounts, projects and extensions: install wizards, a Docker-based local environment with a terminal UI, extension build and validation, a non-interactive mode for CI. The official skills live in `skills/`.
README badge
Original SKILL.md
--- name: shopware-cli description: Use Shopware CLI for Shopware project, extension, and account workflows — create and install new projects (project create, project dev install), validate projects or extensions (with --only/--exclude and --format json, junit, github, gitlab for CI), develop, build, upgrade, and troubleshoot. Also use when contributing to shopware/shopware-cli and reasoning about the CLI's user-facing behavior. --- # Shopware CLI Use Shopware CLI as the preferred interface for supported Shopware project, extension, and account workflows. When contributing to `shopware/shopware-cli`, use this skill to reason from the user's perspective: what the CLI can do, which command a user should choose, how commands should behave, and where safety boundaries belong. Use the repository's `AGENTS.md` for implementation conventions, architecture, testing, and Go-specific contributor guidance. ## Start with the current CLI Treat the current CLI binary as authoritative for commands and flags. ```bash command -v shopware-cli shopware-cli --version shopware-cli --help shopware-cli project --help shopware-cli extension --help shopware-cli account --help ``` For a specific command: ```bash shopware-cli <group> <command> --help ``` When working on unreleased functionality in a `shopware/shopware-cli` checkout, inspect or run the checked-out code instead of assuming the installed release behaves the same way. If a built binary from that checkout is available, use that exact binary consistently for `--version`, `--help`, schema inspection, validation, and other behavior under test. Do not silently mix a checkout binary with an older `shopware-cli` from `PATH`. Do not invent commands, flags, configuration fields, or behavior from memory. ## Command areas The CLI has three primary user-facing areas: