Skip to content

fix(reference): cover utilized and utilization in prefer-use-over-utilize - #592

Merged
theCodeDrift merged 1 commit into
mainfrom
fix/reference-utilize-inflections
Oct 30, 2026
Merged

theCodeDrift merged 1 commit into
mainfrom
fix/reference-utilize-inflections

Conversation

@theCodeDrift

Copy link
Copy Markdown
Member

The `prefer-use-over-utilize` reference rule's prompt asks it to "cover the inflected forms", but its swap held only `utilize`, `utilizes` and `utilizing`. A rule generated correctly from the prompt, with fail cases like `We utilized the API`, was graded against a reference that did not fire on them, so taskless/taskless's generation evals counted correct fixtures as wrong.

  • The swap adds `utilized: used` and `utilization: use`, each with a reference fail case (`tests/fail/utilized-past/`, `tests/fail/utilization-noun/`), listed in the corpus manifest.
  • The prompt now names the forms it is graded on, including the noun, so a generation that follows it passes the held-out cases.
  • `assets/reference.json` is regenerated. Its `version` is unchanged: the shape is the same, only one entry's content moved.
  • `test/reference-verify.test.ts` stages the published vale entry as a consumer would and verifies it against its own cases. With the old swap restored it fails with the two `fail case did not fire` errors from the issue.

Only the vale reference was failing evals, so the sg and runtime entries are out of scope.

Refs taskless/taskless#406
Fixes #591

…lize

The prompt asks for the inflected forms, but the swap lacked utilized and
the noun utilization, so downstream evals graded correct generations as
wrong. Add both to the swap with a fail case each, name the forms in the
prompt, and verify the published vale reference against its own cases.
@theCodeDrift
theCodeDrift merged commit 0b2ed45 into main Oct 30, 2026
8 checks passed
@theCodeDrift
theCodeDrift deleted the fix/reference-utilize-inflections branch October 30, 2026 16:37
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.

Reference rules no-eval-call and prefer-use-over-utilize are narrower than their own prompts

1 participant