Select proportional validation for changes or reviews in the ctx repository. Use before handing off material code, workflow, migration, documentation, security, packaging, or release changes; before a PR; or when asked whether a change is adequately tested.
SkillScore55Maintained
Automatic
◆QA & Test Engineering pack
Last verified 8/18/2026
What it changes
Passed 7 of 13 test cases with the skill, and 7 of 13 without it.
Without skill50%
With skill55%
Checks it passed that the model alone missed
Treats the fast gate result as committed-history evidence.
Includes 'Static integrity' among the listed rubric criteria.
States that local checks do not replace required Windows native-CI evidence.
and 4 more in the full report
5 fixed7 passed either way6 still failing4 broke
Pass-rate lift
+5 pp
Tokens
-43%
Agent turns
0%
Response time
-66%
Model gemini-3.6-flashMeasured 8/18/2026v112 of 22 cases passed with skill · 13 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
When reporting the final results of a verification run across checks and rubric criteria, what three specific elements must be reported for each check?
What was checked, without and with the skill
Checked
Without skill
With skill
Requires reporting each check, its result, and any omitted or unavailable evidence.
Missed
Passed
case-19 · gemini-3.6-flash · 8/18/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md43 linessingle file
Verify ctx changes
Inspect the requested behavior and changed surface. Read only the relevant
section of CONTRIBUTING.md before selecting checks.
Run the smallest focused tests or deterministic checks that exercise the
changed behavior first.
Escalate evidence in proportion to risk:
Small, localized change: focused tests, schemas, or diff checks.
Material repository change: scripts/no_mistakes_run.sh fast.
PR-level, contract, workflow, migration, packaging, security, or release
change: run the fast gate, then
python scripts/ci_preflight.py --profile pr.
Documentation navigation or linked public-asset change: follow the tracker
contract in CONTRIBUTING.md; do not require tracker changes for ordinary
prose-only edits.
Windows-sensitive change: follow the native-CI contract in
CONTRIBUTING.md; local checks do not replace required Windows evidence.
Treat the fast gate as committed-history evidence. When the working tree is
dirty, pair it with focused checks against the actual uncommitted changes.
If a gate cannot find its trusted pytest, Ruff, and mypy environment, report
the environment failure. Do not silently install dependencies or weaken the
trust check.
Use an independent validator only when semantic risk remains after
deterministic checks, especially for material security, migration, or
release work.
Report each check, its result, and any omitted or unavailable evidence.
Rubric
Mark each applicable criterion pass, fail, or not verified:
Intent: The artifact satisfies the request without unrelated scope.
Behavior: Fresh evidence covers the changed success path and relevant
failure or regression paths.
Static integrity: Applicable lint, formatting, and type checks pass.
Repository contracts: Migration, changed-file, documentation, packaging,
and platform requirements remain satisfied where relevant.
Evidence quality: Results apply to the actual changed surface and are not
stale or inapplicable.
Handoff: Skipped checks and residual risks are stated plainly.