Verification
| Key | Shape | Default | Purpose |
|---|---|---|---|
verify.typecheck |
string[] | none | Commands run in order during builds and before push or merge. This is the preferred form. |
verify.typecheckCombined |
string | none | One equivalent fallback command, used only when verify.typecheck is absent. |
verify.test |
string | none | Standard local suite. Required for setup to enable fast item merges. |
verify.testSingle |
string | none | Single-spec command containing a <path/to/test> placeholder, replaced with the file to run. The story gate uses it for the touched suites. |
verify.lint |
string | none | Lint command, used when the changed paths are in its scope. |
verify.testDir |
string | none | Test directory used to place new specs. |
verify.skipDuringStoryBuilds |
array | [] |
Slow suites that run as conditional cloud CI jobs. Every entry must match a real workflow job. |
With no typecheck command, push asks instead of guessing. With no test command, setup disables fast merges; if fast merges were enabled manually anyway, the item would have review but no local test gate.
Conditional cloud suite entry#
{
"name": "e2e-matrix",
"alwaysRunWhenBase": ["productionBranch"],
"manualTriggerLabel": "run-e2e",
"runWhenChangedPaths": ["apps/web/**", "packages/e2e/**"],
"ciChecksByBase": {
"baseBranch": ["E2E (PR gate)"],
"productionBranch": ["E2E (full matrix)"]
}
}
| Field | Meaning |
|---|---|
name |
Display name. |
alwaysRunWhenBase |
Branch roles where the suite is always required, regardless of paths. |
manualTriggerLabel |
Label the loop adds when the suite is requested manually. |
runWhenChangedPaths |
Globs matched against the complete final diff, including both sides of renames. |
ciChecksByBase |
Required check names for each branch role. No mapping means no requirement on that base. |
An empty verify.skipDuringStoryBuilds means no slow cloud gate exists and no absent check should be awaited.
Local pre-ship checks#
preShipChecks is an array of suites that run locally at a pull-request or production-release boundary and never appear in CI:
{
"name": "integration-suite",
"pathGlobs": ["packages/api/**", "migrations/**"],
"command": "pnpm test:integration",
"when": "perPr",
"timeoutNote": "About 25 minutes; do not run beside another test process."
}
| Field | Meaning |
|---|---|
name |
Display name. |
pathGlobs |
Per-PR changed-path selector. Empty means every PR. Ignored for releaseOnly, unless the entry also sets onlyWhenTouched. |
onlyWhenTouched |
From 3.13.0, releaseOnly entries only: true runs the check only when the release diff touches its pathGlobs, and the release reports the skip with its reason. Absent means the check runs at every release. |
command |
Command to run. |
when |
perPr, releaseOnly, or always. An entry without it is never selected. |
runAt |
From 3.28.0, releaseOnly entries only: "train" runs the check on the release-train snapshot before the train merges into the release source (outside release clearance when release.clearance.scope is "cut-to-deploy"), and the release does not repeat it before the production merge when it passed there on the same snapshot. Combining it with onlyWhenTouched, or setting it on any other when, is a config error. Absent, a releaseOnly check runs at the release as before. |
rerunAtMerge |
From 3.61.0, releaseOnly entries only: true runs the check again at every clearance claim and just before the merge under release.clearance.scope: "merge-and-deploy", for a check whose result can lapse while a release waits, such as a sign-in. Elsewhere it changes nothing. Setting it on any other when, or together with runAt, is a config error. |
timeoutNote |
Duration and environment guidance shown before the run. |
Entries run sequentially in array order. A red per-PR check blocks the pull request. A release check can be waived only by the owner, with the waiver recorded. Re-run them by hand with /devstride:pre-ship: --only <names> re-runs just the failed or affected checks after a fix, and --skip <name> is the owner's explicit waiver, reported as WAIVED.
Keep a suite in exactly one place: verify.skipDuringStoryBuilds for cloud CI, or preShipChecks for a local ship-boundary run.
preCommitWiringChecks is a string array of repository-specific wiring checks the build loop expects before commits. Setup leaves it [] because only the repository can name these checks.