/refactor-apex — Refactor an Apex class to canonical patterns
Refactor Apex classes to canonical patterns with automated templates and testing.
Wraps agents/apex-refactorer/AGENT.md. Takes a target class, returns a refactored version + test class using templates/apex/.
Step 1 — Collect inputs
Ask the user:
1. Path to the Apex class to refactor?
Example: force-app/main/default/classes/AccountTrigger.cls
2. Any related paths the refactorer should read alongside it?
(Helper classes, existing test class — optional)
3. Is a target-org alias connected for MCP lookups? [optional]
(If yes, the refactorer will call validate_against_org to check for existing frameworks)
If the source path is missing or the file doesn't exist, STOP and ask for a valid path. Do not guess.
Step 2 — Load the agent
Read agents/apex-refactorer/AGENT.md in full. Also read every file it lists under Mandatory Reads Before Starting.
Step 3 — Execute the plan
Follow the 5-step plan inside the AGENT.md exactly:
- Classify the class shape
- Apply templates
- Insert CRUD/FLS enforcement
- Generate the test class
- (Optional) org validation
Step 4 — Deliver the output
Return the Output Contract block from the AGENT.md:
- Summary (shape, templates applied, confidence)
- Refactored files (one fenced block per generated file)
- Diff summary with per-change citation
- Risk notes
- Citations
Step 5 — Recommend follow-ups
After the refactor, suggest running (but do not auto-invoke):
/scan-securityon the refactored class/optimize-soqlif the class contains SOQL/gen-testsif the generated test class needs extension
What this command does NOT do
- Does not commit or deploy the refactored code.
- Does not run multiple files in a single invocation.
- Does not freestyle — every change cites a template or skill.