Apex Desk - will this Apex trigger survive 200 records?
Paste one Salesforce Apex deployment unit - the trigger, its handler and service classes, the SOQL they run and the test class - and run one of five jobs over it: a governor-limit budget projected across a full 200-record trigger batch, a sharing / CRUD / FLS security review, a SOQL selectivity review with every risky query rewritten, the unit refactored into one-trigger-per-object handler shape, or a bulk-safe PNB test class. A free in-browser Apex reader masks comments and strings, brace-matches every loop and parses every query first, so the model is handed facts instead of guesses - and has to reconcile each one. Derived from the agent skills @github/salesforce-apex-quality, @forcedotcom/querying-soql, @forcedotcom/generating-apex, @forcedotcom/generating-apex-test and @forcedotcom/trigger-refactor-pipeline. Not affiliated with Salesforce or GitHub.
Details
gpt-terra Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.