chore: add spell check step to code-smell command

Runs cspell before structural analysis. Reports unknown words at Smell
severity. Points to .cspell.json for adding project-specific terms.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

Author: Devesh-Skyflow

.claude/commands/code-smell.md

@@ -1,6 +1,6 @@
 ---
 name: code-smell
-description: Standalone structural smell analysis — long methods, dead code, misplaced validation, deep nesting, magic numbers. Does not check patterns or security.
+description: Structural smell analysis + spell check — long methods, dead code, misplaced validation, deep nesting, magic numbers. Does not check patterns or security.
 paths:
   - src/main/java/**/*.java
 ---
@@ -20,6 +20,18 @@ Use `$ARGUMENTS` to determine scope:
 
 ---
 
+## Spell check
+
+Before analysing smells, run cspell on the files in scope:
+
+```bash
+npx cspell --no-progress "src/**/*.java" ".claude/**/*.md" "CLAUDE.md" "docs/**/*.md" 2>&1 | grep "Unknown word"
+```
+
+Report any spelling violations at **Smell** severity in the per-file table. The word list is in `.cspell.json` — add legitimate project-specific terms there rather than fixing them as typos.
+
+---
+
 ## What Are Code Smells
 
 Code smells are structural signals — they do not necessarily mean the code is broken, but they indicate areas of technical debt, reduced readability, or future maintenance risk. All findings are reported at **Smell** severity and do not block merge unless they indicate a design violation.