Verification steps for code changes. Use after ANY code change to ensure quality, or when creating plans because those should include verification steps.
Resources
1Install
npx skillscat add forcedotcom/salesforcedx-vscode/verification Install via the SkillsCat registry.
Verification
Do each of these steps, in order. Do not move to a step unless all previous are passing. Run these commands from the repo level. If you make any changes, go back to step 1.
npm run compile- See references/compile.md for commands and errorsnpm run lint- fix any new errors or warningsnpm run test- See [references/unit-tests.md]npm run vscode:bundleto ensure the extensions still bundleIf working in packages with
test:web/test:desktopscripts:- Package-level only (not in root):
salesforcedx-vscode-core,salesforcedx-vscode-services(web),salesforcedx-vscode-org-browser,salesforcedx-vscode-metadata,salesforcedx-vscode-apex-testing,playwright-vscode-ext - Run from root:
npm run test:web -w <package-name>/npm run test:desktop -w <package-name> - Skip if not in these packages
- Run with
--retries 0for fast feedback and less flakes
- Package-level only (not in root):
npx knip- check for dead code related to your changes
- Fix ALL unused exports - if knip shows unused exports, remove them immediately unless they're used for tests. Exception for ts4023 reasons
- Don't leave any exports that are only used within the same file
- check for dupes
npm run check:dupesand then look injscpd-reportto make sure none of your changes are flagged.
Rules
- Don't change /src AND /test together (except imports/renames)
- Be aware of wireit caching; You can look in the bundle to see (and also turn off
minifyif that helps debug) - Port 3001 for tests (not 3000 - Docker/Grafana uses that)
- All commands run from salesforcedx-vscode root; use
-wto specify runs for a single package. Nevercdinto a package. - do not say a test/compile/lint failure was "pre-existing" without running the same operation on a previous version of the code before the current un-pushed commits began.
Troubleshooting
- if knip fails due to
ERR_MODULE_NOT_FOUNDyou canrm -rf ~/.npm/_npxand re-run it. You'll have to agree to it (or pass-yto it)
Plans
When creating plans in plan mode, always include verification steps after the "actual" todos. The verification steps should follow this checklist.
References
references/unit-tests.md- Running unit testsreferences/compile.md- Compilation commands and TS4023 errors@.claude/skills/playwright-e2e/- Playwright E2E testing guidelines