Overview
Availability
✅
❌
From
January 25
The project analysis command helps you analyze your Salesforce project for potential issues and provides detailed reports in various formats. This command is particularly useful for identifying issues such as duplicate components, hardcoding of environment configuration metadata and so fort the
Usage
Common Use Cases
The analyze command serves several key purposes:
Runs various available linters across the project
Generating comprehensive analysis reports
Integration with CI/CD pipelines for automated checks
Available Flags
--package, -p
The name of the package to analyze
No
-
--domain, -d
The domain to analyze
No
-
--source-path, -s
The path to analyze
No
-
--exclude-linters
Comma-separated list of linters to exclude
No
[]
--fail-on
Linters that should cause command failure if issues found
No
[]
--show-aliasfy-notes
Show notes for aliasified packages
No
true
--fail-on-unclaimed
Fail when duplicates are found in unclaimed packages
No
false
--output-format
Output format (markdown, json, github)
No
markdown
--report-dir
Directory for analysis reports
No
-
Scoping Analysis
The command provides three mutually exclusive ways to scope your analysis:
By Package: Analyze specific packages
By Domain: Analyze all packages in a domain
By Source Path: Analyze a specific directory
Output Formats
The command supports multiple output formats:
Markdown: Human-readable documentation format
JSON: Machine-readable format for integration with other tools
GitHub: Special format for GitHub Checks API integration
GitHub Integration
When running in GitHub Actions, the command automatically:
Creates GitHub Check runs for each analysis
Adds annotations to the code for identified issues
Provides detailed summaries in the GitHub UI
Examples
Basic analysis of all packages:
Analyze specific packages with JSON output:
Analyze with strict validation:
Generate reports in a specific directory:
Last updated
Was this helpful?