Fix CI and remaining context-tools references

- Update CI workflow to install context-daddy (not context-tools)
- Update session-start.sh plugin name and MCP tool references
- Update SKILL.md files
- Update test-hooks.yml and e2e-test.yml

Co-developed-by: Claude Code v2.1.12 (claude-opus-4-5-20251101)

Author: robtaylor

.claude-plugin/SKILL.md

@@ -43,8 +43,8 @@ The MCP server will restart with the new plugin configuration.
 ```
 
 **When to give this instruction:**
-- Immediately after the user runs `/plugin install context-tools`
-- Immediately after the user runs `/plugin update context-tools`
+- Immediately after the user runs `/plugin install context-daddy`
+- Immediately after the user runs `/plugin update context-daddy`
 - When the user tries to use MCP tools but they're not available (and you suspect they just installed)
 
 **Why this matters:**

.github/workflows/ci.yml

@@ -486,8 +486,8 @@ jobs:
 
       - name: Install plugin
         run: |
-          echo "Installing context-tools plugin..."
-          claude plugin install context-tools
+          echo "Installing context-daddy plugin..."
+          claude plugin install context-daddy
           echo "Plugin installed successfully"
 
       - name: Test plugin loads with --plugin-dir

.github/workflows/e2e-test.yml

@@ -10,7 +10,7 @@ jobs:
   check-secrets:
     name: Check if secrets are available
     runs-on: ubuntu-latest
-    if: ${{ github.repository == 'ChipFlow/claude-context-tools' }}
+    if: ${{ github.repository == 'ChipFlow/context-daddy' }}
     outputs:
       has-api-key: ${{ steps.check.outputs.has-api-key }}
     steps:

.github/workflows/test-hooks.yml

@@ -112,12 +112,12 @@ jobs:
             echo "⚠️  project-manifest.json not created (hook may not have triggered generate-manifest)"
           fi
 
-          # Check if Claude mentioned anything about context-tools or project context
+          # Check if Claude mentioned anything about context-daddy or project context
           # The systemMessage goes to Claude's context, so Claude might reference it
-          if grep -qi "context-tools\|repo.map\|mcp\|symbol" session-start-output.txt; then
-            echo "✅ Claude appears to have received context-tools context"
+          if grep -qi "context-daddy\|repo.map\|mcp\|symbol" session-start-output.txt; then
+            echo "✅ Claude appears to have received context-daddy context"
           else
-            echo "⚠️  Claude response doesn't mention context-tools features"
+            echo "⚠️  Claude response doesn't mention context-daddy features"
           fi
 
           # Check for .claude directory (created by hook)

SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: context-tools
+name: context-daddy
 description: Context management tools for Claude Code - provides intelligent codebase mapping with Python, Rust, and C++ parsing, duplicate detection, and MCP-powered symbol queries. Use this skill when working with large codebases that need automated indexing and context management.
 ---
 
@@ -45,9 +45,9 @@ Am I searching for code symbols (functions, classes, enums, structs, types)?
 - Cross-file text pattern searches
 
 **Tool availability check:**
-Before attempting to use MCP tools (mcp__plugin_context-tools_repo-map__*), check if `.claude/repo-map.db` exists:
+Before attempting to use MCP tools (mcp__plugin_context-daddy_repo-map__*), check if `.claude/repo-map.db` exists:
 - If YES: Try the MCP tool. If it fails (not available), use sqlite3 fallback.
-- If NO: The project hasn't been indexed yet. Either wait for indexing or run `/context-tools:repo-map` to generate it.
+- If NO: The project hasn't been indexed yet. Either wait for indexing or run `/context-daddy:repo-map` to generate it.
 
 **Fallback order:**
 1. Try MCP tool first
@@ -66,7 +66,7 @@ Problems: Slow, error-prone pattern matching, gets interrupted on large codebase
 
 **Efficient approach** (DO THIS):
 ```
-mcp__plugin_context-tools_repo-map__search_symbols
+mcp__plugin_context-daddy_repo-map__search_symbols
 pattern: "setup_*"
 ```
 Result: Instant list of all `setup_model`, `setup_instance`, etc. with locations and signatures.
@@ -80,13 +80,13 @@ find . -name "*.py" -exec grep -l "class.*Config" {} \;
 
 **Efficient approach** (DO THIS):
 ```
-mcp__plugin_context-tools_repo-map__search_symbols
+mcp__plugin_context-daddy_repo-map__search_symbols
 pattern: "*Config*"
 kind: "class"
 ```
 Then get the source:
 ```
-mcp__plugin_context-tools_repo-map__get_symbol_content
+mcp__plugin_context-daddy_repo-map__get_symbol_content
 name: "ConfigLoader"
 ```
 
@@ -99,7 +99,7 @@ grep "^def " src/utils.py
 
 **Efficient approach** (DO THIS):
 ```
-mcp__plugin_context-tools_repo-map__get_file_symbols
+mcp__plugin_context-daddy_repo-map__get_file_symbols
 file: "src/utils.py"
 ```
 Result: Complete list of all functions/classes with signatures and docstrings.
@@ -117,10 +117,10 @@ Problems: Multiple searches, manual parsing, easy to miss correct variant.
 
 **Efficient approach** (DO THIS):
 ```
-mcp__plugin_context-tools_repo-map__search_symbols
+mcp__plugin_context-daddy_repo-map__search_symbols
 pattern: "InstructionData"
 
-mcp__plugin_context-tools_repo-map__get_symbol_content
+mcp__plugin_context-daddy_repo-map__get_symbol_content
 name: "InstructionData"
 ```
 Result: Complete enum with all variants visible, including `PhiNode(_)`.
@@ -129,11 +129,11 @@ Result: Complete enum with all variants visible, including `PhiNode(_)`.
 
 **IMPORTANT**: If the user has just installed this plugin:
 
-> "I see you've installed the context-tools plugin. The MCP server should auto-configure on restart. After restarting Claude Code, run `/mcp` to verify the `repo-map` server is loaded.
+> "I see you've installed the context-daddy plugin. The MCP server should auto-configure on restart. After restarting Claude Code, run `/mcp` to verify the `repo-map` server is loaded.
 >
-> If it doesn't load automatically, let me know and I can help troubleshoot using `/context-tools:setup-mcp`."
+> If it doesn't load automatically, let me know and I can help troubleshoot using `/context-daddy:setup-mcp`."
 
-The MCP server auto-configures from the plugin manifest. Only if auto-config fails should you run `/context-tools:setup-mcp` for troubleshooting.
+The MCP server auto-configures from the plugin manifest. Only if auto-config fails should you run `/context-daddy:setup-mcp` for troubleshooting.
 
 ## Included Components
 
@@ -180,25 +180,25 @@ Keys:
 - **Behavior**: Most tools wait for completion, repo_map_status does not (use to check progress)
 
 **Available MCP Tools:**
-- `mcp__plugin_context-tools_repo-map__search_symbols` - Search symbols by pattern (supports glob wildcards)
+- `mcp__plugin_context-daddy_repo-map__search_symbols` - Search symbols by pattern (supports glob wildcards)
   - Returns: name, kind, signature, file_path, line_number, docstring, parent
   - **AUTO-WAIT**: If indexing is in progress, automatically waits up to 60s for completion
-- `mcp__plugin_context-tools_repo-map__get_file_symbols` - Get all symbols in a specific file
+- `mcp__plugin_context-daddy_repo-map__get_file_symbols` - Get all symbols in a specific file
   - Returns: All symbols with full metadata
   - **AUTO-WAIT**: If indexing is in progress, automatically waits up to 60s for completion
-- `mcp__plugin_context-tools_repo-map__get_symbol_content` - Get full source code of a symbol by exact name
+- `mcp__plugin_context-daddy_repo-map__get_symbol_content` - Get full source code of a symbol by exact name
   - Returns: symbol metadata + content (source code text) + location
   - **AUTO-WAIT**: If indexing is in progress, automatically waits up to 60s for completion
-- `mcp__plugin_context-tools_repo-map__list_files` - List all indexed files, optionally filtered by glob pattern
+- `mcp__plugin_context-daddy_repo-map__list_files` - List all indexed files, optionally filtered by glob pattern
   - Returns: list of file paths matching pattern (e.g., "*.va", "*psp103*", "**/devices/*")
   - **MUCH faster than find/ls** - queries pre-built index instead of filesystem traversal
   - **AUTO-WAIT**: If indexing is in progress, automatically waits up to 60s for completion
-- `mcp__plugin_context-tools_repo-map__reindex_repo_map` - Trigger manual reindex
+- `mcp__plugin_context-daddy_repo-map__reindex_repo_map` - Trigger manual reindex
   - Does NOT auto-wait (use to force reindex)
-- `mcp__plugin_context-tools_repo-map__repo_map_status` - Check indexing status and staleness
+- `mcp__plugin_context-daddy_repo-map__repo_map_status` - Check indexing status and staleness
   - Returns: index_status (idle/indexing/completed/failed), symbol_count, last_indexed, indexing_duration_seconds
   - Does NOT auto-wait (use to check status)
-- `mcp__plugin_context-tools_repo-map__wait_for_index` - Explicitly wait for indexing to complete
+- `mcp__plugin_context-daddy_repo-map__wait_for_index` - Explicitly wait for indexing to complete
   - Takes: timeout_seconds (default: 60)
   - Returns: success (bool), message (str)
   - Use when you want to wait longer than the default 60s auto-wait timeout
@@ -215,10 +215,10 @@ sqlite3 .claude/repo-map.db "SELECT * FROM symbols WHERE name = 'function_name'"
 ```
 
 ### Slash Commands
-- `/context-tools:repo-map` - Regenerate repository map
-- `/context-tools:manifest` - Refresh project manifest
-- `/context-tools:learnings` - Manage project learnings
-- `/context-tools:status` - Show plugin status
+- `/context-daddy:repo-map` - Regenerate repository map
+- `/context-daddy:manifest` - Refresh project manifest
+- `/context-daddy:learnings` - Manage project learnings
+- `/context-daddy:status` - Show plugin status
 
 ## Language Support
 

scripts/session-start.sh

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# Session Start Hook for context-tools plugin
+# Session Start Hook for context-daddy plugin
 # Outputs JSON with systemMessage (shown to user) and context for Claude
 # NOTE: Indexing is now handled by the MCP server - no subprocess spawning here
 
@@ -105,18 +105,18 @@ if [[ "${INDEXING_STATUS}" == "indexing" ]]; then
     CONTEXT="${CONTEXT}\n• Most tools auto-wait up to 15 seconds, then return progress info"
 elif [[ -f "${DB_FILE}" ]]; then
     # Ready to use
-    CONTEXT="${CONTEXT}\n\n✅ **Repo map ready: ${SYMBOL_COUNT} symbols indexed** - context-tools MCP guaranteed to work!"
+    CONTEXT="${CONTEXT}\n\n✅ **Repo map ready: ${SYMBOL_COUNT} symbols indexed** - context-daddy MCP guaranteed to work!"
     CONTEXT="${CONTEXT}\n\n🎯 **MANDATORY FIRST ACTION**: Verify MCP tools work by running ONE of these NOW:"
-    CONTEXT="${CONTEXT}\n   • mcp__plugin_context-tools_repo-map__list_files(pattern=\"*.py\") - see indexed Python files"
-    CONTEXT="${CONTEXT}\n   • mcp__plugin_context-tools_repo-map__search_symbols(pattern=\"*\", limit=5) - see available symbols"
+    CONTEXT="${CONTEXT}\n   • mcp__plugin_context-daddy_repo-map__list_files(pattern=\"*.py\") - see indexed Python files"
+    CONTEXT="${CONTEXT}\n   • mcp__plugin_context-daddy_repo-map__search_symbols(pattern=\"*\", limit=5) - see available symbols"
     CONTEXT="${CONTEXT}\n   This takes <1 second and proves the tools work in THIS project. Do it before any other work."
     CONTEXT="${CONTEXT}\n\n⚡ **BEFORE using Search/Grep/Glob/find/ls for code**: ALWAYS try MCP tools first."
     CONTEXT="${CONTEXT}\n• Finding enum/struct/class definition? → search_symbols(\"TypeName\") then get_symbol_content(\"TypeName\")"
     CONTEXT="${CONTEXT}\n• Finding functions by pattern? → search_symbols(\"setup_*\") or search_symbols(\"*Handler\")"
     CONTEXT="${CONTEXT}\n• What's in a file? → get_file_symbols(\"path/to/file.rs\")"
     CONTEXT="${CONTEXT}\n• Finding files? → list_files(\"*.py\") or list_files(\"*ring*\") - faster than Search/find/ls"
     CONTEXT="${CONTEXT}\n• 10-100x faster than Search/Grep/find/ls. Use MCP tools for code, grep only for text/comments."
-    CONTEXT="${CONTEXT}\n• /context-tools:mcp-help for detailed examples showing MCP vs Search tool usage."
+    CONTEXT="${CONTEXT}\n• /context-daddy:mcp-help for detailed examples showing MCP vs Search tool usage."
 elif [[ -f "${REPO_MAP}" ]]; then
     CONTEXT="${CONTEXT}\nRepo map available with ${SYMBOL_COUNT} symbols in .claude/repo-map.md"
 fi