ApexGuru is most useful when teams treat it as a recurring triage surface, not a one-off audit. The setup is light; the operating rhythm matters more.
- Open ApexGuru in Setup
Setup, ApexGuru. The page lists the current Insights inbox with severity, impact, and class.
- Filter and prioritise
Sort by Estimated Impact descending. Filter to high severity first. Most orgs find 10 to 20 high-impact Insights that account for the bulk of preventable governor and performance pain.
- Drill into a specific Insight
Click the Insight. Read the rule, the offending lines, the production telemetry, and the suggested fix. Validate the recommendation against the rest of the class before applying.
- Apply, validate, and mark resolved
Apply the suggested fix in Code Builder or your IDE. Run the relevant Apex tests. Once the deploy lands, mark the Insight resolved in ApexGuru so the inbox reflects reality.
- Run a weekly triage
Schedule a 30-minute weekly review of the inbox. The cadence keeps new Insights from piling up and turns ApexGuru into a steady code-quality habit rather than a quarterly audit.
- ApexGuru ranks by runtime telemetry. An anti-pattern in code nobody calls scores low; do not dismiss the tool when low-value findings dominate a cold codebase.
- AI-suggested fixes are recommendations, not commits. Validate against the rest of the class and run tests before applying.
- Marking Insights Resolved without actually fixing the underlying code hides the issue from the inbox; treat the resolved status as a commitment, not a snooze.
- Some Insights overlap with Code Analyzer findings. Decide which tool owns which check so the same anti-pattern does not generate parallel tickets.