Skip to content

docs: make the documented verification loop match what CI runs - #644

Open
ayobamiseun wants to merge 1 commit into
addyosmani:mainfrom
ayobamiseun:docs/verification-loop-matches-ci
Open

ayobamiseun wants to merge 1 commit into
addyosmani:mainfrom
ayobamiseun:docs/verification-loop-matches-ci

Conversation

@ayobamiseun

Copy link
Copy Markdown
Contributor

Summary

docs/developer-onboarding.md promises "everything CI runs, you can run locally", then lists three validators, the eval runner, and one hook test. CI today runs six validators, seven unit-test files, and three hook suites, on three operating systems. A contributor who follows §3 to the letter can open a PR that fails the reference-link, artifact-path, or manifest-version step, or any unit test, without having run them.

The tier table in evals/README.md has the same drift: Tier 1 names two validators where there are now five, and Tier 2 omits the --min-rank1 95 floor that CI actually enforces.

Change

docs/developer-onboarding.md

  • §3 block now lists every command the workflow runs, in workflow order, each with a one-line comment: the five validators, the unit-test glob (with a note for PowerShell, which does not expand globs, the same reason CI lists the files), Tier 2 with the rank-1 floor, Tier 3 dry-run, and all three hook suites.
  • A closing paragraph says CI runs this set on Ubuntu and repeats the validators and unit tests on macOS and Windows, and names the workflow file as the source of truth if the two ever disagree.
  • §4 Path 3 and the §5 pre-PR checklist updated to match: hooks need all three tests, scripts/ changes need the unit tests, command-directory changes need both parity and artifact-path checks.

evals/README.md: Tier 1 row lists what is checked and the five validators; Tier 2 row shows the --min-rank1 95 invocation.

CLAUDE.md has the same stale one-liner but is left alone here because #548 edits that file.

Verification

Every command in the new block was run from this branch and passes:

node scripts/validate-skills.js                      OK
node scripts/validate-reference-links.js             OK
node scripts/validate-versions.js                    OK
node scripts/validate-commands.js                    OK
node scripts/validate-artifact-paths.js              OK
node --test scripts/*-test.js scripts/lib/*-test.js  OK
node scripts/run-evals.js --min-rank1 95             OK
bash hooks/session-start-test.sh                     OK
bash hooks/sdd-cache-test.sh                         OK
bash hooks/simplify-ignore-test.sh                   OK

And the reverse check: every node scripts/…, node --test …, and bash hooks/… command in .github/workflows/test-plugin-install.yml appears in the new block (unit-test files via the glob). Docs only; no behaviour changes.

docs/developer-onboarding.md promises that everything CI runs can be run
locally, then lists three validators, the eval runner and one hook test.
CI runs six validators, seven unit-test files and three hook suites on
three operating systems, so a contributor following the doc can fail
several steps they never ran. The Tier 1 row in evals/README.md names
two validators where there are five, and Tier 2 omits the rank-1 floor.

List every workflow command in the onboarding block in workflow order,
note the PowerShell glob caveat, state the cross-platform leg, name the
workflow file as the source of truth, and align Path 3 and the pre-PR
checklist. Update both tier rows in evals/README.md. CLAUDE.md's stale
line is left for later because addyosmani#548 edits that file.

Every command in the new block was run from this branch and passes, and
every command in the workflow appears in the block.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant