magento2-linter

# Magento 2 Linter This skill runs automated code quality checks to verify Magento 2 coding standards compliance. ## Related Skills **REQUIRED BACKGROUND:** Load `magento2-dev-core` first — this skill validates code against the coding/security standards that skill defines, and its patterns are what you fix findings with. Part of the QA trio with `magento2-security-scan` (deeper vulnerability scanning) and `magento2-performance-audit` (runtime/infrastructure checks) — run all three before a release. Fix findings using the patterns in `magento2-dev-core` (or the relevant frontend/backend/Hyvä skill). ## Real CI Verification Is Mandatory Before Pushing If the project has a real CI wrapper for linting (e.g. Sutunam's `magelint` — see "Check the Project's Real CI Setup First" below), running it for real is a **required step before pushing or opening a PR/MR, not an optional nice-to-have**. A local approximation (isolated scratch install, `bootstrapFiles` pointed at a host project's autoload, or any other stand-in for the actual per-PHP-version isolated install the CI runs) is a fast pre-check to catch obvious problems early — it is not proof the branch is clean, because it can diverge from the real run in either direction (see the finding-triage callout under "Check the Project's Real CI Setup First"). Before telling the user a branch is "verified" or "ready to push": either run the real CI wrapper yourself if credentials/access allow, or explicitly ask the user to run it a...