acoustic-carpenter-78188
03/26/2026, 9:02 PM[tool.codespell] section to pyproject.toml with comprehensive skip patterns
• Created GitHub Actions workflow (.github/workflows/codespell.yml) to check spelling on push and PRs
• Configured to skip: .git, .gitignore, .gitattributes, *.lock
Domain-Specific Whitelist
Added legitimate terms that codespell flags as typos:
• ot — variable name for output type in tests
• nd — NamedDelivery variable in tests
• crasher — legitimate word in stress test examples
• tru — intentional truncated JSON in test fixture
• nome — timezone name "America/Nome"
• lits — variable short for "literals"
• rouge — NLP scoring metric (not "rogue")
Typo Fixes
Ambiguous typos fixed manually (3 fixes with context review):
• respones → responses (examples/interactive/interactive.ipynb)
• replacas → replicas (examples/reuse/errors.py, examples/reuse/reusable.py)
Non-ambiguous typos fixed automatically (14 fixes in 10 files):
• optimial → optimal, Thne → Then, handel → handle (×5),
pre-pending → prepending, infact → in fact, agregate → aggregate,
langauge → language, orignal → original, propogated → propagated,
wihtin → within
Potential Functional Fix
• handel → `handle`: renamed method PoetryProjectHandler.handel() and all its call sites — this was a misspelled method name that could cause issues if anyone tried to call .handle() by the correct name.
@yarikoptic got intrigued -- are those tests part of CI at all?
Historical Context
This project has had 10+ prior commits fixing typos manually, demonstrating the value of automated spell-checking.
Testing
Codespell passes with zero errors after all fixes.
---
🤖 Generated with Claude Code and love to typos free code
flyteorg/flyte-sdkacoustic-carpenter-78188
04/06/2026, 1:58 PM