What problem does it solve? Setting up Salesforce Code Analyzer involves installing the sf CLI plugin, verifying Java/Node/Python prerequisites, and authoring a correct code-analyzer.yml file where a single misspelled rule name is silently ignored. This Skill handles installation, prerequisite checks, broken-setup diagnosis, and all configuration edits so scans run correctly. ## Core Features & Use Cases - Setup and Diagnostics: Checks sf CLI, plugin, Java 11+, Node 18+, and Python 3 prerequisites, then follows a layered diagnostic flow to fix broken installations one layer at a time. - Configuration Management: Creates or edits code-analyzer.yml for engine enable/disable, ignore patterns, rule severity overrides, suppressions, and engine-specific tuning like SFGE heap size, with fuzzy rule-name resolution to exact names before writing YAML. - CI/CD Pipeline Setup: Generates GitHub Actions, Jenkins, GitLab, or Bitbucket pipelines with quality gates, SARIF upload, and changed-files-only scanning. - Use Case: A developer says "disable the ApexDoc rule, ignore test files, and add a GitHub Actions quality gate" — the Skill resolves the exact rule name, writes only those overrides to code-analyzer.yml, validates with sf code-analyzer config, and produces the workflow file. ## Quick Start Ask the assistant to set up Salesforce Code Analyzer in this project and configure it to ignore test files and fail the build on critical violations.
