dive-prep

Gather local documents and repository state into a .wm/dive_context.md file.

3|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/open-horizon-labs/bottle --skill dive-prep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dive-prep
Source: https://github.com/open-horizon-labs/bottle/tree/main/.claude-plugin/plugins/wm/skills/dive-prep
Command: npx skills add https://github.com/open-horizon-labs/bottle --skill dive-prep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dive prep reduces ambiguity at the start of an AI session by gathering relevant context from multiple sources and surfacing a grounded context file for the agent to use.

Core Features & Use Cases

  • Context gathering: Collects local documents (CLAUDE.md, git state) and OH context when available.
  • Grounding file generation: Writes .wm/dive_context.md with curated grounding for the session.
  • Deterministic agent spawning: Uses the Task tool to spawn the wm:dive-prep agent with a user intent or context.
  • Use Case: Before tackling a complex bug, run this skill to assemble sources and establish a grounded starting point.

Quick Start

Invoke the skill with /wm:dive-prep [intent or context]. Use the Task tool to spawn the wm:dive-prep agent: Task(subagent_type: "wm:dive-prep", prompt: "<user's intent or context>") If the user provides a GitHub issue URL, include it in the prompt: Task(subagent_type: "wm:dive-prep", prompt: "Prepare dive for https://github.com/org/repo/issues/123")

Frequently Asked Questions about dive-prep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare grounding context for an AI coding session?

Grounding context for focused AI sessions is prepared by gathering local documents, repository state, and OH context into a curated dive_context.md file that reduces ambiguity and gives the agent reliable working memory.

What is the best way to ground an AI agent before debugging a complex issue?

The best way to ground an agent before debugging is to assemble local documents, git state, and OH context into a single dive_context.md file, establishing a deterministic starting point that reduces session ambiguity.

Can I use context management to spawn a deterministic agent in Claude Code?

Yes, context management allows you to spawn a deterministic agent in Claude Code by using the Task tool to invoke the wm:dive-prep agent with a specific user intent or context, bypassing direct shell commands.

How do I generate a context file from a GitHub issue for an AI dive?

You can generate a context file from a GitHub issue by invoking the dive-prep skill with the issue URL included in the prompt, which gathers repository state and outputs a grounded dive_context.md file.

Does dive-prep work with Open Code and Codex sessions?

Yes, dive-prep applies to Claude Code, Codex, and Open Code sessions that require reliable grounding from local documents and repository state to establish a focused working context.

Why do I need a grounding file for AI task spawning?

A grounding file is needed for AI task spawning to reduce ambiguity at the start of a session, surfacing curated context from multiple sources so the agent operates with reliable working memory.