sync: auto-sync from GURU-5070 at 2026-06-03 11:52:45

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-03 11:52:45

.grok/agents/README.md

@@ -0,0 +1,31 @@
+# .grok/agents/
+
+Grok equivalents / thin adapters for the subagent personas defined in `.claude/agents/`.
+
+**Pattern (same as .grok/skills/ for commands and .claude/skills/):** 
+- Thin files here that say "See the corresponding .claude/agents/<name>.md for the full persona definition and instructions."
+- Adapt for Grok: use `run_terminal_command`, `spawn_subagent`, `search_tool` + `use_tool` (esp. grepai__* for deep exploration), other Grok tools (image/video if relevant).
+- All agents must obey CLAUDE.md (Grok loads it), .grok/README.md, GrepAI-first rule before any direct file reads, and the coexistence rules.
+- Do not edit or duplicate the original .claude/agents/ files.
+
+This keeps single source of truth in .claude/ while giving Grok native discovery for subagents (via .grok/agents/ and project rules).
+
+See .claude/agents/AGENT_QUICK_REFERENCE.md and the individual .md for details.
+
+## Key Grok-adapted agents (full list mirrors .claude/agents/):
+- coding.md
+- deep-explore.md (heavy GrepAI/grepai MCP + trace callers/callees)
+- code-review.md
+- backup.md
+- gitea.md
+- database.md
+- documentation-squire.md
+- testing.md
+- photo.md , video-analysis.md
+- dos-coding.md
+- code-fixer.md
+- And the supporting: CODE_REVIEW_ST_*.md , DATABASE_CONNECTION_INFO.md , AGENT_QUICK_REFERENCE.md
+
+For subagent spawning in Grok, use the `spawn_subagent` tool with the persona from the .grok/ or .claude/ definition (deeper wins or as specified).
+
+See also: .grok/skills/ for the main /command skills, CLAUDE.md for when to use subagents.

.grok/agents/backup.md

@@ -0,0 +1,18 @@
+---
+name: backup
+description: Backup operations custodian.
+---
+
+**Grok agent equivalent.** See `.claude/agents/backup.md` (full custodian for all backups including MSP360/CloudBerry, B2 offsite, RMM agent_backup_status, database, etc.).
+
+For MSP backups removal (e.g. "remove SBS machine from mspbackups" for glaztech client):
+- Auto context load via GrepAI + wiki/clients/glaztech + clients/glaztech/backup docs + B2 skill + RMM mspbackups migrations + .claude/memory/ mspbackups refs.
+- Use .grok/skills/b2/SKILL.md (Grok mirror) to list buckets/keys for the machine's prefix (e.g. in MSPBackups* or ACG-GLAZTECH bucket), then gated delete-key/delete-prefix --confirm for the SBS backup destination.
+- Update RMM if backup status tracked per-agent.
+- Document: session log in client, update wiki if infra change, memory feedback if new lesson.
+- GrepAI-first before any reads; use run_terminal_command for b2.py (py + vault), spawn_subagent if complex.
+
+Grok tools (GrepAI MCP primary, b2 skill, terminal with git-bash, coord for locks) for all backup ops. See .grok/skills/b2/SKILL.md and context skill for MSP example.
+
+Use for all backup/restore with vault aware terminal, GrepAI for context in scripts/configs/memory/wiki.
+

.grok/agents/code-fixer.md

@@ -0,0 +1,8 @@
+---
+name: code-fixer
+description: Autonomous code quality agent that scans and fixes coding violations.
+---
+
+**Grok agent equivalent.** See `.claude/agents/code-fixer.md` and related CODE_REVIEW_ST_*.
+
+Use GrepAI, run tests/builds via terminal, search_replace for fixes, spawn_subagent. Follow review-fix-verify.

.grok/agents/code-review.md

@@ -0,0 +1,12 @@
+---
+name: code-review
+description: Code review agent. Mandatory after changes.
+---
+
+**Grok agent equivalent.** Full persona in `.claude/agents/code-review.md` (and supporting CODE_REVIEW_ST_*).
+
+For Grok: Use GrepAI MCP heavily for diffs/context, run_terminal_command for builds/tests, spawn_subagent, read_file after search.
+
+Enforce the review standards from source + CLAUDE.md + CODING_GUIDELINES.
+
+See .grok/agents/coding.md etc.

.grok/agents/coding.md

@@ -0,0 +1,12 @@
+---
+name: coding
+description: General-purpose coding agent.
+---
+
+**Grok agent equivalent.** See the full definition in `.claude/agents/coding.md`.
+
+Adapt for Grok tools: run_terminal_command (git-bash aware), search_replace/write/read (GrepAI MCP first for context), spawn_subagent, MCP use_tool for grepai etc.
+
+Follow the same coding standards, review-fix-verify loops, etc. from the source and CLAUDE.md / .claude/CODING_GUIDELINES.md (Grok loads the rules).
+
+See also: .grok/agents/code-review.md , code-fixer.md , deep-explore.md .

.grok/agents/database.md

@@ -0,0 +1,10 @@
+---
+name: database
+description: Database transaction authority and single source of truth for data operations.
+---
+
+**Grok agent equivalent.** See `.claude/agents/database.md` and DATABASE_CONNECTION_INFO.md .
+
+Use for DB queries etc. with run_terminal_command (vault for creds), GrepAI searches.
+
+See .claude/agents/DATABASE_CONNECTION_INFO.md .

.grok/agents/deep-explore.md

@@ -0,0 +1,14 @@
+---
+name: deep-explore
+description: Deep codebase exploration using grepai semantic search and call graph tracing. Use this agent for understanding code architecture, finding implementations by intent, analyzing function relationships, and exploring unfamiliar code areas.
+---
+
+**Grok agent equivalent.** See the full persona and instructions in `.claude/agents/deep-explore.md`.
+
+For Grok: Use `search_tool` + `use_tool` (grepai__grepai_search, grepai__grepai_trace_callers, grepai__grepai_trace_callees, grepai__grepai_trace_graph, etc.) as primary for semantic search and call graph (exactly as the source emphasizes "Use GrepAI first").
+
+Then use `read_file` only for full content when needed, `run_terminal_command`, `spawn_subagent`, etc.
+
+Obey CLAUDE.md, GrepAI-first (this agent is the embodiment of it), .grok/README.md .
+
+The core is deep exploration with GrepAI MCP + traces before traditional tools.

.grok/agents/documentation-squire.md

@@ -0,0 +1,10 @@
+---
+name: documentation-squire
+description: Documentation and task management specialist.
+---
+
+**Grok agent equivalent.** See `.claude/agents/documentation-squire.md`.
+
+Grok version for docs, session logs, wiki, memory updates. Use GrepAI, read/write, run for sync etc.
+
+See .grok/README.md for memory/docs coexistence.

.grok/agents/gitea.md

@@ -0,0 +1,10 @@
+---
+name: gitea
+description: Version control custodian for Git and Gitea operations.
+---
+
+**Grok agent equivalent.** See `.claude/agents/gitea.md`.
+
+For Grok: run_terminal_command with git (system ssh, not git's for windows issues), GrepAI for repo context.
+
+Follow git standards in .claude/standards/git/ .

.grok/agents/photo.md

@@ -0,0 +1,8 @@
+---
+name: photo
+description: Image analysis specialist for screenshots, photos, and visual documentation.
+---
+
+**Grok agent equivalent.** See `.claude/agents/photo.md`.
+
+For Grok: use image analysis tools if available, run_terminal_command, GrepAI for related code/docs. Adapt the persona.

.grok/agents/testing.md

@@ -0,0 +1,10 @@
+---
+name: testing
+description: Test execution specialist for running and validating tests.
+---
+
+**Grok agent equivalent.** See `.claude/agents/testing.md`.
+
+For Grok: run_terminal_command for test commands (pytest, cargo test, etc.), GrepAI for test code context, spawn_subagent.
+
+Follow .claude/standards/ for testing.