◆ Salesforce

Perform Apex static code analysis

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Salesforce tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskRun the code quality check on the new Apex class 'OpportunityProcessor' that I just wrote, and…+
Run the code quality check on the new Apex class 'OpportunityProcessor' that I just wrote, and give me a report of any critical vulnerabilities or performance issues before I commit it.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I deploy any new Apex code, automatically run a comprehensive security and performance…+
Before I deploy any new Apex code, automatically run a comprehensive security and performance scan, and highlight any potential issues that could lead to governor limit errors or data breaches. I need to see the specific lines of code and recommended fixes.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just finished the 'AccountMergeHandler' Apex class, and it's critical for our end-of-year…+
I'm about to deploy a critical Apex trigger, but I'm worried about it breaking existing functionality or hitting governor limits under load.
I just finished the 'AccountMergeHandler' Apex class, and it's critical for our end-of-year data cleanup. I'm worried it might have hidden bugs or hit governor limits if many accounts are merged at once. Our last deployment caused a major outage. How can I run a thorough analysis on this specific code to catch any potential runtime issues or security flaws before I even think about deploying it to production?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently find out about performance bottlenecks or security vulnerabilities in my Apex…+
I often find out about Apex code issues only after deployment, leading to rollbacks and lost time.
I consistently find out about performance bottlenecks or security vulnerabilities in my Apex code only after it's been deployed, which leads to emergency fixes and lost credibility with the business. This pattern of reactive debugging is costing us too much. What habit or pre-deployment check should I integrate into my workflow to proactively catch these issues and ensure robust, secure code every time?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Salesforce's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.