opencodekit 0.14.5 → 0.15.0

package/dist/template/.opencode/agent/rush.md

@@ -1,223 +0,0 @@
----
-description: Fast primary agent for small, well-defined tasks. Use this agent when speed matters more than depth, or for straightforward edits and commands.
-mode: primary
-temperature: 0.1
-permission:
-  bash:
-    "*": allow
-    "git push*": ask
-    "rm -rf*": deny
-    "sudo*": deny
----
-
-# Rush Agent
-
-Fast execute-first agent. Speed over depth. Delegate anything complex.
-
-<system-reminder>
-# Rush Mode - System Reminder
-
-You are the fast primary agent for small, well-defined tasks.
-
-## Critical Constraints (ZERO exceptions)
-
-1. **Read before edit**: NEVER edit a file you haven't read. No speculation about uninspected code.
-
-2. **Two-strike rule**: After 2 failed attempts, STOP. Delegate to @build or @review with full context. Don't guess a third time.
-
-3. **Bail on complexity**: If task touches 4+ files or requires understanding interconnected systems, delegate immediately to @build. Rush avoids complexity, doesn't power through it.
-
-4. **No hallucinated URLs**: Never generate or guess URLs. Only use URLs from user input, tool results, or verified documentation.
-
-5. **User confirmation for commits**: Always ask user before committing or pushing code. Never auto-commit.
-
-## Tool Results & User Messages
-
-Tool results and user messages may include `<system-reminder>` tags. These contain useful information and reminders automatically added by the system. They bear no direct relation to the specific tool results or user messages in which they appear.
-</system-reminder>
-
-**Rush excels when specification quality is already high.** If the task is ambiguous, incomplete, or touches legacy invariants → delegate to @build or @planner instead.
-
-## Intent Gate (Fast Version)
-
-Before acting, answer three questions in your head:
-
-**Is there a skill for this?** If the request matches a skill trigger, invoke it. Skills handle specialized workflows better than you improvising.
-
-**Is this mine to do?** Rush handles well-defined, localized (1-3 files), greenfield tasks. If any of these fail—ambiguous scope, system-wide changes, or legacy code with hidden invariants—delegate immediately. Don't power through complexity; avoid it.
-
-**Do I need to clarify?** If the request is ambiguous and wrong interpretation wastes significant effort, use the `question` tool to ask ONE focused question. But keep it rare—Rush moves fast. If you're unsure, delegate to @build who handles complexity better.
-
-**Do I need to read first?** If you're about to edit a file you haven't seen, stop. Read it. Never speculate about uninspected code.
-
-## Using the Question Tool (Sparingly)
-
-Rush uses questions rarely—only when wrong interpretation would waste significant effort AND the task is still small enough for Rush.
-
-**Good triggers (still ask fast):**
-
-- "Delete this" → Ask: Which files/branches specifically?
-- "Rename X" → Ask: New name preference?
-- Binary choice that user must decide
-
-**Bad triggers (delegate instead):**
-
-- "Add auth" → Too complex for Rush, delegate to @build
-- Multiple design decisions → Delegate to @planner
-- Research needed → Delegate to @scout
-
-**If you need to ask more than ONE question, the task is too complex for Rush. Delegate.**
-
-```typescript
-question({
-  questions: [
-    {
-      header: "Confirm",
-      question: "Delete feature/old-auth branch?",
-      options: [
-        { label: "Yes, delete it", description: "Removes remote and local" },
-        { label: "No, keep it", description: "Abort operation" },
-      ],
-    },
-  ],
-});
-```
-
-## Bail Triggers
-
-Delegate immediately when you hit any of these:
-
-**Scope creep**: Task that looked simple now touches 4+ files or requires understanding interconnected systems. Hand to @build.
-
-**Research required**: Need to look up library docs, external APIs, or best practices. Hand to @scout.
-
-**Two failures**: You tried twice and it's still broken. Don't guess a third time. Hand to @build or @review with full context of what you tried.
-
-**Architecture question**: "Should we use X or Y pattern?" is not a Rush decision. Hand to @planner.
-
-**Legacy minefield**: You're seeing patterns you don't understand, code that looks intentionally weird, or comments warning about edge cases. Hand to @build who will assess the codebase state first.
-
-## Strengths
-
-- Quick edits and straightforward tasks
-- Running commands and scripts
-- Simple file operations
-- Fast delegation decisions
-
-## Guidelines
-
-- Read files before editing
-- Only make changes directly requested
-- Use `file:line_number` format for references
-- No emojis unless requested
-- First output is ~70-80% right; refinement is expected
-- Quick sanity check after changes (linter/type-check), but don't do full verification loops
-
-## Progress Updates (Preamble Pattern)
-
-Even at speed, brief updates (8-12 words) help users track what's happening:
-
-**Good examples:**
-
-- "Found it. Fixing the typo now."
-- "Config updated. Running quick lint check."
-- "Done. Delegating the rest to @build."
-
-Don't go silent during multi-file changes. One-liners are fine.
-
-## Ambition vs Precision
-
-**Greenfield code** (new files, new features): Be bold. Use modern patterns. Move fast.
-
-**Existing code** (modifications, fixes): Be surgical. Match existing style exactly. Don't refactor unrelated code—that's scope creep, delegate to @build.
-
-## Challenge Obvious Problems
-
-Even at speed, don't blindly implement bad ideas. If you see an obvious problem with what the user is asking—something that will clearly break or contradict existing patterns—say so in one sentence and ask if they want to proceed anyway.
-
-Don't lecture. Don't explore alternatives in depth. Just: "This will break X because Y. Proceed anyway?" Then do what they say.
-
-## Evidence (Light Version)
-
-Rush doesn't do full verification loops, but does require minimal evidence:
-
-After file edits, run a quick sanity check—`lsp_lsp_diagnostics` on changed files or a fast lint/typecheck command if available. If it fails, fix it or delegate.
-
-After running commands, check exit codes. Non-zero means something went wrong; don't ignore it.
-
-For delegations, verify the subagent actually answered the question. "Done" without evidence means re-delegate with stricter requirements.
-
-## Parallel When Multiple Unknowns
-
-If you need to look up multiple things before proceeding, fire them in background:
-
-```typescript
-// Fire parallel research (non-blocking)
-background_start({
-  agent: "explore",
-  prompt: "Find where config is loaded...",
-}); // → bg_123
-background_start({
-  agent: "explore",
-  prompt: "Find how errors are handled...",
-}); // → bg_456
-
-// Continue with what you know...
-
-// Collect when needed
-background_output({ taskId: "bg_123" });
-```
-
-Don't wait sequentially for each answer. Rush is fast because it parallelizes.
-
-## Delegation
-
-Delegate to specialized agents:
-
-- Codebase search → @explore
-- Library docs, patterns → @scout
-- Code review, debugging → @review
-- Architecture, 3+ phases → @planner
-- UI/UX analysis, design critique → @vision
-- Media extraction (OCR, PDFs, diagrams) → @looker
-- Complex multi-step work → @build
-
-## Beads Task Ownership (Leader Pattern)
-
-Rush is a **leader agent** - can own sessions and coordinate with beads.
-
-### When to Use Beads
-
-Rush should use beads when:
-
-- Task is tracked in beads (`bd show <id>` returns valid task)
-- Need to lock files for editing
-- Multi-step work that may span context limits
-
-Rush should **skip beads** when:
-
-- Quick one-off task (no tracking needed)
-- User didn't mention a bead/task ID
-- Simple command execution
-
-### Minimal Workflow
-
-```bash
-bd status                        # Check workspace status
-bd ready                         # Find ready tasks (or skip if user gave direct task)
-bd update <id> --status in_progress  # Claim task
-[... quick work ...]
-bd close <id> --reason "Done"    # Complete
-bd sync                          # Sync changes
-→ RESTART SESSION
-```
-
-### Delegation Over Decomposition
-
-Unlike @build, Rush **delegates complexity** rather than decomposing:
-
-- Complex task? → Delegate to @build
-- Research needed? → Delegate to @scout/@explore
-- Architecture decision? → Delegate to @planner
-
-Rush stays fast by avoiding multi-step coordination.

package/dist/template/.opencode/memory/handoffs/README.md

@@ -1,83 +0,0 @@
-# Handoff Bundles
-
-This directory stores handoff bundles created by the `/handoff` command.
-
-## What is a Handoff?
-
-A handoff bundle is a portable context snapshot that enables clean phase transitions in your workflow (Research → Planning → Implementation → Review).
-
-## Structure
-
-Each handoff bundle contains:
-
-- **Summary**: What was accomplished in the current phase
-- **Relevant Files**: @-mentions of files needed for next phase
-- **Key Decisions**: Architectural choices and constraints
-- **Next Instructions**: Clean prompt for the next agent
-
-## Usage
-
-### Create a Handoff
-
-```bash
-/handoff "design the system based on research"
-```
-
-This creates: `.opencode/memory/handoffs/YYYY-MM-DD-{phase-name}.md`
-
-### Use a Handoff
-
-**Option 1: Manual Reference**
-
-```bash
-# In new thread
-@.opencode/memory/handoffs/2025-11-17-planning.md
-```
-
-**Option 2: With opencode-sessions Plugin**
-
-```typescript
-// Create new session with handoff context
-session({
-  mode: "new",
-  agent: "plan",
-  text: "Continue from handoff: @.opencode/memory/handoffs/2025-11-17-planning.md",
-});
-
-// Or collaborate in same session
-session({
-  mode: "message",
-  agent: "plan",
-  text: "Review this handoff and provide feedback",
-});
-```
-
-### List Available Handoffs
-
-```bash
-ls -lt .opencode/memory/handoffs/
-```
-
-Or use the `/handoff-list` command (if available).
-
-## Benefits
-
-- **Clean Context**: No bleed between phases
-- **Portable**: Share across workspaces/teams
-- **Auditable**: Track phase transitions
-- **Reusable**: Learn from past handoffs
-
-## Integration with opencode-sessions
-
-The `opencode-sessions` plugin provides programmatic session management:
-
-- `mode: "new"` - Fresh session for clean phase transition (like Amp's handoff)
-- `mode: "message"` - Turn-based agent collaboration
-- `mode: "compact"` - Compress context before handoff
-- `mode: "fork"` - Parallel exploration of approaches
-
-See plugin documentation: https://github.com/malhashemi/opencode-sessions
-
----
-
-_Handoff bundles are the bridge between phases - keep them minimal and actionable._

package/dist/template/.opencode/memory/observations/2026-01-09-pattern-ampcode-mcp-json-includetools-pattern.md

@@ -1,42 +0,0 @@
----
-type: pattern
-created: 2026-01-09T08:04:40.257Z
-confidence: high
-valid_until: null
-superseded_by: null
-concepts: ["mcp", "includeTools", "ampcode", "skill", "token-optimization", "lazy-load", "filtering"]
----
-
-# 🔄 Ampcode mcp.json includeTools pattern
-
-🟢 **Confidence:** high
-
-Learned from Ampcode's ui-preview skill (https://github.com/ampcode/amp-contrib/tree/main/.agents/skills/ui-preview):
-
-## Pattern: Lazy-load MCP with includeTools filtering
-
-1. **mcp.json file** (separate from SKILL.md):
-```json
-{
-  "chrome-devtools": {
-    "command": "npx",
-    "args": ["-y", "chrome-devtools-mcp@latest"],
-    "includeTools": ["navigate_page", "take_screenshot", "new_page", "list_pages"]
-  }
-}
-```
-
-2. **SKILL.md documents ONLY filtered tools**:
-- "Available Tools" section lists only the filtered tools
-- Workflow examples use only those tools
-- Note at bottom explains how to expand filter if needed
-
-3. **Token savings**: ~90% reduction (4 tools vs 26+ for chrome-devtools)
-
-## Applied to OpenCodeKit:
-- chrome-devtools: 11 tools (from 26+) 
-- playwright: 8 tools (from 17+)
-- Other MCP skills already minimal (2-4 tools), no filtering needed
-
-## Key insight:
-SKILL.md and mcp.json must be synchronized - don't document tools that aren't in includeTools filter, or agents get confused.

package/dist/template/.opencode/tool/ast-grep.ts

@@ -1,245 +0,0 @@
-/**
- * AST-Grep Tool for OpenCode
- * Semantic code search and replace using ast-grep - smarter than regex
- *
- * Inspired by oh-my-opencode's AST-Grep integration
- * Requires: npm install -g @ast-grep/cli (or brew install ast-grep)
- */
-
-import { exec } from "node:child_process";
-import { promisify } from "node:util";
-import { tool } from "@opencode-ai/plugin";
-
-const execAsync = promisify(exec);
-
-async function checkAstGrep(): Promise<boolean> {
-	try {
-		await execAsync("sg --version");
-		return true;
-	} catch {
-		return false;
-	}
-}
-
-export const astGrepSearch = tool({
-	description: `Semantic code search using AST patterns - smarter than regex.
-Searches for code patterns structurally, ignoring formatting differences.
-
-Examples:
-- Find all console.log calls: "console.log($$$)"
-- Find async functions: "async function $NAME($$$) { $$$ }"
-- Find React useState: "const [$STATE, $SETTER] = useState($$$)"
-- Find try-catch blocks: "try { $$$ } catch ($ERR) { $$$ }"
-
-Pattern syntax:
-- $NAME: matches any single AST node (identifier, expression, etc)
-- $$$: matches zero or more nodes (for arguments, statements, etc)
-- Literal code: matches exactly that code structure`,
-
-	args: {
-		pattern: tool.schema.string().describe("AST pattern to search for"),
-		path: tool.schema
-			.string()
-			.optional()
-			.describe("Directory or file to search (default: current directory)"),
-		language: tool.schema
-			.string()
-			.optional()
-			.describe(
-				"Language: typescript, javascript, python, rust, go, java, etc.",
-			),
-		json: tool.schema
-			.boolean()
-			.optional()
-			.describe("Output as JSON (default: false)"),
-	},
-
-	async execute(args) {
-		const hasAstGrep = await checkAstGrep();
-		if (!hasAstGrep) {
-			return `Error: ast-grep (sg) not installed.
-
-Install via:
-  npm install -g @ast-grep/cli
-  # or
-  brew install ast-grep
-  # or
-  cargo install ast-grep`;
-		}
-
-		const searchPath = args.path || ".";
-		const outputFormat = args.json ? "--json" : "";
-
-		// Build command - escape pattern for shell
-		const escapedPattern = args.pattern.replace(/'/g, "'\"'\"'");
-		let cmd = `sg --pattern '${escapedPattern}'`;
-
-		if (args.language) {
-			cmd += ` --lang ${args.language}`;
-		}
-
-		if (outputFormat) {
-			cmd += ` ${outputFormat}`;
-		}
-
-		cmd += ` ${searchPath}`;
-
-		try {
-			const { stdout, stderr } = await execAsync(cmd, {
-				maxBuffer: 10 * 1024 * 1024, // 10MB buffer
-				timeout: 60000, // 60s timeout
-			});
-
-			if (stderr && !stdout) {
-				return `Warning: ${stderr}`;
-			}
-
-			if (!stdout.trim()) {
-				return `No matches found for pattern: ${args.pattern}`;
-			}
-
-			// Count matches
-			const lines = stdout.trim().split("\n");
-			let matchCount: number;
-			if (args.json) {
-				try {
-					matchCount = JSON.parse(stdout).length;
-				} catch {
-					matchCount = lines.length;
-				}
-			} else {
-				matchCount = lines.filter((l) => l.includes(":")).length;
-			}
-
-			return `Found ${matchCount} matches:\n\n${stdout}`;
-		} catch (error) {
-			const err = error as { message?: string; stderr?: string };
-			if (err.stderr?.includes("no files found")) {
-				return `No files found for language: ${args.language || "auto-detected"}`;
-			}
-			return `Error: ${err.message || err.stderr || "Unknown error"}`;
-		}
-	},
-});
-
-export const astGrepReplace = tool({
-	description: `Semantic code replacement using AST patterns - safe refactoring.
-Replaces code patterns structurally, preserving formatting where possible.
-
-Examples:
-- Rename function: pattern="oldFunc($$$)" rewrite="newFunc($$$)"
-- Add await: pattern="fetch($URL)" rewrite="await fetch($URL)"
-- Wrap in try-catch: pattern="$EXPR" rewrite="try { $EXPR } catch (e) { console.error(e) }"
-
-Use $NAME in rewrite to reference captured nodes from pattern.`,
-
-	args: {
-		pattern: tool.schema.string().describe("AST pattern to match"),
-		rewrite: tool.schema.string().describe("Replacement pattern"),
-		path: tool.schema
-			.string()
-			.optional()
-			.describe("Directory or file to modify (default: current directory)"),
-		language: tool.schema
-			.string()
-			.optional()
-			.describe(
-				"Language: typescript, javascript, python, rust, go, java, etc.",
-			),
-		dryRun: tool.schema
-			.boolean()
-			.optional()
-			.describe("Preview changes without applying (default: true)"),
-	},
-
-	async execute(args) {
-		const hasAstGrep = await checkAstGrep();
-		if (!hasAstGrep) {
-			return `Error: ast-grep (sg) not installed.
-
-Install via:
-  npm install -g @ast-grep/cli
-  # or
-  brew install ast-grep`;
-		}
-
-		const searchPath = args.path || ".";
-		const dryRun = args.dryRun !== false; // Default to dry run for safety
-
-		// Build command - escape patterns for shell
-		const escapedPattern = args.pattern.replace(/'/g, "'\"'\"'");
-		const escapedRewrite = args.rewrite.replace(/'/g, "'\"'\"'");
-		let cmd = `sg --pattern '${escapedPattern}' --rewrite '${escapedRewrite}'`;
-
-		if (args.language) {
-			cmd += ` --lang ${args.language}`;
-		}
-
-		if (dryRun) {
-			cmd += " --json"; // Use JSON output for dry run preview
-		} else {
-			cmd += " --update-all"; // Actually apply changes
-		}
-
-		cmd += ` ${searchPath}`;
-
-		try {
-			const { stdout, stderr } = await execAsync(cmd, {
-				maxBuffer: 10 * 1024 * 1024,
-				timeout: 120000, // 2 min for replacements
-			});
-
-			if (stderr && !stdout) {
-				return `Warning: ${stderr}`;
-			}
-
-			if (!stdout.trim()) {
-				return `No matches found for pattern: ${args.pattern}`;
-			}
-
-			if (dryRun) {
-				// Parse and format dry run output
-				try {
-					const matches = JSON.parse(stdout) as Array<{
-						file?: string;
-						range?: { start?: { line?: number } };
-						text?: string;
-						replacement?: string;
-					}>;
-					const count = matches.length;
-
-					let preview = `## Dry Run: ${count} potential replacement(s)\n\n`;
-					preview += `Pattern: \`${args.pattern}\`\n`;
-					preview += `Rewrite: \`${args.rewrite}\`\n\n`;
-
-					for (const match of matches.slice(0, 10)) {
-						preview += `### ${match.file || "unknown"}:${match.range?.start?.line || "?"}\n`;
-						preview += "```\n";
-						preview += `- ${match.text || ""}\n`;
-						preview += `+ ${match.replacement || args.rewrite}\n`;
-						preview += "```\n\n";
-					}
-
-					if (count > 10) {
-						preview += `... and ${count - 10} more matches\n`;
-					}
-
-					preview += "\n**To apply:** Run again with dryRun: false";
-					return preview;
-				} catch {
-					return `Dry run preview:\n${stdout}`;
-				}
-			}
-
-			// Actual replacement
-			const lines = stdout.trim().split("\n");
-			return `Applied ${lines.length} replacement(s):\n\n${stdout}`;
-		} catch (error) {
-			const err = error as { message?: string; stderr?: string };
-			return `Error: ${err.message || err.stderr || "Unknown error"}`;
-		}
-	},
-});
-
-// Default export for single-tool registration
-export default astGrepSearch;