Agent skill · adobe
commerce-app-review
Use when validating an App Builder app before submitting to Adobe Exchange, or when the user mentions Adobe Commerce app compliance, extension review, marketplace submission, or Adobe Exchange listing. Checks security requirements, project structure, documentation completeness, and dependency health; reports MUST-have blockers and NICE-to-have recommendations and walks through each finding interactively.
What it needs
About 5k tokens when loaded.
What this skill does
Self-review an App Builder app Reviews a local app directory against Adobe's Commerce submission guidelines and walks through each finding interactively — MUST-have blockers first, then NICE-to-have recommendations. Inputs APPPATH (optional) — path to the app root. Defaults to the current working directory. APPTYPE (required) — downloadable or non-downloadable. A downloadable app allows merchants to download the source package; a non-downloadable app is installed directly from Adobe Exchange with one click. Procedure 1. Validate the path and app type If APPPATH is not provided, use the current working directory. Confirm it exists and is a directory. If not, stop and report: Path not found. Please provide the path to the root of your app codebase. If APPTYPE is not provided, ask: Is this app downloadable or non-downloadable? - Downloadable — merchants download the source package and deploy it themselves - Non-downloadable — merchants install directly from Adobe Exchange with one click Do not proceed until both are confirmed. Check whether aio is installed (e.g. command -v aio). This is a presence check only — do not attempt to authenticate at this stage. If aio is not found, note it once: Note: aio isn't installed. Walkthrough enrichment (Step 8) will use fallback knowledge unless aio is installed and authenticated before then. Continue either way. 2. Load local references Read references/finding.md and all files under references/exceptions/ (paths relative to this skill file). Load pattern files conditionally: references/patterns/cors-storefront-actions.md — always references/patterns/accs-rest-api-dependency.md — always references/patterns/aio-commerce-sdk.md — always references/patterns/admin-ui-sdk.md — only if commerce/backend-ui/1 is in app.config.yaml or ext.config.yaml, or @adobe/uix-guest/@adobe/uix-core in package.json Pattern files take precedence over fetched guidelines. Exception files suppress findings from both. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills adobe/commerce-app-review