Menü
Find discussions and entries related to a specific topic or entry. Use to discover connected context across threads.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | find-related |
| description | Find discussions and entries related to a specific topic or entry. Use to discover connected context across threads. |
| allowed-tools | ["ToolSearch","mcp__watercooler__watercooler_search"] |
Find content related to: $ARGUMENTS
Determine argument type:
01HQXYZ123ABC456DEF789GHJ) — exactly 26 characters matching ^[0-9A-HJKMNP-TV-Z]{26}$ (Crockford base32)For Entry ID — use seeded similarity search:
ToolSearch: select:mcp__watercooler__watercooler_search
Then call:
mcp__watercooler__watercooler_search(seed_entry_id="<ulid>")
For Description — use semantic search:
ToolSearch: select:mcp__watercooler__watercooler_search
Then call:
mcp__watercooler__watercooler_search(query="<description>", mode="entries", semantic=true, code_path="<repo root>")
Present results:
Suggest deeper exploration:
/find-related 01HQXYZ123ABC456DEF789GHI - Find entries similar to this one/find-related git sync conflict resolution - Find related discussions/find-related branch parity implementation - Discover connected contextThis skill should be used to keep CLAUDE.md, AGENTS.md, and the skill files themselves compact, current, and internally consistent. It runs in three phases: Phase 1 performs a one-time structural refactor of CLAUDE.md using a Karpathy-inspired behavioral scaffold and derives AGENTS.md from it by stripping Claude Code-specific sections. Phase 2 extracts durable project conventions from Watercooler Decision entries since the last update and patches a bounded generated section. Phase 3 audits the local skill surface against the live MCP tool surface and the in-process alias registry (`TOOL_ALIASES` in `aliases.py`), surfacing skill files that reference retired or renamed tools. Use when CLAUDE.md has grown verbose or stale, when AGENTS.md has drifted from CLAUDE.md, when significant project decisions have accumulated since the last refresh, or after a watercooler-cloud tool-surface consolidation lands.
Recall project context or answer questions about history and decisions. Use before starting work, when investigating unfamiliar code, or asking "What was decided about X?" / "Why did we choose Y?"
Search threads with filters. Supports filters like role:planner, type:Decision, after:2024-01, thread:topic-name, status:OPEN
List and navigate watercooler threads. Use to see active discussions, find specific threads, or get an overview of project threads.
Check watercooler system health — MCP server, baseline graph (T1), git auth, GitHub rate limit, and daemons. Use when syncs break or anything in the watercooler stack behaves unexpectedly.
Bootstrap Watercooler memory for a repository by inspecting local code, docs, CI, git history, and existing Watercooler threads, then writing a small set of durable, provenance-backed seed threads that future agents can query and extend. Use when entering a repo for the first time, seeding a repo with Watercooler context, or refreshing foundational repository context.