From 69eb26055dab50b181979351e3f9267ad28d186f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nerijus=20Bend=C5=BEi=C5=ABnas?= Date: Sun, 17 May 2026 08:01:48 +0300 Subject: [PATCH] docs: note hyphenated verb-prefix escape in imperative section MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PR #115 added a third escape clause to check_imperative; section already enumerates the POS-tagger and WordNet-morphy strategies, so list this one alongside them for parity. Signed-off-by: Nerijus Bendžiūnas --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 109932b..cd428b8 100644 --- a/README.md +++ b/README.md @@ -482,11 +482,14 @@ To selectively enable or disable checks, pass `args`: ## Imperative mood detection -commit-guard combines two strategies to detect non-imperative descriptions: +commit-guard combines three strategies to detect non-imperative descriptions: 1. nltk POS tagging — flags words tagged as past tense (`VBD`), gerund (`VBG`), third person (`VBZ`), etc. 2. WordNet morphology as a fallback for words the tagger misclassifies. +3. Hyphenated verb prefixes — accepts `re-enable`, `auto-detect`, + `pre-process`, `co-locate`, `under-mine` and similar + `-` compounds the POS tagger misclassifies. This catches common mistakes like `added logging` or `fixes bug` while keeping false positives low.