Avoid using abusive words

Validate the entire commit message for abusive language. Only a small
set of abusive words was detected.

Change-Id: Ib59b2c04f7edfc34fd68873dc58df1419be49b95

Author: jserv

scripts/commit-msg.hook

@@ -282,16 +282,29 @@ validate_commit_message() {
 
   word_count=$(echo "$COMMIT_SUBJECT_TO_PROCESS" | wc -w)
   test "$word_count" -gt 1
-  test $? -eq 0 || add_warning 1 "Commit subject should contain more than one word (e.g. 'Update dependencies' instead of 'Update')"
+  test $? -eq 0 || add_warning 1 "Commit subject should contain more than one word. Summarize your changes"
 
   # 11. Avoid commit subject that simply states a file update (e.g. "Update console.c")
+  # ------------------------------------------------------------------------------
+
   if [[ $COMMIT_SUBJECT_TO_PROCESS =~ ^Update[[:space:]]+([^[:space:]]+)$ ]]; then
     candidate="${BASH_REMATCH[1]}"
     # Only warn if the candidate filename ends with .c or .h
     if [[ $candidate =~ \.(c|h)$ ]]; then
       add_warning 1 "Avoid using just a filename like '$candidate'. Provide a functional, meaningful description"
     fi
   fi
+
+  # 12. Avoid abusive language in commit message content
+  # ------------------------------------------------------------------------------
+
+  FULL_COMMIT_MSG=$(sed '/^#/d;/^[[:space:]]*$/d' "$COMMIT_MSG_FILE")
+  # Extended list of abusive words (case-insensitive).
+  # Adjust the list as needed.
+  ABUSIVE_WORDS_REGEX='\b(fuck|fucking|dick|shit|bitch|asshole|cunt|motherfucker|damn|crap|dumbass|piss)\b'
+  if echo "$FULL_COMMIT_MSG" | grep -Eiq "$ABUSIVE_WORDS_REGEX"; then
+    add_warning 1 "Commit message contains inappropriate language. Avoid using abusive words"
+  fi
 }
 
 unset GREP_OPTIONS