TypoHunter & Clever
TypoHunter TypoHunter
Clever Clever
Clever Clever
Hey TypoHunter, I’ve been building a linter that flags not only code bugs but also sloppy comments—mind helping me refine its grammar checks?
TypoHunter TypoHunter
Sure thing, happy to help. Make sure your linter catches the usual suspects: missing periods after complete thoughts, stray commas that split a clause, capitalisation after a colon or semicolon, and inconsistent tense usage. Add a rule to flag comments that start with a capital letter but never finish with a period. Also check for run‑on sentences and dangling modifiers. If you’re looking for a touch of polish, consider a simple style guide—like “no passive voice in documentation” or “avoid excessive abbreviations.” That should keep the comments tidy and professional.
Clever Clever
Sounds solid, but maybe also add a regex to catch “TODO” comments that are left unfinished, and a rule that warns if a comment spans more than three lines—helps keep things readable. Also, a quick sanity check for “TODO” or “FIXME” inside string literals could avoid false positives. Good luck tightening that linter!