agentleFS
Sign inStart free
forcedotcomforcedotcom/salesforcedx-vscode/.claude/skills/verification/SKILL.md

verification

Skill1k starsChanged 26 days agoBSD-3-ClauseView on GitHub

Verification steps for code changes. Use after ANY code change to ensure quality, or when creating plans because those should include verification steps.

47 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about forcedotcom/salesforcedx-vscode

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on GitHub and Stack Overflow (52 times).

On GitHub · 50

45 more on GitHub

Used with

Projects with it also use evidence-driven-writing, experiment-results-planning and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Norman-burySkill

    evidence-driven-writing

    Use when writing or revising Introduction, Related Work, background, literature synthesis, or any section where references must drive claims

    Also in 3 projects that use this

  • Norman-burySkill

    experiment-results-planning

    Use when designing experiments, result tables, mock planning data, evaluation protocols, or results sections before real data are final

    Also in 3 projects that use this

  • +10 more from Norman-bury

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this only if the stop hook doesn't catch it:

    line 11
  2. Very specific:

    Run from root: npm run test:web -w <package-name> -- --retries 0 / npm run test:desktop -w <package-name> -- --retries 0

    line 18
  3. Distinctive:

    Don't change /src AND /test together (except imports/renames)

    line 22
  4. Very specific:

    All commands run from repo root.

    line 23
  5. Distinctive:

    Don't call a failure "pre-existing" without verifying on a prior commit

    line 24

“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Verification

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:

  1. Dupes — npm run check:dupes, check jscpd-report for flagged changes
  2. GitHub Actions (only if changing .github/workflows/*.{yml,yaml} or .github/actions/*/action.{yml,yaml}) — npm run check:actions
  3. 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)
    • Run from root: npm run test:web -w <package-name> -- --retries 0 / npm run test:desktop -w <package-name> -- --retries 0

Rules

  • Don't change /src AND /test together (except imports/renames)
  • All commands run from repo root; use -w for single package, never cd into a package
  • Don't call a failure "pre-existing" without verifying on a prior commit

Plans

Include verification steps after the "actual" todos. Follow this checklist.

References

  • references/unit-tests.md — unit tests
  • references/compile.md — compile; TS4023 / TS1261 skills
  • @.claude/skills/ts4023-effect-errors/ — TS4023
  • @.claude/skills/ts1261-filename-casing/ — TS1261
  • @.claude/skills/playwright-e2e/ — Playwright E2E
  • effect-advocate subagent — invoke after Effect-related changes to flag missed Effect idioms (schemas, Option, retry/timeout/cache, services reuse).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free