sf-apex-constraints

To check Apex classes for governor limit violations, run validation checks against defined governance rules to automatically flag bulkification issues, naming inconsistencies, and insecure patterns across artifacts before deployment.

During a Salesforce Apex code review, you should enforce explicit sharing rules, bulkification best practices, and security patterns defined in SECURITY_PATTERNS.md to flag insecure patterns across classes, triggers, and batch jobs.

Yes, you can apply this to bulkify Apex triggers and enforce naming conventions. It validates triggers against governor limits and ensures explicit sharing and naming consistency across multiple artifacts during development.

You need to validate Salesforce batch jobs against governor limits during development and code reviews to ensure bulkification and prevent limit violations before deploying the batch jobs to production.

The best way to automate Apex governance checks is to apply constraint rules across multiple artifacts, automatically flagging naming inconsistencies, security vulnerabilities, and governor limit violations during the development and review phases.