fix(pstack): avoid canonical when clearer wording fits - #399
Open
martinfrancois wants to merge 1 commit into
Open
martinfrancois wants to merge 1 commit into
martinfrancois wants to merge 1 commit into
Conversation
|
The canonical solution to a canonical problem |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Avoid using
canonicalwhen a clearer word fits, such as "main checklist" instead of "canonical checklist". This change adds the word to the existing list in rule 26.Before I asked Codex to avoid this word, it used it 132 times in 595,332 words. That is 2.22 uses per 10,000 words, compared with 0.158 in Python developer discussions from 2016 through 2018. Codex used it about 14.1 times as often in this comparison. All Codex text written after I introduced the preference on July 29, 2026, is excluded from both counts. The texts cover different subjects and years, so this does not prove that all AI tools use the word too often.
I compared the unchanged and changed skill in separate new Codex and Claude sessions. Each version produced 12 short texts per tool, across four sessions.
I also checked that the change still allows valid uses. The writing requests did not supply the word
canonical. With the changed skill, all six Ubuntu articles named Canonical, and all six answers asking for the standard SEO name of a preferred indexing address used "canonical URL". Each check ran three times per tool. The unchanged skill also passed these checks, so the change preserved this behavior.These small tests do not guarantee the same results in every situation.
The change adds only one word.