opencodekit 0.20.7 → 0.20.8

package/dist/template/.opencode/skill/beads-bridge/SKILL.md

@@ -1,321 +0,0 @@
----
-name: beads-bridge
-description: >
-  Multi-agent task coordination using br (beads_rust) and OpenCode tools. Use when work spans multiple sessions,
-  has dependencies, needs file locking, or requires agent coordination. Covers claim/reserve/done cycle,
-  dependency management, hierarchical decomposition, and session protocols.
-version: "2.0.0"
-license: MIT
-tags: [agent-coordination, workflow]
-dependencies: [beads]
----
-
-# Beads Bridge - Cross-Session Task Coordination
-
-## When to Use
-
-- Work spans multiple sessions and needs persistent task tracking
-- Multiple agents must coordinate via Beads, swarm, and OpenCode todos
-
-## When NOT to Use
-
-- Single-session, single-agent work with no dependencies
-- Simple tasks that don’t require Beads or swarm coordination
-
-## Overview
-
-**Beads Bridge = Beads (br) + OpenCode Todos + Swarm Monitor**
-
-- **Beads (br)**: Git-backed task tracking with dependency management
-- **OpenCode Todos**: Native session-scoped task lists for subagents
-- **Swarm Monitor**: Real-time progress tracking (visualization only)
-
-**Key Tools**:
-
-| Tool    | Purpose                     | When to Use                                          |
-| ------- | --------------------------- | ---------------------------------------------------- |
-| `swarm` | Unified swarm coordination  | All swarm operations (sync, monitor, plan, delegate) |
-| `Task`  | Parallel subagent execution | Spawning worker swarms                               |
-
-**swarm operations:**
-
-- `sync`: Sync Beads ↔ OpenCode todos (start of session, before spawning)
-- `monitor`: Progress tracking/visualization (during swarm execution)
-- `plan`: Task classification + dependency graphs (before spawning workers)
-- `delegate`: Create delegation packets (assigning work to workers)
-
-## Core Workflows
-
-### 1. Session Start: Load Beads into Todos
-
-Make Beads tasks visible to subagents:
-
-```typescript
-// Push Beads to OpenCode todos
-const result = await swarm({
-  operation: "sync",
-  action: "push",
-  filter: "open", // or "in_progress", "all"
-});
-
-// Subagents can now use todoread to see tasks
-// [Bead] task-title will appear in their todo list
-```
-
-### 2. Check Swarm Status
-
-Check current swarm progress:
-
-```typescript
-// Check swarm status
-const status = await swarm({
-  operation: "monitor",
-  action: "status",
-  team_name: "api-refactor-swarm",
-});
-
-const stats = JSON.parse(status).summary;
-console.log(`Workers: ${stats.total_workers}, Completed: ${stats.completed}`);
-
-// Render TUI for visualization
-const ui = await swarm({
-  operation: "monitor",
-  action: "render_block",
-  team_name: "api-refactor-swarm",
-});
-console.log(ui);
-```
-
-### 3. Shared Task Lists for Cross-Session Work
-
-For work that spans multiple sessions, use shared task lists:
-
-```typescript
-// Create a shared list that persists across sessions
-const list = await swarm({
-  operation: "sync",
-  action: "create_shared",
-  name: "api-refactor-swarm",
-  tasks: JSON.stringify([
-    { id: "task-1", content: "Refactor auth endpoint", status: "pending", priority: "high" },
-    { id: "task-2", content: "Update user routes", status: "pending", priority: "medium" },
-  ]),
-});
-
-// Workers update the shared list as they complete work
-await swarm({
-  operation: "sync",
-  action: "update_shared",
-  list_id: list.list_id,
-  tasks: JSON.stringify([{ id: "task-1", status: "completed" }]),
-});
-```
-
-### 4. Create Shared Task Lists for Swarms
-
-Create persistent task lists that survive session boundaries:
-
-```typescript
-// Create a shared list for a swarm
-const list = await swarm({
-  operation: "sync",
-  action: "create_shared",
-  name: "api-refactor-swarm",
-  tasks: JSON.stringify([
-    { id: "task-1", content: "Refactor auth endpoint", status: "pending", priority: "high" },
-    { id: "task-2", content: "Update user routes", status: "pending", priority: "medium" },
-    { id: "task-3", content: "Fix validation", status: "pending", priority: "medium" },
-  ]),
-});
-
-// Share the list ID with workers
-console.log(`List ID: ${list.list_id}`);
-// Workers can access via: swarm({ operation: "sync", action: "get_shared", list_id: "..." })
-```
-
-### 5. Worker Updates to Shared List
-
-Workers can update their task status:
-
-```typescript
-// Worker completes a task
-await swarm({
-  operation: "sync",
-  action: "update_shared",
-  list_id: "shl_abc123",
-  tasks: JSON.stringify([{ id: "task-1", status: "completed" }]),
-});
-```
-
-## Integration Patterns
-
-### Pattern A: Beads → Swarm → Beads
-
-Full cycle from Beads task to swarm execution and back:
-
-```typescript
-// 1. Start: Push Beads to todos
-await swarm({ operation: "sync", action: "push" });
-
-// 2. Claim the parent Bead
-await bash("br update parent-task --status in_progress");
-
-// 3. Analyze and spawn swarm
-const analysis = await swarm({
-  operation: "plan",
-  action: "analyze",
-  task: "Implement API refactor",
-  files: "src/api/users.ts,src/api/posts.ts,src/api/auth.ts",
-});
-
-// 4. Execute swarm (see swarm-coordination skill)
-// ... spawn workers, monitor progress ...
-
-// 5. Complete: Pull completed todos back to Beads
-await swarm({ operation: "sync", action: "pull" });
-
-// 6. Clear swarm state
-await swarm({
-  operation: "monitor",
-  action: "clear",
-  team_name: "api-refactor-swarm",
-});
-
-// 7. Close parent Bead and sync
-await bash("br close parent-task --reason 'Swarm completed all subtasks'");
-await bash("br sync --flush-only");
-await bash("git add .beads/ && git commit -m 'close parent-task'");
-```
-
-### Pattern B: Dependency-Aware Task Scheduling
-
-Use swarm tool's dependency graph for proper ordering:
-
-```typescript
-// Get full analysis with dependency graph
-const analysis = await swarm({
-  operation: "plan",
-  action: "analyze",
-  task: "Refactor authentication system",
-  files: "src/auth/service.ts,src/auth/types.ts,src/routes/auth.ts,src/middleware/auth.ts",
-});
-
-const plan = JSON.parse(analysis);
-
-// Use parallelizable_groups for spawn order
-for (const group of plan.dependency_graph.parallelizable_groups) {
-  // Spawn all tasks in this group in parallel
-  for (const taskId of group) {
-    const node = plan.dependency_graph.nodes.find((n) => n.id === taskId);
-    Task({
-      subagent_type: "general",
-      description: `Execute ${taskId}`,
-      prompt: `Execute task ${taskId}: ${node.content}
-      
-Files: ${node.assignedFiles.join(", ")}
-Blocked by: ${node.blockedBy.join(", ") || "none"}
-Team: auth-refactor-swarm
-Worker: ${node.worker}`,
-    });
-  }
-
-  // Wait for this group to complete before starting next
-  // (dependency ordering)
-}
-```
-
-### Pattern C: Cross-Session Handoff
-
-When work needs to continue in a new session:
-
-```typescript
-// End of session 1: Save state to memory and shared list
-await swarm({
-  operation: "sync",
-  action: "update_shared",
-  list_id: "api-refactor-swarm",
-  tasks: JSON.stringify([
-    { id: "worker-1", content: "Auth service", status: "completed" },
-    { id: "worker-2", content: "User routes", status: "completed" },
-    { id: "worker-3", content: "Validation", status: "in_progress" },
-  ]),
-});
-
-await memory_update({
-  file: "handoffs/swarm-state",
-  content: `
-## Swarm Handoff
-
-Team: api-refactor-swarm
-Progress: 60% complete (3/5 workers done)
-Remaining: worker-4 (blocked), worker-5 (pending)
-Blockers: worker-4 needs auth types from worker-1
-
-Next steps:
-1. Check shared task list for current status
-2. Unblock worker-4 with completed types
-3. Spawn remaining workers
-`,
-  mode: "replace",
-});
-
-// Sync beads before ending session
-await bash("br sync --flush-only");
-await bash("git add .beads/ && git commit -m 'session handoff'");
-
-// Start of session 2: Check status and continue
-const status = await swarm({
-  operation: "monitor",
-  action: "status",
-  team_name: "api-refactor-swarm",
-});
-
-const shared = await swarm({
-  operation: "sync",
-  action: "get_shared",
-  list_id: "api-refactor-swarm",
-});
-
-console.log(`Continuing swarm with ${shared.tasks.length} tasks...`);
-```
-
-## Data Locations
-
-| Data Type         | Location                                        | Persistence   |
-| ----------------- | ----------------------------------------------- | ------------- |
-| Beads tasks       | `.beads/issues/*.md`                            | Git-backed    |
-| Swarm progress    | `.beads/swarm-progress.jsonl`                   | Session       |
-| Shared task lists | `~/.local/share/opencode/storage/shared-tasks/` | Cross-session |
-| OpenCode todos    | `~/.local/share/opencode/storage/todo/`         | Session       |
-
-## Quick Reference
-
-```
-SESSION START:
-  swarm({ operation: "sync", action: "push" })  // Make Beads visible to subagents
-  swarm({ operation: "monitor", action: "status", team_name: "..." })  // Check swarm status
-
-DURING WORK:
-  swarm({ operation: "monitor", action: "progress_update", ... })  // Track worker progress
-  swarm({ operation: "monitor", action: "render_block", ... })  // TUI visualization
-  swarm({ operation: "sync", action: "update_shared", ... })  // Cross-session updates
-
-SESSION END:
-  swarm({ operation: "sync", action: "pull" })  // Sync completed todos back to Beads
-  swarm({ operation: "monitor", action: "clear", team_name: "..." })  // Cleanup swarm state
-  br sync --flush-only  // Export Beads changes
-  git add .beads/ && git commit -m "..."  // Commit changes to git
-
-RECOVERY:
-  swarm({ operation: "sync", action: "get_shared", list_id: "..." })  // Get shared task list
-  swarm({ operation: "monitor", action: "status", team_name: "..." })  // Check swarm status
-```
-
-## Rules
-
-1. **Always push Beads at session start** - Subagents need visibility via todoread
-2. **Use shared lists for long-running swarms** - Cross-session persistence via swarm sync
-3. **Pull completed todos back to Beads** - Keep tracking system in sync
-4. **Check swarm status before spawning** - Avoid duplicate work
-5. **Clear swarm state when done** - Cleanup after completion
-6. **Always sync and commit before session end** - `br sync --flush-only` then `git add .beads/ && git commit`

package/dist/template/.opencode/skill/code-navigation/SKILL.md

@@ -1,130 +0,0 @@
----
-name: code-navigation
-description: Use when navigating unfamiliar code, tracing cross-file dependencies, or before editing — efficient code reading patterns that minimize tool calls and token waste
-version: 1.0.0
-tags: [workflow, code-quality, context]
-dependencies: []
----
-
-# Code Navigation Skill
-
-## When to Use
-
-- Exploring an unfamiliar codebase or module
-- Tracing a function call across multiple files
-- Understanding blast radius before a breaking change
-- Planning edits that touch multiple files
-
-## When NOT to Use
-
-- Simple single-file edits where you already know the location
-- Reading config or documentation files
-
-## Core Principle
-
-> Collapse multiple tool calls into fewer, smarter ones. Every unnecessary read or search wastes tokens and turns.
-
-## Navigation Patterns
-
-### Pattern 1: Search First, Read Second
-
-**Wrong** (3-6 tool calls):
-```
-glob("*.ts") → read(file1) → "too big" → grep("functionName") → read(file2) → read(file3, section)
-```
-
-**Right** (1-2 tool calls):
-```
-grep("functionName", path: "src/") → read(exact_file, offset: line-10, limit: 30)
-```
-
-Start with search (grep, LSP findReferences) to locate, then read only what you need.
-
-### Pattern 2: Multi-Symbol Search
-
-When tracing a call chain (A calls B calls C), search for all symbols together:
-```
-grep({ pattern: "functionA|functionB|functionC", path: "src/" })
-```
-
-Or use LSP outgoingCalls to get the full call tree from a single point.
-
-### Pattern 3: Don't Re-Read What You've Already Seen
-
-**Anti-pattern**: Search returns full function body, then agent reads the same file again.
-
-If search results already show the code you need, work from that output. Only re-read when:
-- You need surrounding context (lines above/below the match)
-- You need the exact content for editing (verify before edit)
-- The search result was truncated
-
-### Pattern 4: Blast Radius Check (Before Breaking Changes)
-
-**WHEN**: Before renaming, removing, or changing the signature of an export.
-**SKIP**: When adding new code, fixing internal bugs, or reading.
-
-Steps:
-1. `lsp({ operation: "findReferences" })` — find all callers
-2. `lsp({ operation: "incomingCalls" })` — get the call hierarchy
-3. Review each caller to assess impact
-4. Plan edits from leaf callers inward (furthest dependencies first)
-
-### Pattern 5: Context Locality
-
-When editing a file, search results from the same directory/package are more likely relevant. Pass context when available:
-- In grep: use `path: "src/same-module/"` to scope
-- In LSP: operations are already file-scoped
-- In tilth: pass `context` param to boost nearby results
-
-### Pattern 6: Outline Before Deep Read
-
-For large files (>200 lines), get the structure first:
-```
-lsp({ operation: "documentSymbol", filePath: "src/large-file.ts", line: 1, character: 1 })
-```
-
-This gives you function names + line ranges. Then read only the section you need with `offset` and `limit`.
-
-### Pattern 7: Follow the Call Chain (Not the File Tree)
-
-**Wrong**: Read files top-to-bottom hoping to understand the flow.
-**Right**: Start from the entry point, follow function calls:
-
-```
-1. lsp({ operation: "goToDefinition" })   → find where it's defined
-2. lsp({ operation: "outgoingCalls" })     → what does it call?
-3. lsp({ operation: "goToDefinition" })    → follow the interesting callee
-```
-
-## With tilth MCP
-
-When tilth is available, it provides superior navigation:
-
-| Built-in Tool | tilth Equivalent | Advantage |
-|---|---|---|
-| `grep` + `read` | `tilth_search` (expand: 2) | Returns definitions with inline source — no second read needed |
-| `glob` | `tilth_files` | Adds token estimates per file |
-| `read` (large file) | `tilth_read` | Auto-outlines large files, shows structure |
-| `lsp(incomingCalls)` | `tilth_search(kind: "callers")` | Cross-language structural caller detection |
-| Manual tracing | `tilth_deps` | Shows imports + downstream callers before breaking changes |
-
-**IMPORTANT**: If tilth is available, prefer it over built-in grep/glob/read for code navigation. Tilth's expanded search results include full source — do NOT re-read files already shown in search output.
-
-## Cost Awareness
-
-Every tool call has a token cost. Efficient navigation means:
-- Fewer tool calls per task
-- Less context consumed by redundant reads
-- More budget available for actual implementation
-
-**Target**: Find and understand any symbol in ≤3 tool calls, not 6+.
-
-## Common Mistakes
-
-| Mistake | Fix |
-|---|---|
-| Read entire large file | Use outline first, then section read |
-| Search → read same code again | Work from search results directly |
-| Trace calls one-by-one | Multi-symbol search or outgoingCalls |
-| Explore randomly | Start from entry point, follow calls |
-| Forget to check blast radius | Always check before signature changes |

package/dist/template/.opencode/skill/mqdh/SKILL.md

@@ -1,171 +0,0 @@
----
-name: mqdh
-description: Use when building Meta Quest VR/AR apps, accessing Meta Horizon OS docs, or managing Quest devices via ADB. MUST load before any Meta XR development or documentation lookup.
-mcp:
-  mqdh:
-    command: "${MQDH_MCP_PATH}"
-    args: []
-version: 1.0.0
-tags: [integration, mcp]
-dependencies: []
----
-
-# Meta Quest Developer Hub MCP
-
-## When to Use
-
-- When you need Meta Quest docs, ADB tooling, or device management via MQDH MCP.
-
-## When NOT to Use
-
-- When you are not working on Meta Quest/VR development or MQDH is unavailable.
-
-
-## Prerequisites
-
-### 1. Install MQDH
-
-Download and install Meta Quest Developer Hub v6.2.1 or later:
-
-- **macOS**: [Download MQDH for Mac](https://developers.meta.com/horizon/documentation/android-apps/meta-quest-developer-hub)
-- **Windows**: [Download MQDH for Windows](https://developers.meta.com/horizon/documentation/android-apps/meta-quest-developer-hub)
-
-### 2. Set MCP Path Environment Variable
-
-The MCP server is bundled with MQDH. Set the path to the MCP executable:
-
-**macOS:**
-
-```bash
-export MQDH_MCP_PATH="/Applications/Meta Quest Developer Hub.app/Contents/Resources/mcp-server"
-```
-
-**Windows:**
-
-```powershell
-$env:MQDH_MCP_PATH = "C:\Program Files\Meta Quest Developer Hub\resources\mcp-server.exe"
-```
-
-> **Note**: Paths may vary based on your installation. Check MQDH's AI Tools settings tab for the exact path.
-
-### 3. Alternative: Use MQDH's Built-in Setup
-
-MQDH v6.2.1+ includes an **AI Tools settings tab** with:
-
-- One-click install for **Cursor** and **VS Code**
-- Guided setup for Claude Desktop, Gemini CLI, Android Studio
-- Manual configuration export for other tools
-
-## Quick Start
-
-After setting up the environment variable and loading this skill:
-
-```
-skill_mcp(skill_name="mqdh", list_tools=true)
-```
-
-Then invoke tools:
-
-```
-skill_mcp(skill_name="mqdh", tool_name="fetch_meta_quest_doc", arguments='{"query": "hand tracking setup"}')
-```
-
-## Available Tools
-
-### fetch_meta_quest_doc
-
-Search and retrieve Meta Horizon OS documentation.
-
-| Parameter | Type   | Required | Description                |
-| --------- | ------ | -------- | -------------------------- |
-| `query`   | string | Yes      | Documentation search query |
-
-**Example:**
-
-```
-skill_mcp(skill_name="mqdh", tool_name="fetch_meta_quest_doc", arguments='{"query": "passthrough API Unity"}')
-```
-
-### get_adb_path
-
-Get the path to the bundled ADB executable.
-
-**Example:**
-
-```
-skill_mcp(skill_name="mqdh", tool_name="get_adb_path", arguments='{}')
-```
-
-### device_list
-
-List connected Quest devices.
-
-**Example:**
-
-```
-skill_mcp(skill_name="mqdh", tool_name="device_list", arguments='{}')
-```
-
-### install_apk
-
-Install an APK to a connected Quest device.
-
-| Parameter   | Type   | Required | Description      |
-| ----------- | ------ | -------- | ---------------- |
-| `apk_path`  | string | Yes      | Path to APK file |
-| `device_id` | string | No       | Target device ID |
-
-**Example:**
-
-```
-skill_mcp(skill_name="mqdh", tool_name="install_apk", arguments='{"apk_path": "/path/to/app.apk"}')
-```
-
-## Use Cases
-
-- **Documentation Lookup**: Quickly search Meta Horizon OS docs for APIs, best practices
-- **Device Management**: List devices, install APKs, manage Quest headsets
-- **Development Workflow**: Integrate ADB operations into AI-assisted development
-- **Troubleshooting**: Find solutions in Meta's documentation
-
-## Workflow Examples
-
-### 1. Look Up API Documentation
-
-```
-# Search for hand tracking documentation
-skill_mcp(skill_name="mqdh", tool_name="fetch_meta_quest_doc", arguments='{"query": "hand tracking gesture detection"}')
-
-# Search for passthrough setup
-skill_mcp(skill_name="mqdh", tool_name="fetch_meta_quest_doc", arguments='{"query": "mixed reality passthrough Unity"}')
-```
-
-### 2. Device Operations
-
-```
-# List connected devices
-skill_mcp(skill_name="mqdh", tool_name="device_list", arguments='{}')
-
-# Install a build
-skill_mcp(skill_name="mqdh", tool_name="install_apk", arguments='{"apk_path": "/builds/myapp.apk", "device_id": "1234567890"}')
-```
-
-## Transport
-
-This MCP uses **STDIO** transport to communicate with the LLM agent.
-
-## Troubleshooting
-
-**"Command not found"**: Verify `MQDH_MCP_PATH` points to the correct executable. Check MQDH's AI Tools settings for the exact path.
-
-**"MQDH not installed"**: Download MQDH v6.2.1+ from [Meta Developer Portal](https://developers.meta.com/horizon/documentation/android-apps/meta-quest-developer-hub).
-
-**"Device not found"**: Ensure your Quest is connected via USB and developer mode is enabled.
-
-**One-click setup preferred**: Use MQDH's built-in AI Tools settings tab for automatic configuration with Cursor or VS Code.
-
-## References
-
-- [MQDH MCP Documentation](https://developers.meta.com/horizon/documentation/unity/ts-mqdh-mcp/)
-- [Install MQDH](https://developers.meta.com/horizon/documentation/android-apps/meta-quest-developer-hub)
-- [Meta Horizon OS Developer Docs](https://developers.meta.com/horizon/documentation/)