Individual skill
dx-code-analyzer-run
Run Salesforce Code Analyzer to scan code for security, performance, best practice, and code style violations. Supports all engines (PMD, ESLint, CPD, RetireJS, Flow, SFGE, ApexGuru), targets (files, folders, git diff), categories, and severities. Also handles post-scan exploration: filtering results by engine/severity/category/file, and explaining what rules mean. TRIGGER when: user says 'scan my code', 'check security issues', 'run PMD/ESLint', 'find duplicates', 'analyze Flows', 'check vulnerable libraries', 'AppExchange review', 'lint my LWC', 'static analysis', 'code quality', 'show security violations', 'what is this rule', 'explain ApexCRUDViolation', 'filter results', or mentions engines/file types (.cls, .trigger, .js, .flow-meta.xml). Use this skill for scanning, exploring results, and listing rules. DO NOT TRIGGER when: user asks only about installation/configuration (use dx-code-analyzer-configure), or wants to create a custom rule (use dx-code-analyzer-custom-rule-create).
skills/dx-code-analyzer-run/SKILL.md
Source commit a8a18ce1e4ba12e69b4073eab98ce31bfbd8271e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,151
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesSKILL.mdcore · 25,315 bytesexamples/README.mddoc · 1,861 bytesexamples/basic-scan-output.jsonasset · 2,382 bytesexamples/command-variations.mddoc · 9,780 bytesexamples/fix-application-before-after.mddoc · 3,460 bytesexamples/large-scan-output.jsonasset · 2,253 bytesexamples/security-focused-output.jsonasset · 2,611 bytesreferences/command-examples.mddoc · 3,395 bytesreferences/engine-reference.mddoc · 1,326 bytesreferences/error-handling.mddoc · 1,775 bytesreferences/flag-reference.mddoc · 4,775 bytesreferences/post-scan-workflows.mddoc · 8,065 bytesreferences/quick-start.mddoc · 1,117 bytesreferences/special-behaviors.mddoc · 4,731 bytesreferences/vendor-file-handling.mddoc · 7,105 bytesscripts/apply-fixes.jsruns · 4,485 bytesscripts/describe-rule.jsruns · 12,192 bytesscripts/discover-fixes.jsruns · 1,063 bytesscripts/filter-violations.jsruns · 12,707 bytesscripts/list-rules.jsruns · 8,111 bytesscripts/parse-results.jsruns · 2,123 bytesscripts/query-results.jsruns · 7,324 bytesscripts/summarize-fixes.jsruns · 1,000 bytesscripts/verify-execution.shruns · 863 bytes
Read excerpt
# Running Code Analyzer Skill
## CRITICAL: Mandatory Script Usage
Every interaction with Code Analyzer results MUST go through the bundled scripts in `<skill_dir>/scripts/`. No exceptions.
### WRONG — never do this:
```bash
# WRONG: inline Python to parse results
python3 -c "import json; data = json.load(open('results.json'))..."
# WRONG: inline Node.js to parse results
node -e "const data = require('./results.json')..."