Merge remote-tracking branch 'origin/dev'

Author: github-actions[bot]

.claude/skills/dale/rules/exclamatory-sentences.yml

@@ -0,0 +1,3 @@
+message: "Don't use exclamatory sentences."
+level: warning
+reason: "This rule should trigger when the user or agent writes exclamatory sentences."

.claude/skills/dale/rules/idioms.yml

@@ -0,0 +1,3 @@
+message: "Don't use idioms. Write what you mean more directly and literally."
+level: warning
+reason: "This rule should trigger when the user or agent uses an idiom or other culturally specific expression."

.claude/skills/dale/rules/misplaced-modifiers.yml

@@ -0,0 +1,3 @@
+message: "Avoid misplaced modifiers. Move the modifier, or descriptive phrase, so that it accurately describes the right thing."
+level: warning
+reason: "This rule should trigger when the documentation has a misplaced or dangling modifier. This includes participial phrases that attach to the wrong subject (e.g., '[participle phrase], [wrong subject] [verb]') and modifying clauses placed too far from the word they describe (e.g., '[noun A] [preposition] [noun B] [modifier that actually describes noun A]')."

.claude/skills/dale/rules/passive-voice.yml

@@ -0,0 +1,3 @@
+message: "Don't use passive voice. Use active voice instead."
+level: warning
+reason: "This rule should trigger when the user or agent writes a sentence or clause in passive voice."

.claude/skills/dale/rules/positional-references.yml

@@ -0,0 +1,3 @@
+message: "Avoid positional references like 'below', 'above', or 'as shown below'. Use 'the following' or a named anchor instead."
+level: warning
+reason: "This rule should trigger when the documentation uses spatial direction words like 'below', 'above', 'as shown below', or 'the above section' to reference other content."

.claude/skills/dale/rules/wordiness.yml

@@ -0,0 +1,3 @@
+message: "This sentence is wordy. A more concise, direct alternative is possible."
+level: warning
+reason: "This rule should trigger when the user or agent writes a wordy sentence when a more concise, direct alternative is possible without altering the meaning."

.claude/skills/doc-help/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: doc-help
-description: "Interactive writing assistant for Netwrix documentation. Use when a writer wants hands-on, conversational help: brainstorming structure, drafting a section, editing existing content, or understanding a style or Vale rule. For fully autonomous tasks (write this entire doc, fix all Vale errors end-to-end), use the tech-writer agent instead."
+description: "Interactive writing assistant for Netwrix documentation. Use when a writer wants hands-on, conversational help: brainstorming structure, drafting a section, editing existing content, incorporating external documents (e.g., .docx files) into existing markdown files, or understanding a style or Vale rule. For fully autonomous tasks (write this entire doc, fix all Vale errors end-to-end), use the tech-writer agent instead."
 argument-hint: "[topic, file path, content to edit, or question]"
 ---
 
@@ -14,6 +14,7 @@ Read `docs/CLAUDE.md` before starting any session. It contains the Netwrix style
 
 - User invokes `/doc-help` with or without arguments
 - User asks for help writing, editing, or reviewing Netwrix documentation
+- User asks to incorporate, merge, or integrate content from an external document (e.g., `.docx`) into an existing markdown file
 - User has a question about a style rule, Vale error, or Netwrix writing convention
 
 ## Stage 1: Intake

CLAUDE.md

@@ -82,7 +82,7 @@ PRs target `dev`. Never commit directly to `dev` or `main`. The `sync-dev-to-mai
 Skills (`.claude/skills/`) are invoked with `/skill-name`. Agents (`.claude/agents/`) are autonomous workers launched via the Agent tool.
 
 When a user asks for help with documentation, always use the appropriate tool:
-- **`/doc-help` skill** — Interactive tasks: reviewing content, suggesting improvements, discussing structure or flow, brainstorming, explaining style rules, or any back-and-forth conversation about writing.
+- **`/doc-help` skill** — Interactive tasks: reviewing content, suggesting improvements, discussing structure or flow, brainstorming, explaining style rules, incorporating external documents (e.g., `.docx` files) into existing markdown files, or any back-and-forth conversation about writing.
 - **`tech-writer` agent** — Autonomous end-to-end tasks: drafting new documents, rewriting files, fixing all Vale errors, or editing for style and clarity.
 
 | Component | Type | Purpose |

docs/auditor/10.8/admin/riskassessment/dashboard.md

@@ -59,6 +59,10 @@ Also, for several metrics the Customize risk indicators command is available.
 | Servers with unauthorized antivirus software    | Edit the whitelist of permitted antivirus tools. Any other antivirus will be considered a risk factor.                                               |
 | Administrative group membership sprawl          | Edit the whitelist of permitted accounts that can be the members of local administrative groups. Any other account will be considered a risk factor. |
 
+**Note:** Special characters such as %, *, and ? are not interpreted as wildcards in risk indicator customization and are treated as literal characters. The only exception is the domain portion of
+domain\account entries in Administrative group membership sprawl, where % can be used to represent any domain. In all other cases (for example, account names, file names, operating system names, and antivirus names),
+values must be entered explicitly and are not matched using wildcard patterns.
+
 New settings will be applied/risk level thresholds will be refreshed after the next data collection
 session.