magento2-tools

Full release-readiness audit — every findings dimension consolidated into one ranked report + merged SARIF (magento2-audit)

Reproduce → root-cause → minimal TDD fix → regression test → review (magento2-bug-fix)

Resolve the Magento 2 project context — vendor, runner, versions, theme, tools (magento2-context). Use when explicitly asked to resolve or refresh project context.

Deploy Magento 2 module(s) — pre-flight, ordered deploy, rollback (magento2-deploy)

End-to-end Magento 2 feature implementation orchestrator (magento2-feature-implement)

Use for a read-only COMPREHENSION mapping of an existing Magento 2 module or feature — maps execution paths, DI wiring, plugin/observer/preference extension points, service-contract and cross-module dependencies, and produces a Mermaid call-chain flowchart. Use before modifying unfamiliar code, during bug-fix root-cause analysis (RCA) to trace a suspect execution path, or as the inventory/comprehension step of a parallel review (run this first, then pass the map to magento2-reviewer for quality judgement). Returns a structured COMPREHENSION MAP — entry points, data flow, extension points, dependencies, Mermaid flowchart, and open questions. Never modifies code and never emits severity-ranked findings (that is magento2-reviewer's role). Examples — "map how Acme_Checkout builds the grand totals and which plugins intercept the collect call"; "trace what runs when sales_order_place_after fires in Acme_Loyalty".

Use for an independent, READ-ONLY review/audit of a Magento 2 module — either a whole module or a single review dimension (architecture/API, security, frontend/admin, testing/tooling, or performance/operations). Dispatch one agent per dimension to review large or security-sensitive modules in parallel; the caller (magento2-module-review) owns final synthesis (dedup, severity normalization, conflict tie-breaking). Returns findings-first results — each finding with a severity (Critical/High/Medium/Low/Info), category, `file:line` evidence, and a concrete fix. Never modifies code. Examples — "review the security dimension of app/code/Acme/OrderExport"; "audit the performance surfaces of Acme_Catalog and return ranked findings".

Audit a Magento 2 module's/theme's storefront templates for WCAG accessibility issues — missing alt text, unlabelled form controls, ARIA misuse, heading-order breaks, keyboard/tab-index problems, and LESS color-contrast heuristics — and emit ranked findings (Markdown + JSON + SARIF). Static-first (no running instance needed); optional opt-in pa11y runtime pass. For building accessible frontend assets use `magento2-frontend-create`; for general module quality use `magento2-module-review`.

Generate a Magento 2 adminhtml UI-component edit form — the modern declarative ui_component/{entity}_form.xml plus its DataProvider, button blocks, and the New/Edit/Save/Delete controllers wired to a listing. Use when the user wants to add or scaffold a new admin form, an entity edit page, a "New/Edit" backend screen, fieldsets, a WYSIWYG field, a toggle, dynamic-rows, or file/image uploaders in the Magento admin. Detects edition (Open Source vs Adobe Commerce) and flags Commerce-only form features. Produces files that pass magento2-module-review with zero Critical/High findings.

Generate a Magento 2 adminhtml UI-component listing/grid — the declarative `ui_component/{entity}_listing.xml` plus its DataProvider, columns, actions column, and mass actions, wired to an existing edit form. Use when the user wants to add or scaffold an admin grid, data grid, listing page, grid columns, filters, mass actions, or an actions column in the Magento admin. Pairs with magento2-adminhtml-form (the edit form); for the form itself use magento2-adminhtml-form. Detects edition and flags Commerce-only grid features. Produces files that pass magento2-module-review with zero Critical/High findings.

Use when the user wants a full pre-release, release-readiness, or "audit everything" pass over a Magento 2 module or codebase — one command that runs every read-only findings dimension and returns a SINGLE consolidated, de-duplicated, severity-ranked report plus one merged SARIF for CI / GitHub Code Scanning. Fans the dimensions out in parallel: architecture/quality/security review via the `magento2-reviewer` agent per dimension, plus the specialist audits `magento2-security-audit`, `magento2-performance-audit`, `magento2-static-analysis`, `magento2-accessibility-audit`, `magento2-marketplace-prep`, and `magento2-breeze-compat-audit` where the module's surface warrants — then consolidates. Read-only; never modifies code. For a SINGLE dimension, invoke that skill directly (`magento2-module-review`, `magento2-security-audit`, `magento2-performance-audit`); to BUILD or change functionality rather than inspect it, use `magento2-feature-implement`.

Scaffold a Swissup Breeze (Breezefront) child theme — theme.xml with a Swissup/breeze-* parent, registration.php, composer.json, a Breeze-only layout handle, and Breeze-side overrides in web/css/breeze/_default.less with @critical guards. Use when the user wants a new Breeze child or custom theme. Detects Breeze via magento2-context (theme.breeze) and refuses with the install command when Breeze is absent. Sibling to magento2-frontend-create, which builds generic Luma/Hyva/custom themes plus RequireJS/Knockout/Alpine components; this skill is Breeze-specific. To adapt an existing module to Breeze use magento2-breeze-module-adapt; to check a module's Breeze compatibility use magento2-breeze-compat-audit.

1 hook across 1 event