fix: address remaining CodeRabbit review feedback on PR #35

- chief-of-staff: declare `mcp__slack__conversations_add_message` in
  frontmatter; it is referenced in the body at line 102 (send action)
  and would otherwise be unavailable at runtime
- .coderabbit.yaml: clarify that skill "When to Use"/"Ideal For" sections
  live in the document body (not frontmatter); tighten shell-script
  guidance to `set -euo pipefail`

Not changed (disputed):
- MCP tool naming convention remains `mcp__<server>__<tool>` (double
  underscore) — matches existing usage across chief-of-staff, docs-lookup,
  and gan-evaluator; single-underscore variant would break all current
  agents
- `replace` and `save_memory` kept in the built-in allow-list — this
  PR itself proves `replace` is valid (it is the fix for #34); the
  CodeRabbit web-search result claiming they are deprecated is
  inconsistent with the Gemini CLI version this repo targets

Author: Jamkris

.coderabbit.yaml

@@ -54,18 +54,19 @@ reviews:
         is consistent and shell snippets are safely quoted.
     - path: "skills/**/*.md"
       instructions: |
-        Skill definitions. Check that frontmatter includes `name` and `description`,
-        and that "When to Use" / "Ideal For" sections are present and specific.
+        Skill definitions. Frontmatter must include `name` and `description`.
+        The document body (not the frontmatter) should contain a "When to Use"
+        or "Ideal For" section with specific, actionable trigger conditions.
     - path: "hooks/**"
       instructions: |
         Hook scripts and hooks.json. Hooks run automatically on tool events —
         any failure impacts all sessions. Verify error handling, quiet logging,
         and that exit codes are intentional.
     - path: "scripts/**"
       instructions: |
-        Shell scripts must use `set -e`, quote all variables, and avoid
-        interpolating shell variables into `node -e` strings (use `process.env`
-        instead). JS scripts target Node.js 20+.
+        Shell scripts must use `set -euo pipefail`, quote all variables, and
+        avoid interpolating shell variables into `node -e` strings (use
+        `process.env` instead). JS scripts target Node.js 20+.
     - path: "rules/**/*.md"
       instructions: |
         Coding rules shipped to end users' ~/.gemini/rules/. Cross-references

agents/chief-of-staff.md

@@ -1,7 +1,7 @@
 ---
 name: chief-of-staff
 description: Personal communication chief of staff that triages email, Slack, LINE, and Messenger. Classifies messages into 4 tiers (skip/info_only/meeting_info/action_required), generates draft replies, and enforces post-send follow-through via hooks. Use when managing multi-channel communication workflows.
-tools: ["read_file", "search_file_content", "list_directory", "run_shell_command", "replace", "write_file", "mcp__slack__conversations_search_messages", "mcp__slack__channels_list", "mcp__slack__conversations_history"]
+tools: ["read_file", "search_file_content", "list_directory", "run_shell_command", "replace", "write_file", "mcp__slack__conversations_search_messages", "mcp__slack__channels_list", "mcp__slack__conversations_history", "mcp__slack__conversations_add_message"]
 ---
 
 You are a personal chief of staff that manages all communication channels — email, Slack, LINE, Messenger, and calendar — through a unified triage pipeline.