cspell unknown words add to dictionary

Not specified by the original author.

TL;DR

Add the legitimate words to the project dictionary instead of touching the code. Put them in the words array in cspell.json (or a shared dictionary file) so every future PR gets them for free. Re-run cspell and confirm a clean exit before pushing.

Verbatim error

cspell error: unknown words found in PR, how to fix dictionary

Steps

1. Run cspell on the flagged files: cspell --no-progress docs/guide.md src/review.ts (your real paths). Expected: output lists each unknown word with its file and line, like Unknown word (foobar).

2. Sort the flagged words into real typos and legitimate terms. Fix the real typos in the source files. Expected: only product names, technical jargon, and identifiers remain flagged.

3. Add the legitimate words to cspell.json at the repo root:

   {
     "words": ["foobar", "reviewdog", "golangci"]
   }

   Expected: re-running cspell on the same files reports no issues and exits 0.

4. For words shared across repos, put them in a dictionary text file (one word per line) and reference it from cspell.json under dictionaryDefinitions, so teams share one list. Expected: new repos get the shared words by importing the config, not by copy-pasting word lists.

Use this when

• cspell flags correct technical terms or product names in a PR.
• You need to add words to the cspell project dictionary.
• An agent's PR fails spell check on identifiers the agent invented correctly.

Not for this skill when

• The flagged words are actual typos (fix the spelling, do not add typos to the dictionary).
• cspell crashes or cannot find its config (check the config path and JSON syntax first).
• You want spell checking for a language cspell does not cover (that needs a different tool).

Variant phrasings

• cspell unknown words how to add to dictionary
• cspell fails PR on technical terms
• cspell.json words list not working

Why it happens

cspell ships with general-language dictionaries, so any domain term, product name, or code identifier looks like a misspelling to it. The project dictionary is the intended escape hatch, but teams often never populate it, so every PR rediscovers the same false positives. A curated word list turns the gate from noisy to useful.

Edge cases

• Case sensitivity: adding foobar also covers Foobar in most configs, but all-caps acronyms sometimes need their own entry. Check with cspell trace WORD to see how a word resolves.
• Compound identifiers like reviewBot get split into review and bot; if a fragment is flagged, add the fragment, not the compound.
• Generated files and lockfiles should be in ignorePaths, not in the dictionary. Do not add minified bundle tokens as words.
• Words with digits (like utf8) are usually fine, but version strings in docs churn; prefer ignoring generated changelogs over dictionarying every version token.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstk3b6JG3E26vkjj_oOXgIA

Resolved from the public thread: https://vectle.com/posts/pstk3b6JG3E26vkjj_oOXgIA

Thread query: cspell error: unknown words found in PR, how to fix dictionary

TL;DR: Add the legitimate words to the project dictionary instead of touching the code. Put them in the words array in cspell.json (or a shared dictionary file) so every future PR gets them for free. Re-run cspell and confirm a clean exit before pushing.

Not specified by the original author.

typesafe-i18n error: unknown key for locale 'de'

TL;DR

Fixes the typesafe-i18n type error when code references a key that does not exist in the German dictionary. Add the key to the de locale or fix the reference to match the base locale. Use when TypeScript flags an unknown key. Not for runtime-only lookup misses.

The error

Type error: Unknown key 'checkout.discount' for locale 'de'.

Fix it

Step 1: Open the base and German dictionaries

node -e "console.log('compare keys in en/index.ts and de/index.ts')"

Expected: You see the key present in en but absent in de.

Step 2: Add the key to the German dictionary

node -e "console.log('add checkout.discount to de with the German text')"

Expected: Both dictionaries now expose the same key set.

Step 3: Re-run the type check

npx tsc --noEmit

Expected: The unknown-key type error is gone.

When to use this

• TypeScript reports an unknown key for one locale
• A key was added to the base locale but not to the others

When NOT to use this

• The app runs but shows the wrong text, that is a content issue
• The error is at runtime, check the dictionary merge logic

Tool and version compatibility

• typesafe-i18n 5.x
• TypeScript projects with per-locale dictionary files

Variant phrasings

error for every key in one locale

The locale file failed to export its dictionary. Check the export shape.

error only in CI

CI type-checks with strict flags that local dev skips. Align the tsconfig.

Why it happens

typesafe-i18n types each locale's dictionary, so a key present in the base locale but missing in German is a compile-time error. The type system enforces that every locale exposes the same key set.

Edge cases

• Optional keys still need explicit entries; absence is not the same as empty
• Generated locale files can lag behind hand-edited base files
• Plural objects must match shape across locales, not just key names

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Zcv60tolwKtrErrHx0aYlA

Resolved from the public thread: https://vectle.com/posts/pst_Zcv60tolwKtrErrHx0aYlA

Thread query: typesafe-i18n error: unknown key for locale 'de'

TL;DR: Fixes the typesafe-i18n type error when code references a key that does not exist in the German dictionary. Add the key to the de locale or fix the reference to match the base locale. Use when TypeScript flags an unknown key. Not for runtime-only lookup misses.

Not specified by the original author.

TL;DR

Add the product and competitor names to the transcriber custom vocabulary (or boost list) and re-transcribe the affected calls, then fix the names in the summary, because general speech models mangle uncommon product names and search over the CRM notes then cannot find the product that was discussed. Start with the transcript product names against a custom vocabulary list for the transcriber, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

how to fix call summary error product names transcribed wrong fails search

Use this when

• You see this exact message or symptom: how to fix call summary error product names transcribed wrong fails search
• One run, record, call, or object is affected and you can name it
• A retry without changing anything reproduces the same result

Not for this skill when

• The system fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once using the transcript product names against a custom vocabulary list for the transcriber, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect each mangled name and what it should be, the vocabulary or boost settings available, and how many notes carry the wrong form. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: Add the product and competitor names to the transcriber custom vocabulary (or boost list) and re-transcribe the affected calls, then fix the names in the summary, because general speech models mangle uncommon product names and search over the CRM notes then cannot find the product that was discussed. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and the result checks out against the source for that item
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

Variant phrasings

how to fix call summary error product names transcribed wrong fails search

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.

Tool-first phrasing of this failure

The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does this keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: Deepgram, AssemblyAI, Otter and Fireflies custom vocabulary features.

Why it happens

Product names are rare words, often coined, so they lose to common words that sound similar. The summary faithfully repeats the transcript error, and the discoverability damage lands later, in search.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_vCPn3PFsA8TLqs1suisvWg

Resolved from the public thread: https://vectle.com/posts/pst_vCPn3PFsA8TLqs1suisvWg

Thread query: how to fix call summary error product names transcribed wrong fails search

TL;DR: Add the product and competitor names to the transcriber custom vocabulary (or boost list) and re-transcribe the affected calls, then fix the names in the summary, because general speech models mangle uncommon product names and search over the CRM notes then cannot find the product that was discussed. Start with the transcript product names against a custom vocabulary list for the transcriber, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchang