What problem does it solve? Salesforce teams struggle to enforce consistent static analysis across Apex, LWC, Flows, and metadata: Code Analyzer v5 has seven engines, a complex rule selector grammar, and a severity taxonomy that is easy to misconfigure, leading to noisy reports, silently disabled security rules, or gates that block all delivery on legacy codebases. ## Core Features & Use Cases - Engine and CLI mastery: Covers sf code-analyzer run/rules/config with --workspace, --target, --rule-selector, --severity-threshold, and output formats (JSON, HTML, SARIF) across the pmd, eslint, regex, retire-js, flow, cpd, and sfge engines. - Configuration and custom rules: Provides the code-analyzer.yml schema, severity and tag overrides, custom PMD XPath rulesets, regex convention rules, ESLint flat config with @salesforce/eslint-config-lwc, and Prettier with prettier-plugin-apex. - Gate policy and legacy adoption: Defines the 1-5 severity taxonomy, suppression markers with caps and reasons, and baseline-plus-ratchet strategies for introducing the gate to legacy code without stopping delivery. - Use Case: A vf-check analyzer run fails on a pull request; use this Skill to triage the violation, decide fix versus suppression, write a scoped suppression with max_suppressed_violations and a ticket reference, and verify the gate exits 0. ## Quick Start Ask the assistant to configure Salesforce Code Analyzer for the project and run the recommended ruleset with a severity threshold of 3 against the changed files.
