Menu
Verification steps for code changes. Use after ANY code change to ensure quality, or when creating plans because those should include verification steps.
| name | verification |
| description | Verification steps for code changes. Use after ANY code change to ensure quality, or when creating plans because those should include verification steps. |
The stop hook runs compile, lint, effect LS, test, vscode:bundle, and knip automatically when the agent stops — no need to run these manually.
Run this only if the stop hook doesn't catch it:
Dupes — npm run check:dupes, check jscpd-report for flagged changes
GitHub Actions (only if changing .github/workflows/*.{yml,yaml} or .github/actions/*/action.{yml,yaml}) — npm run check:actions
Playwright (only if working in these packages: salesforcedx-vscode-core, salesforcedx-vscode-org, salesforcedx-vscode-services, salesforcedx-vscode-org-browser, salesforcedx-vscode-metadata, salesforcedx-vscode-apex-testing, salesforcedx-vscode-apex-log, playwright-vscode-ext)
npm run test:web -w <package-name> -- --retries 0 / npm run test:desktop -w <package-name> -- --retries 0-w for single package, never cd into a packageInclude verification steps after the "actual" todos. Follow this checklist.
references/unit-tests.md — unit testsreferences/compile.md — compile; TS4023 / TS1261 skills@.claude/skills/ts4023-effect-errors/ — TS4023@.claude/skills/ts1261-filename-casing/ — TS1261@.claude/skills/playwright-e2e/ — Playwright E2Eeffect-advocate subagent — invoke after Effect-related changes to flag missed Effect idioms (schemas, Option, retry/timeout/cache, services reuse).writing, running, and debugging Playwright tests; creating and recreating scratch orgs (Dreamhouse, minimal, non-tracking); working with their output from github actions
Guidelines for consuming salesforcedx-vscode-services extension API. Use when working with extensions that have extensionDependency on salesforcedx-vscode-services, registering commands, using Workspace/Connection/Project/Settings/FS/Channel/Media services, quickpick/quickInput, implementing file/config watchers, editing extensionProvider.ts, buildAllServicesLayer, AllServicesLayer, setAllServicesLayer, prebuiltServicesDependencies, or Layer composition for VS Code extensions.
Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Interact with the Gus Salesforce org via CLI (sf). Query, create, update work items; query team epics. Use when user mentions Gus, work items, epics, or GUS/Git2Gus workflows.
Polish the automated CHANGELOG for a release branch. Removes GUS refs, categorizes under-the-cover changes, improves customer-facing descriptions. Use when preparing/reviewing the changelog on a release branch, or when user mentions changelog quality.