@hiai-gg/hiai-opencode 0.1.7 → 0.1.9

package/src/features/builtin-commands/templates/handoff.ts

@@ -1,177 +0,0 @@
-export const HANDOFF_TEMPLATE = `# Handoff Command
-
-## Purpose
-
-Use /handoff when:
-- The current session context is getting too long and quality is degrading
-- You want to start fresh while preserving essential context from this session
-- The context window is approaching capacity
-
-This creates a detailed context summary that can be used to continue work in a new session.
-
----
-
-# PHASE 0: VALIDATE REQUEST
-
-Before proceeding, confirm:
-- [ ] There is meaningful work or context in this session to preserve
-- [ ] The user wants to create a handoff summary (not just asking about it)
-
-If the session is nearly empty or has no meaningful context, inform the user there is nothing substantial to hand off.
-
----
-
-# PHASE 1: GATHER PROGRAMMATIC CONTEXT
-
-Execute these tools to gather concrete data:
-
-1. session_read({ session_id: "$SESSION_ID" }) - full session history
-2. todoread() - current task progress
-3. Bash({ command: "git diff --stat HEAD~10..HEAD" }) - recent file changes
-4. Bash({ command: "git status --porcelain" }) - uncommitted changes
-
-Suggested execution order:
-
-\`\`\`
-session_read({ session_id: "$SESSION_ID" })
-todoread()
-Bash({ command: "git diff --stat HEAD~10..HEAD" })
-Bash({ command: "git status --porcelain" })
-\`\`\`
-
-Analyze the gathered outputs to understand:
-- What the user asked for (exact wording)
-- What work was completed
-- What tasks remain incomplete (include todo state)
-- What decisions were made
-- What files were modified or discussed (include git diff/stat + status)
-- What patterns, constraints, or preferences were established
-
----
-
-# PHASE 2: EXTRACT CONTEXT
-
-Write the context summary from first person perspective ("I did...", "I told you...").
-
-Focus on:
-- Capabilities and behavior, not file-by-file implementation details
-- What matters for continuing the work
-- Avoiding excessive implementation details (variable names, storage keys, constants) unless critical
-- USER REQUESTS (AS-IS) must be verbatim (do not paraphrase)
-- EXPLICIT CONSTRAINTS must be verbatim only (do not invent)
-
-Questions to consider when extracting:
-- What did I just do or implement?
-- What instructions did I already give which are still relevant (e.g. follow patterns in the codebase)?
-- What files did I tell you are important or that I am working on?
-- Did I provide a plan or spec that should be included?
-- What did I already tell you that is important (libraries, patterns, constraints, preferences)?
-- What important technical details did I discover (APIs, methods, patterns)?
-- What caveats, limitations, or open questions did I find?
-
----
-
-# PHASE 3: FORMAT OUTPUT
-
-Generate a handoff summary using this exact format:
-
-\`\`\`
-HANDOFF CONTEXT
-===============
-
-USER REQUESTS (AS-IS)
----------------------
-- [Exact verbatim user requests - NOT paraphrased]
-
-GOAL
-----
-[One sentence describing what should be done next]
-
-WORK COMPLETED
---------------
-- [First person bullet points of what was done]
-- [Include specific file paths when relevant]
-- [Note key implementation decisions]
-
-CURRENT STATE
--------------
-- [Current state of the codebase or task]
-- [Build/test status if applicable]
-- [Any environment or configuration state]
-
-PENDING TASKS
--------------
-- [Tasks that were planned but not completed]
-- [Next logical steps to take]
-- [Any blockers or issues encountered]
-- [Include current todo state from todoread()]
-
-KEY FILES
----------
-- [path/to/file1] - [brief role description]
-- [path/to/file2] - [brief role description]
-(Maximum 10 files, prioritized by importance)
-- (Include files from git diff/stat and git status)
-
-IMPORTANT DECISIONS
--------------------
-- [Technical decisions that were made and why]
-- [Trade-offs that were considered]
-- [Patterns or conventions established]
-
-EXPLICIT CONSTRAINTS
---------------------
-- [Verbatim constraints only - from user or existing AGENTS.md]
-- If none, write: None
-
-CONTEXT FOR CONTINUATION
-------------------------
-- [What the next session needs to know to continue]
-- [Warnings or gotchas to be aware of]
-- [References to documentation if relevant]
-\`\`\`
-
-Rules for the summary:
-- Plain text with bullets
-- No markdown headers with # (use the format above with dashes)
-- No bold, italic, or code fences within content
-- Use workspace-relative paths for files
-- Keep it focused - only include what matters for continuation
-- Pick an appropriate length based on complexity
-- USER REQUESTS (AS-IS) and EXPLICIT CONSTRAINTS must be verbatim only
-
----
-
-# PHASE 4: PROVIDE INSTRUCTIONS
-
-After generating the summary, instruct the user:
-
-\`\`\`
----
-
-TO CONTINUE IN A NEW SESSION:
-
-1. Press 'n' in OpenCode TUI to open a new session, or run 'opencode' in a new terminal
-2. Paste the HANDOFF CONTEXT above as your first message
-3. Add your request: "Continue from the handoff context above. [Your next task]"
-
-The new session will have all context needed to continue seamlessly.
-\`\`\`
-
----
-
-# IMPORTANT CONSTRAINTS
-
-- DO NOT attempt to programmatically create new sessions (no API available to agents)
-- DO provide a self-contained summary that works without access to this session
-- DO include workspace-relative file paths
-- DO NOT include sensitive information (API keys, credentials, secrets)
-- DO NOT exceed 10 files in the KEY FILES section
-- DO keep the GOAL section to a single sentence or short paragraph
-
----
-
-# EXECUTE NOW
-
-Begin by gathering programmatic context, then synthesize the handoff summary.
-`

package/src/features/builtin-commands/templates/init-deep.ts

@@ -1,305 +0,0 @@
-export const INIT_DEEP_TEMPLATE = `# /init-deep
-
-Generate hierarchical AGENTS.md files. Root + complexity-scored subdirectories.
-
-## Usage
-
-\`\`\`
-/init-deep                      # Update mode: modify existing + create new where warranted
-/init-deep --create-new         # Read existing → remove all → regenerate from scratch
-/init-deep --max-depth=2        # Limit directory depth (default: 3)
-\`\`\`
-
----
-
-## Workflow (High-Level)
-
-1. **Discovery + Analysis** (concurrent)
-   - Fire background researcher agents immediately
-   - Main session: bash structure + LSP codemap + read existing AGENTS.md
-2. **Score & Decide** - Determine AGENTS.md locations from merged findings
-3. **Generate** - Root first, then subdirs in parallel
-4. **Review** - Deduplicate, trim, validate
-
-<critical>
-**TodoWrite ALL phases. Mark in_progress → completed in real-time.**
-\`\`\`
-TodoWrite([
-  { id: "discovery", content: "Fire researcher agents + LSP codemap + read existing", status: "pending", priority: "high" },
-  { id: "scoring", content: "Score directories, determine locations", status: "pending", priority: "high" },
-  { id: "generate", content: "Generate AGENTS.md files (root + subdirs)", status: "pending", priority: "high" },
-  { id: "review", content: "Deduplicate, validate, trim", status: "pending", priority: "medium" }
-])
-\`\`\`
-</critical>
-
----
-
-## Phase 1: Discovery + Analysis (Concurrent)
-
-**Mark "discovery" as in_progress.**
-
-### Fire Background Researcher Agents IMMEDIATELY
-
-Don't wait-these run async while main session works.
-
-\`\`\`
-// Fire all at once, collect results later
-task(subagent_type="researcher", load_skills=[], description="Research project structure", run_in_background=true, prompt="Project structure: PREDICT standard patterns for detected language → REPORT deviations only")
-task(subagent_type="researcher", load_skills=[], description="Research entry points", run_in_background=true, prompt="Entry points: FIND main files → REPORT non-standard organization")
-task(subagent_type="researcher", load_skills=[], description="Research conventions", run_in_background=true, prompt="Conventions: FIND config files (.eslintrc, pyproject.toml, .editorconfig) → REPORT project-specific rules")
-task(subagent_type="researcher", load_skills=[], description="Research anti-patterns", run_in_background=true, prompt="Anti-patterns: FIND 'DO NOT', 'NEVER', 'ALWAYS', 'DEPRECATED' comments → LIST forbidden patterns")
-task(subagent_type="researcher", load_skills=[], description="Research build/CI", run_in_background=true, prompt="Build/CI: FIND .github/workflows, Makefile → REPORT non-standard patterns")
-task(subagent_type="researcher", load_skills=[], description="Research test patterns", run_in_background=true, prompt="Test patterns: FIND test configs, test structure → REPORT unique conventions")
-\`\`\`
-
-<dynamic-agents>
-**DYNAMIC AGENT SPAWNING**: After bash analysis, spawn ADDITIONAL researcher agents based on project scale:
-
-| Factor | Threshold | Additional Agents |
-|--------|-----------|-------------------|
-| **Total files** | >100 | +1 per 100 files |
-| **Total lines** | >10k | +1 per 10k lines |
-| **Directory depth** | ≥4 | +2 for deep exploration |
-| **Large files (>500 lines)** | >10 files | +1 for complexity hotspots |
-| **Monorepo** | detected | +1 per package/workspace |
-| **Multiple languages** | >1 | +1 per language |
-
-\`\`\`bash
-# Measure project scale first
-total_files=$(find . -type f -not -path '*/node_modules/*' -not -path '*/.git/*' | wc -l)
-total_lines=$(find . -type f \\( -name "*.ts" -o -name "*.py" -o -name "*.go" \\) -not -path '*/node_modules/*' -exec wc -l {} + 2>/dev/null | tail -1 | awk '{print $1}')
-large_files=$(find . -type f \\( -name "*.ts" -o -name "*.py" \\) -not -path '*/node_modules/*' -exec wc -l {} + 2>/dev/null | awk '$1 > 500 {count++} END {print count+0}')
-max_depth=$(find . -type d -not -path '*/node_modules/*' -not -path '*/.git/*' | awk -F/ '{print NF}' | sort -rn | head -1)
-\`\`\`
-
-Example spawning:
-\`\`\`
-// 500 files, 50k lines, depth 6, 15 large files → spawn 5+5+2+1 = 13 additional agents
-task(subagent_type="researcher", load_skills=[], description="Analyze large files", run_in_background=true, prompt="Large file analysis: FIND files >500 lines, REPORT complexity hotspots")
-task(subagent_type="researcher", load_skills=[], description="Research deep modules", run_in_background=true, prompt="Deep modules at depth 4+: FIND hidden patterns, internal conventions")
-task(subagent_type="researcher", load_skills=[], description="Find shared utilities", run_in_background=true, prompt="Cross-cutting concerns: FIND shared utilities across directories")
-// ... more based on calculation
-\`\`\`
-</dynamic-agents>
-
-### Main Session: Concurrent Analysis
-
-**While background agents run**, main session does:
-
-#### 1. Bash Structural Analysis
-\`\`\`bash
-# Directory depth + file counts
-find . -type d -not -path '*/\\.*' -not -path '*/node_modules/*' -not -path '*/venv/*' -not -path '*/dist/*' -not -path '*/build/*' | awk -F/ '{print NF-1}' | sort -n | uniq -c
-
-# Files per directory (top 30)
-find . -type f -not -path '*/\\.*' -not -path '*/node_modules/*' | sed 's|/[^/]*$||' | sort | uniq -c | sort -rn | head -30
-
-# Code concentration by extension
-find . -type f \\( -name "*.py" -o -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.go" -o -name "*.rs" \\) -not -path '*/node_modules/*' | sed 's|/[^/]*$||' | sort | uniq -c | sort -rn | head -20
-
-# Existing AGENTS.md / CLAUDE.md
-find . -type f \\( -name "AGENTS.md" -o -name "CLAUDE.md" \\) -not -path '*/node_modules/*' 2>/dev/null
-\`\`\`
-
-#### 2. Read Existing AGENTS.md
-\`\`\`
-For each existing file found:
-  Read(filePath=file)
-  Extract: key insights, conventions, anti-patterns
-  Store in EXISTING_AGENTS map
-\`\`\`
-
-If \`--create-new\`: Read all existing first (preserve context) → then delete all → regenerate.
-
-#### 3. LSP Codemap (if available)
-\`\`\`
-LspServers()  # Check availability
-
-# Entry points (parallel)
-LspDocumentSymbols(filePath="src/index.ts")
-LspDocumentSymbols(filePath="main.py")
-
-# Key symbols (parallel)
-LspWorkspaceSymbols(filePath=".", query="class")
-LspWorkspaceSymbols(filePath=".", query="interface")
-LspWorkspaceSymbols(filePath=".", query="function")
-
-# Centrality for top exports
-LspFindReferences(filePath="...", line=X, character=Y)
-\`\`\`
-
-**LSP Fallback**: If unavailable, rely on researcher agents + AST-grep.
-
-### Collect Background Results
-
-\`\`\`
-// After main session analysis done, collect all task results
-for each task_id: background_output(task_id="...")
-\`\`\`
-
-**Merge: bash + LSP + existing + researcher findings. Mark "discovery" as completed.**
-
----
-
-## Phase 2: Scoring & Location Decision
-
-**Mark "scoring" as in_progress.**
-
-### Scoring Matrix
-
-| Factor | Weight | High Threshold | Source |
-|--------|--------|----------------|--------|
-| File count | 3x | >20 | bash |
-| Subdir count | 2x | >5 | bash |
-| Code ratio | 2x | >70% | bash |
-| Unique patterns | 1x | Has own config | researcher |
-| Module boundary | 2x | Has index.ts/__init__.py | bash |
-| Symbol density | 2x | >30 symbols | LSP |
-| Export count | 2x | >10 exports | LSP |
-| Reference centrality | 3x | >20 refs | LSP |
-
-### Decision Rules
-
-| Score | Action |
-|-------|--------|
-| **Root (.)** | ALWAYS create |
-| **>15** | Create AGENTS.md |
-| **8-15** | Create if distinct domain |
-| **<8** | Skip (parent covers) |
-
-### Output
-\`\`\`
-AGENTS_LOCATIONS = [
-  { path: ".", type: "root" },
-  { path: "src/hooks", score: 18, reason: "high complexity" },
-  { path: "src/api", score: 12, reason: "distinct domain" }
-]
-\`\`\`
-
-**Mark "scoring" as completed.**
-
----
-
-## Phase 3: Generate AGENTS.md
-
-**Mark "generate" as in_progress.**
-
-<critical>
-**File Writing Rule**: If AGENTS.md already exists at the target path → use \`Edit\` tool. If it does NOT exist → use \`Write\` tool.
-NEVER use Write to overwrite an existing file. ALWAYS check existence first via \`Read\` or discovery results.
-</critical>
-
-### Root AGENTS.md (Full Treatment)
-
-\`\`\`markdown
-# PROJECT KNOWLEDGE BASE
-
-**Generated:** {TIMESTAMP}
-**Commit:** {SHORT_SHA}
-**Branch:** {BRANCH}
-
-## OVERVIEW
-{1-2 sentences: what + core stack}
-
-## STRUCTURE
-\\\`\\\`\\\`
-{root}/
-├── {dir}/    # {non-obvious purpose only}
-└── {entry}
-\\\`\\\`\\\`
-
-## WHERE TO LOOK
-| Task | Location | Notes |
-|------|----------|-------|
-
-## CODE MAP
-{From LSP - skip if unavailable or project <10 files}
-
-| Symbol | Type | Location | Refs | Role |
-|--------|------|----------|------|------|
-
-## CONVENTIONS
-{ONLY deviations from standard}
-
-## ANTI-PATTERNS (THIS PROJECT)
-{Explicitly forbidden here}
-
-## UNIQUE STYLES
-{Project-specific}
-
-## COMMANDS
-\\\`\\\`\\\`bash
-{dev/test/build}
-\\\`\\\`\\\`
-
-## NOTES
-{Gotchas}
-\`\`\`
-
-**Quality gates**: 50-150 lines, no generic advice, no obvious info.
-
-### Subdirectory AGENTS.md (Parallel)
-
-Launch writing tasks for each location:
-
-\`\`\`
-for loc in AGENTS_LOCATIONS (except root):
-  task(category="writing", load_skills=[], run_in_background=false, description="Generate AGENTS.md", prompt=\\\`
-    Generate AGENTS.md for: \${loc.path}
-    - Reason: \${loc.reason}
-    - 30-80 lines max
-    - NEVER repeat parent content
-    - Sections: OVERVIEW (1 line), STRUCTURE (if >5 subdirs), WHERE TO LOOK, CONVENTIONS (if different), ANTI-PATTERNS
-  \\\`)
-\`\`\`
-
-**Wait for all. Mark "generate" as completed.**
-
----
-
-## Phase 4: Review & Deduplicate
-
-**Mark "review" as in_progress.**
-
-For each generated file:
-- Remove generic advice
-- Remove parent duplicates
-- Trim to size limits
-- Verify telegraphic style
-
-**Mark "review" as completed.**
-
----
-
-## Final Report
-
-\`\`\`
-=== init-deep Complete ===
-
-Mode: {update | create-new}
-
-Files:
-  [OK] ./AGENTS.md (root, {N} lines)
-  [OK] ./src/hooks/AGENTS.md ({N} lines)
-
-Dirs Analyzed: {N}
-AGENTS.md Created: {N}
-AGENTS.md Updated: {N}
-
-Hierarchy:
-  ./AGENTS.md
-  └── src/hooks/AGENTS.md
-\`\`\`
-
----
-
-## Anti-Patterns
-
-- **Static agent count**: MUST vary agents based on project size/depth
-- **Sequential execution**: MUST parallel (researcher + LSP concurrent)
-- **Ignoring existing**: ALWAYS read existing first, even with --create-new
-- **Over-documenting**: Not every dir needs AGENTS.md
-- **Redundancy**: Child never repeats parent
-- **Generic content**: Remove anything that applies to ALL projects
-- **Verbose style**: Telegraphic or die`

package/src/features/builtin-commands/templates/mcp-status.ts

@@ -1,36 +0,0 @@
-export const MCP_STATUS_TEMPLATE = `# MCP Status Command
-
-## Purpose
-
-Use /mcp-status to show the effective hiai-opencode MCP setup without relying on OpenCode's mcp list output.
-
-## Execute
-
-Run:
-
-\`\`\`bash
-hiai-opencode mcp-status
-\`\`\`
-
-If the binary is not on PATH, try the package-local fallback:
-
-\`\`\`bash
-node ./node_modules/@hiai-gg/hiai-opencode/assets/cli/hiai-opencode.mjs mcp-status
-\`\`\`
-
-## Report
-
-Summarize the output in a compact status table:
-
-- MCP server name
-- status: ok, warning, error, disabled
-- cause or next action
-
-Rules:
-
-- Do not print API key values.
-- If a key is missing, name the env var only.
-- If a runtime is missing, give the exact install hint from the command output or the shortest safe next command.
-- Do not edit config unless the user explicitly asks.
-- Do not run package installs unless the user explicitly asks.
-`

package/src/features/builtin-commands/templates/ralph-loop.ts

@@ -1,66 +0,0 @@
-export const RALPH_LOOP_TEMPLATE = `You are starting a Ralph Loop - a self-referential development loop that runs until task completion.
-
-## How Ralph Loop Works
-
-1. You will work on the task continuously
-2. When you believe the task is FULLY complete, output: \`<promise>{{COMPLETION_PROMISE}}</promise>\`
-3. If you don't output the promise, the loop will automatically inject another prompt to continue
-4. Maximum iterations: Configurable (default 100)
-
-## Rules
-
-- Focus on completing the task fully, not partially
-- Don't output the completion promise until the task is truly done
-- Each iteration should make meaningful progress toward the goal
-- If stuck, try different approaches
-- Use todos to track your progress
-
-## Exit Conditions
-
-1. **Completion**: Output your completion promise tag when fully complete
-2. **Max Iterations**: Loop stops automatically at limit
-3. **Cancel**: User runs \`/cancel-ralph\` command
-
-## Your Task
-
-Parse the arguments below and begin working on the task. The format is:
-\`"task description" [--completion-promise=TEXT] [--max-iterations=N] [--strategy=reset|continue]\`
-
-Default completion promise is "DONE" and default max iterations is 100.`
-
-export const ULW_LOOP_TEMPLATE = `You are starting an ULTRAWORK Loop - a self-referential development loop that runs until verified completion.
-
-## How ULTRAWORK Loop Works
-
-1. You will work on the task continuously
-2. When you believe the work is complete, output: \`<promise>{{COMPLETION_PROMISE}}</promise>\`
-3. That does NOT finish the loop yet. The system will require Critic verification
-4. The loop only ends after the system confirms Critic verified the result
-5. The iteration limit is 500 for ultrawork mode, 100 for normal mode
-
-## Rules
-
-- Focus on finishing the task completely
-- After you emit the completion promise, run Critic verification when instructed
-- Do not treat DONE as final completion until Critic verifies it
-
-## Exit Conditions
-
-1. **Verified Completion**: Critic verifies the result and the system confirms it
-2. **Cancel**: User runs \`/cancel-ralph\`
-
-## Your Task
-
-Parse the arguments below and begin working on the task. The format is:
-\`"task description" [--completion-promise=TEXT] [--strategy=reset|continue]\`
-
-Default completion promise is "DONE".`
-
-export const CANCEL_RALPH_TEMPLATE = `Cancel the currently active Ralph Loop.
-
-This will:
-1. Stop the loop from continuing
-2. Clear the loop state file
-3. Allow the session to end normally
-
-Check if a loop is active and cancel it. Inform the user of the result.`