magento2-performance-audit

This skill should be used when the user asks to "audit performance", "check Core Web Vitals", "run Lighthouse", "check server configuration", "verify Redis/Varnish setup", "analyze database queries", "find N+1 query issues", "review indexer configuration", "check cron health", "debug cache flush", asks "why does full_page cache keep flushing", wants to "trace FPC invalidation", or reports "too many ajax requests", a "customer data section reload storm", or a "crawler overloading server". Performs a comprehensive performance and health audit for Magento 2 projects against Adobe Commerce Best Practices. DEPENDENT on magento2-dev-core for code-level performance patterns.

跳到安装

仓库: ddtcorex/maestro-skills
最近来源活动: 2026年8月27日 07:17
检测到的 SKILL.md 语言: 英语
星标: 4
分支: 2

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/ddtcorex/maestro-skills --skill magento2-performance-audit

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

12 个文件

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

Magento 2 Performance Audit

This skill performs a comprehensive audit of Magento 2 performance, infrastructure, and code-level patterns.

Govard-Native Audit Coverage

govard audit run executes PHPCS and PHPStan through Govard's pinned lint toolchain image — it covers coding-standard and static-analysis findings only. As of Govard v1.64.0 no performance audit check exists: govard audit run --checks performance fails with "audit check ... is not implemented". Govard v1.64.0 does add a native check () that machine-captures the stock profiler CSV for one URL — a quick complement to this skill's manual per-page audit, not a replacement: it ships no query log, no cross-page matrix, and no threshold analysis. The profiler requires a project target (not standalone), an absolute http(s) URL (the request carries so stock Magento enables the CSV), and is guarded by a per-project lease; the CSV lands as with its SHA in — open it as spreadsheet to read per-timer costs. Manual per-page captures (7 pages) cost ~2.5-3 min on reference project (50k queries/page with call-stack, 16-26s each) — keep all 7, run with 300s timeout or background polling and trap restore, not by sampling fewer categories (that hides per-item N+1s). Keep running this checklist yourself and treat as the shared lint gate. Never present a lint-only pass as a performance verdict.

Magento 2 Performance Audit

This skill performs a comprehensive audit of Magento 2 performance, infrastructure, and code-level patterns.

Govard-Native Audit Coverage

Rationalization

Reality

"Infra/cache/indexer checks already give strong signal, that's enough"

Slow Query Analysis, Cache Invalidation Efficiency, and Client-Side AJAX Load each catch bug classes the others structurally cannot see — one being clean says nothing about the others

"I already found a solid N+1, that's enough for a report"

A real finding proves the audit found something; it doesn't prove the mandatory steps ran. Finding a bug early is not a reason to stop the checklist

"One category and one product page is representative enough"

Only 3 differently-sized samples per type can surface the size-scaling N+1 signal (references/per-page-type-audit.md) — a single sample is provably unable to show it, however clean the one page looks

"This step needs admin credentials / a Chrome DevTools MCP I don't have"

Mark that section unverified with the reason, in the report — don't drop it from the conversation as if it were never in scope

"The draft report already has good findings, ship it"

Diff the draft against every checkbox in the Audit Report Template before presenting it as done — an unchecked box with no skip reason means the audit isn't finished, not that it's fine to omit

"This query shape (or profiler timer) repeats/is slow but I don't think it's a real bug"

Not your call to make silently — list it in the Repeated Query Shapes or Slowest Blocks/Templates table (references/report-template.md) with your assessment anyway. A borderline case left out of the report is indistinguishable from one that was never checked

"The user only asked about query counts, so I only ran that"

Correct if their own words named that one category — say so under a Scope heading. If their ask was general ("audit performance", "review this project"), this is the same shortcut as the rows above, just dressed up as scoping

"There's no dev:profiler:enable / dev:query-log:enable flag, so I'll add one to env.php / patch a bootstrap script"

These are CLI diagnostics, not config flags. Use the exact commands in references/database-query-profiling.md and references/per-page-type-audit.md; never edit env.php or add a one-off bootstrap script

"The reference's grep recipes don't work in govard sh, so I'll write my own"

The container's grep is BusyBox — no --include. find app/code -name '*.php' -exec grep -Hn ... {} + is the supported equivalent (recipes in references/code-level-patterns.md are already BusyBox-safe)

name	magento2-performance-audit
description	This skill should be used when the user asks to "audit performance", "check Core Web Vitals", "run Lighthouse", "check server configuration", "verify Redis/Varnish setup", "analyze database queries", "find N+1 query issues", "review indexer configuration", "check cron health", "debug cache flush", asks "why does full_page cache keep flushing", wants to "trace FPC invalidation", or reports "too many ajax requests", a "customer data section reload storm", or a "crawler overloading server". Performs a comprehensive performance and health audit for Magento 2 projects against Adobe Commerce Best Practices. DEPENDENT on magento2-dev-core for code-level performance patterns.
compatibility	claude, codex, opencode, copilot, dsh
depends	["magento2-dev-core"]
metadata	{"audience":"developers","workflow":"magento"}

name	magento2-performance-audit
description	This skill should be used when the user asks to "audit performance", "check Core Web Vitals", "run Lighthouse", "check server configuration", "verify Redis/Varnish setup", "analyze database queries", "find N+1 query issues", "review indexer configuration", "check cron health", "debug cache flush", asks "why does full_page cache keep flushing", wants to "trace FPC invalidation", or reports "too many ajax requests", a "customer data section reload storm", or a "crawler overloading server". Performs a comprehensive performance and health audit for Magento 2 projects against Adobe Commerce Best Practices. DEPENDENT on magento2-dev-core for code-level performance patterns.
compatibility	claude, codex, opencode, copilot, dsh
depends	["magento2-dev-core"]
metadata	{"audience":"developers","workflow":"magento"}

Category	Reference
Infrastructure, cache, indexer, async consumers, asset optimization, cron, security probes	`references/infrastructure-checks.md`
Core Web Vitals (LCP/INP/CLS, Chrome DevTools MCP trace, Lighthouse fallback)	`references/core-web-vitals.md`
Database query profiling: query-count tiers, query log setup, common issues, Slow Query Analysis	`references/database-query-profiling.md`
HTML profiler: block/template timing, tracing custom-code cost, cross-page-type signals	`references/html-profiler-audit.md`
Per-page-type audit (homepage + 3 category + 3 product samples, uncached)	`references/per-page-type-audit.md`
Cache invalidation efficiency (built-in FPC debug log + Varnish BAN tracing)	`references/cache-invalidation-audit.md`
Client-side AJAX/Customer Data load (sections.xml, reload storms)	`references/ajax-load-audit.md`
Code-level performance patterns (N+1, collection counting, heavy constructors, cache invalidation code)	`references/code-level-patterns.md`
Audit report template + self-verification checklist	`references/report-template.md`

Mode	Pages	Query-log call-stack	Query-time threshold	Files scope	grid_per_page	Time cap	Transport & restore
quick	3 pages small/medium/large (1 home + 1 category + 1 product) — call-stack false — threshold 1 — quick files — grid_per_page 48 — cap 3–5m	`--include-call-stack=false`	`--query-time-threshold=1`	quick files (`app/code` + `app/design` + `app/etc` sampled, batch govard sh)	48	3–5m	On DSH: call `maestro_perf_log_stats` streaming (bounded 2 MiB, server-side `cat var/debug/db.log`) / Otherwise: grep; batch govard sh single setup cmd; trap single
deep	7 pages double-pass (1 home + 3 category small/medium/large + 3 product) — call-stack true — threshold 0 — deep files — 8–12m	`--include-call-stack=true` (two-pass: pass 1 false for counts, pass 2 true for 1–2 traces)	`--query-time-threshold=0`	deep files (full `app/code` + `vendor`/`dev`/`lib`/`m2-hotfixes` to the ignore boundary)	prod `grid_per_page`/`list_per_page`	8–12m	Same On DSH/Otherwise split; batch govard sh where possible; trap single (one `trap ... EXIT` for the whole session)

magento2-performance-audit

安装方式

检查来源文件