skills.rest
forcedotcom
forcedotcomOFFICIAL
Explore all skills by this author →
Website𝕏@salesforcedevsGitHub

verification

Validate code changes with compile, lint, diagnostics, tests, and bundling.

1.0k|453|Updated Jun 21, 2017
Search Tags:#verification#ci-cd#quality-assurance#compile#lint#tests#code-changes
One-click install
npx skills add https://github.com/forcedotcom/salesforcedx-vscode --skill verification-forcedotcom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/forcedotcom/salesforcedx-vscode/tree/main/.claude/skills/verification
Command: npx skills add https://github.com/forcedotcom/salesforcedx-vscode --skill verification-forcedotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Verification steps provide a repeatable, hands-off process to ensure code changes don't introduce regressions.

Core Features & Use Cases

  • Defines a repeatable verification plan for code changes, guiding execution of compilation, linting, diagnostics, tests, and packaging.
  • Enforces a strict execution order and ensures issues are surfaced early in the workflow.
  • Suitable after commits, pull requests, or planning phases in multi-package workspaces.

Quick Start

Run the verification steps from the repository root to validate your changes.

Frequently Asked Questions about verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate code changes across a multi-package repository?▼

Guarantee quality after every code change by executing a reproducible verification workflow that covers compilation, linting, diagnostics, tests, and bundling. This enforces a strict execution order to surface errors before shipping.

What is the correct sequence to run compile, lint, and tests after a commit?▼

The verification sequence enforces strict execution order across compilation, linting, diagnostics, tests, and packaging. This ensures issues are surfaced early in the workflow before bundling.

Can I use this verification workflow for multi-package workspaces?▼

Yes, the verification workflow is suitable for multi-package workspaces after commits or plan creation. It defines a repeatable plan to validate code changes across the repository.

Why do I need a repeatable verification process for code changes?▼

A repeatable verification process provides a hands-off method to ensure code changes do not introduce regressions. It enforces required commands and sequencing to surface errors before shipping.

Does the verification workflow handle bundling and packaging?▼

Yes, the verification workflow includes bundling and packaging as part of its execution sequence. This ensures code changes are fully validated through compilation, linting, diagnostics, tests, and packaging before shipping.

Related Skills

Explore More Software Engineering Skills→
adiomasadiomas

verification-runner

Run typecheck, lint, tests, and build in deterministic order.

Community
Intermediate
VvanlaarVvanlaar

ado-fix-review-comments

Fix GitHub pull request review comments and reply on the PR thread.

Community
Intermediate
DevelopersGlobalDevelopersGlobal
65

ci-cd-pipelines

Automate CI/CD pipelines with quality gates and deployment processes.

Official
Advanced
hardisgroupcomhardisgroupcom
368

test

Build, lint, and test code changes with yarn commands.

Official
Intermediate