@thanhthi2895/luna-ai 2.16.2

package/agentic/opencode/.opencode/skills/team/references/opencode-runner.md

@@ -0,0 +1,115 @@
+# OpenCode Runner — Subprocess Pattern Reference
+
+How to use `spawn-team.sh` to run parallel `opencode` agents from within `lu:team`.
+
+## Usage Pattern
+
+```bash
+bash agentic/opencode/.opencode/scripts/spawn-team.sh \
+  <output-dir> \
+  <timeout-seconds> \
+  <prompt-file-1> [<prompt-file-2> ...]
+```
+
+**Arguments:**
+- `output-dir` — directory where agent reports are written (e.g., `plans/reports/team-{timestamp}/`)
+- `timeout-seconds` — max seconds per agent before watchdog kills it (default: 300)
+- `prompt-file-N` — text files containing each agent's full prompt
+
+## Step-by-Step from lu:team Skill
+
+### Step 1 — Write prompt files
+
+Use `write_file` for each agent role:
+
+```
+write_file /tmp/luna-team-researcher-1.txt  ← researcher prompt
+write_file /tmp/luna-team-researcher-2.txt  ← researcher prompt
+```
+
+Prompt files must be plain text. Use templates from `references/prompt-researcher.md`, `references/prompt-reviewer.md`, `references/prompt-debugger.md`.
+
+### Step 2 — Spawn agents
+
+Use `bash`:
+
+```bash
+bash agentic/opencode/.opencode/scripts/spawn-team.sh \
+  plans/reports/team-$(date +%y%m%d-%H%M) \
+  300 \
+  /tmp/luna-team-researcher-1.txt \
+  /tmp/luna-team-researcher-2.txt
+```
+
+The script will:
+- Spawn all agents with `opencode run` in parallel (`&`)
+- Stagger spawns by 2s (rate limit protection)
+- Start watchdog subprocess per agent (macOS-compatible timeout)
+- Wait for all agents, report ✓/✗ per agent
+- Cap each output at 500 lines
+- Print summary table with file sizes
+
+### Step 3 — Read results
+
+After `bash` exits (exit 0 = all OK, exit 1 = some failed):
+
+```
+read_file plans/reports/team-{timestamp}/agent-1.md
+read_file plans/reports/team-{timestamp}/agent-2.md
+...
+```
+
+Read in parallel — issue all `read_file` calls in one response block.
+
+### Step 4 — Synthesize
+
+Write synthesis to `plans/reports/` using `write_file`:
+
+```
+plans/reports/research-summary-{timestamp}-{topic}.md
+plans/reports/review-{scope}.md
+plans/reports/debug-{issue}.md
+```
+
+### Step 5 — Cleanup
+
+```bash
+bash: rm /tmp/luna-team-*.txt
+```
+
+## Output Format Notes
+
+Each agent output starts with OpenCode header (strip if needed):
+```
+> build · gpt-5.3-codex
+
+[actual content]
+```
+
+Strip with: `tail -n +3` or `grep -v "^> build"`
+
+## Timeout Values by Template
+
+| Template | Recommended Timeout |
+|----------|-------------------|
+| research | 300s (5 min) |
+| review | 240s (4 min) |
+| debug | 360s (6 min) |
+| cook | N/A — sequential |
+
+## Model Recommendations
+
+| Role | Recommended | Flag |
+|------|-------------|------|
+| researcher | default (gpt-5.3-codex) | (none) |
+| reviewer | default | (none) |
+| debugger | default | (none) |
+| Override | specific model | `--model provider/model` |
+
+Note: `--model` flag must be added to `opencode run` call inside `spawn-team.sh` if needed.
+
+## Error Handling
+
+- **Exit 0**: All agents succeeded → proceed to synthesis
+- **Exit 1**: One or more failed → check individual `agent-N.md` for error messages → decide whether to retry or proceed with partial results
+- **Exit 2**: opencode not in PATH → tell user to install opencode

package/agentic/opencode/.opencode/skills/team/references/prompt-debugger.md

@@ -0,0 +1,74 @@
+# Debugger Prompt Template
+
+Use this template for debugger agents in `/team debug`.
+
+Fill in `{variables}` before writing to `/tmp/luna-team-debugger-N.txt`.
+
+---
+
+```
+You are a debugger testing a specific hypothesis.
+
+ISSUE: {issue_description}
+YOUR HYPOTHESIS: {hypothesis}
+PROJECT DIR: {project_dir}
+
+Your job: PROVE or DISPROVE your hypothesis using concrete evidence.
+Be adversarial to yourself — actively look for evidence that contradicts your hypothesis.
+
+Steps:
+1. Look for evidence SUPPORTING your hypothesis (read files, check patterns)
+2. Actively look for evidence DISPROVING your hypothesis
+3. Make a final verdict
+
+Write a markdown report with EXACTLY these sections:
+
+# Hypothesis
+{restate your hypothesis in one sentence}
+
+# Supporting Evidence
+(concrete: file:line, command output, or pattern found)
+- Evidence 1
+- Evidence 2
+
+# Contradicting Evidence
+(what DISPROVES your hypothesis — be honest)
+- Evidence 1 (or "None found")
+
+# Verdict
+CONFIRMED / DISPROVED / INCONCLUSIVE
+
+# If CONFIRMED — Recommended Fix
+(specific: which file, what to change, why)
+
+# If DISPROVED — Alternative Hypothesis
+(what seems more likely based on what you found)
+
+RULES:
+- No "seems" or "probably" — only verifiable evidence
+- Output ONLY the markdown report
+- Max 300 lines
+- Project files are in: {project_dir}
+```
+
+---
+
+## Variable Reference
+
+| Variable | Description | Example |
+|----------|-------------|---------|
+| `{issue_description}` | The bug/problem being debugged | "lu:team references TeamCreate which doesn't exist" |
+| `{hypothesis}` | This debugger's theory | "The SKILL.md was never updated when migrating from Claude Code" |
+| `{project_dir}` | Absolute path | "/Users/user/my-project" |
+
+## Hypothesis Generation Guide
+
+For N=3 debuggers, generate hypotheses that:
+- Are **mutually exclusive** (different root causes)
+- Are **independently testable** (different evidence to look for)
+- Cover **different layers** (e.g., config vs code vs environment)
+
+**Example for "API calls failing":**
+- Hypothesis 1: Authentication token is expired or invalid
+- Hypothesis 2: API endpoint URL has changed
+- Hypothesis 3: Network/firewall blocking outbound requests

package/agentic/opencode/.opencode/skills/team/references/prompt-researcher.md

@@ -0,0 +1,62 @@
+# Researcher Prompt Template
+
+Use this template to generate prompt files for researcher agents in `/team research`.
+
+Fill in `{variables}` before writing to `/tmp/luna-team-researcher-N.txt`.
+
+---
+
+```
+You are a technical researcher. Your task:
+
+TOPIC: {topic}
+RESEARCH ANGLE: {angle_description}
+PROJECT DIR: {project_dir}
+
+Research this angle thoroughly using available tools (read files, search web, analyze code).
+
+Write a markdown report with EXACTLY these sections:
+
+# Executive Summary
+(2-3 sentences: what you found and why it matters)
+
+# Key Findings
+(bullet list — concrete facts only, no "seems" or "probably")
+- Finding 1
+- Finding 2
+- ...
+
+# Evidence
+(code samples, file references as file:line, links, or codebase patterns found)
+
+# Recommendations
+(actionable, specific — what to do based on findings)
+
+# Open Questions
+(what remains unclear or needs further investigation)
+
+RULES:
+- Output ONLY the markdown report — no preamble, no "Here is my report:"
+- Be concrete — every claim needs evidence
+- Max 400 lines total
+- If reading project files, they are in: {project_dir}
+```
+
+---
+
+## Variable Reference
+
+| Variable | Description | Example |
+|----------|-------------|---------|
+| `{topic}` | Full topic from user | "parallel AI agent orchestration" |
+| `{angle_description}` | This researcher's specific angle | "Architecture and proven patterns" |
+| `{project_dir}` | Absolute path to project | "/Users/user/my-project" |
+
+## Angle Suggestions by N
+
+| N | Angles |
+|---|--------|
+| 2 | Architecture + Risks |
+| 3 | Architecture + Alternatives + Risks |
+| 4 | Architecture + Alternatives + Risks + Implementation |
+| 5 | Architecture + Alternatives + Risks + Implementation + Security |

package/agentic/opencode/.opencode/skills/team/references/prompt-reviewer.md

@@ -0,0 +1,54 @@
+# Reviewer Prompt Template
+
+Use this template for reviewer agents in `/team review`.
+
+Fill in `{variables}` before writing to `/tmp/luna-team-reviewer-N.txt`.
+
+---
+
+```
+You are a code reviewer with focus on: {focus_area}
+
+SCOPE: {scope_description}
+PROJECT DIR: {project_dir}
+
+Review the codebase for {focus_area} issues. Read relevant files, run analysis.
+
+For each finding use EXACTLY this format:
+[{SEVERITY}] {finding} — {evidence} — {recommendation}
+
+Where SEVERITY is one of:
+- CRITICAL: blocks release, must fix now
+- IMPORTANT: should fix before next release
+- MODERATE: nice to have, technical debt
+
+Start your output with a 2-line summary:
+Total findings: {N} ({X} CRITICAL, {Y} IMPORTANT, {Z} MODERATE)
+Focus area: {focus_area}
+
+Then list findings, CRITICAL first.
+
+RULES:
+- Evidence MUST be concrete: file:line or specific command output
+- NO "seems", "probably", "might" — only what you can verify
+- Max 50 findings total
+- Output ONLY the findings list + summary header — no preamble
+```
+
+---
+
+## Variable Reference
+
+| Variable | Description | Example |
+|----------|-------------|---------|
+| `{focus_area}` | Review focus | "Security", "Performance", "Test Coverage" |
+| `{scope_description}` | What to review | "~/.config/opencode/skills/ — check for stale references" |
+| `{project_dir}` | Absolute path | "/Users/user/my-project" |
+
+## Default Focus Areas (3 reviewers)
+
+| Reviewer | Focus | Key Checks |
+|----------|-------|------------|
+| 1 | Security | OWASP top 10, auth gaps, secrets in code, input validation |
+| 2 | Performance | N+1 queries, memory leaks, O(n²) algorithms, blocking I/O |
+| 3 | Test Coverage | Untested paths, missing edge cases, flaky tests, no error path tests |

package/agentic/opencode/.opencode/skills/team/scripts/spawn-team.sh

@@ -0,0 +1,142 @@
+#!/usr/bin/env bash
+# spawn-team.sh — Luna AI Parallel OpenCode Agent Spawner
+#
+# Usage:
+#   bash spawn-team.sh <output-dir> <timeout-seconds> <prompt-file-1> [prompt-file-2 ...]
+#
+# Each prompt file: plain text containing the full prompt for one agent.
+# Spawns all agents in parallel via `opencode run`, writes results to <output-dir>/agent-N.md
+#
+# Exit codes:
+#   0 — all agents completed successfully
+#   1 — one or more agents failed or timed out
+#   2 — preflight check failed (opencode not found)
+#
+# Luna AI — https://github.com/thanhthi2895/luna-ai
+
+set -uo pipefail
+
+# ─── Preflight ────────────────────────────────────────────────────────────────
+
+if ! command -v opencode &>/dev/null; then
+  echo "ERROR: opencode not found in PATH." >&2
+  echo "Install from: https://opencode.ai" >&2
+  exit 2
+fi
+
+if [[ $# -lt 3 ]]; then
+  echo "Usage: spawn-team.sh <output-dir> <timeout-seconds> <prompt-file-1> [prompt-file-2 ...]" >&2
+  exit 1
+fi
+
+OUTPUT_DIR="$1"
+TIMEOUT="${2:-300}"
+shift 2
+PROMPT_FILES=("$@")
+N="${#PROMPT_FILES[@]}"
+
+mkdir -p "$OUTPUT_DIR"
+
+# ─── Config ───────────────────────────────────────────────────────────────────
+
+SPAWN_DELAY=2        # seconds between spawns (avoid rate limit burst)
+MAX_LINES=500        # max output lines per agent report
+PROJECT_DIR="$(pwd)" # bind each subprocess to current project
+
+# ─── Spawn agents in parallel ─────────────────────────────────────────────────
+
+echo "🚀 Spawning $N agents in parallel (timeout: ${TIMEOUT}s each)..."
+echo ""
+
+PIDS=()
+WATCHDOG_PIDS=()
+LABELS=()
+
+for i in "${!PROMPT_FILES[@]}"; do
+  PROMPT_FILE="${PROMPT_FILES[$i]}"
+  LABEL="agent-$((i + 1))"
+  OUTPUT="$OUTPUT_DIR/$LABEL.md"
+
+  if [[ ! -f "$PROMPT_FILE" ]]; then
+    echo "ERROR: Prompt file not found: $PROMPT_FILE" >&2
+    exit 1
+  fi
+
+  # Spawn agent (OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS auto-approves file access in non-interactive mode)
+  OPENCODE_DANGEROUSLY_SKIP_PERMISSIONS=true opencode run "$(cat "$PROMPT_FILE")" \
+    --dir "$PROJECT_DIR" \
+    > "$OUTPUT" 2>&1 &
+  AGENT_PID=$!
+  PIDS+=("$AGENT_PID")
+  LABELS+=("$LABEL")
+
+  # Watchdog: kill agent if it exceeds timeout (macOS-compatible)
+  (
+    sleep "$TIMEOUT"
+    if kill -0 "$AGENT_PID" 2>/dev/null; then
+      echo "⏱  $LABEL timed out after ${TIMEOUT}s — killing" >&2
+      kill "$AGENT_PID" 2>/dev/null
+    fi
+  ) &
+  WATCHDOG_PIDS+=($!)
+
+  echo "  ↳ $LABEL spawned (PID: $AGENT_PID)"
+
+  # Stagger spawns to avoid rate limit burst
+  if [[ $i -lt $((N - 1)) ]]; then
+    sleep "$SPAWN_DELAY"
+  fi
+done
+
+echo ""
+echo "⏳ Waiting for all agents to complete..."
+echo ""
+
+# ─── Wait & collect results ───────────────────────────────────────────────────
+
+FAILED=0
+
+for i in "${!PIDS[@]}"; do
+  PID="${PIDS[$i]}"
+  LABEL="${LABELS[$i]}"
+  OUTPUT="$OUTPUT_DIR/$LABEL.md"
+
+  if wait "$PID" 2>/dev/null; then
+    # Cap output size
+    if [[ -f "$OUTPUT" ]]; then
+      LINE_COUNT=$(wc -l < "$OUTPUT")
+      if [[ "$LINE_COUNT" -gt "$MAX_LINES" ]]; then
+        tail -"$MAX_LINES" "$OUTPUT" > "$OUTPUT.tmp" && mv "$OUTPUT.tmp" "$OUTPUT"
+        echo "✓ $LABEL — completed (truncated to $MAX_LINES lines)"
+      else
+        echo "✓ $LABEL — completed ($LINE_COUNT lines)"
+      fi
+    else
+      echo "✓ $LABEL — completed (no output)"
+    fi
+  else
+    EXIT_CODE=$?
+    echo "✗ $LABEL — FAILED (exit $EXIT_CODE)"
+    FAILED=1
+  fi
+
+  # Kill watchdog (suppress "Terminated" noise)
+  { kill "${WATCHDOG_PIDS[$i]}" 2>/dev/null; wait "${WATCHDOG_PIDS[$i]}" 2>/dev/null; } || true
+done
+
+echo ""
+
+# ─── Summary ──────────────────────────────────────────────────────────────────
+
+TOTAL=$N
+SUCCESS=$(grep -c "^✓" <<< "$(for i in "${!PIDS[@]}"; do
+  [[ -f "$OUTPUT_DIR/${LABELS[$i]}.md" ]] && echo "✓" || echo "✗"
+done)" 2>/dev/null || echo "$((N - FAILED))")
+
+echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+echo "Results: $((N - FAILED))/$N agents succeeded"
+echo "Output:  $OUTPUT_DIR/"
+ls -la "$OUTPUT_DIR"/*.md 2>/dev/null | awk '{print "  " $NF " (" $5 " bytes)"}'
+echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+
+exit $FAILED

package/agentic/opencode/.opencode/skills/test/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: lu:test
+author: luna
+description: "Run unit, integration, e2e, and UI tests. Use for test execution, coverage analysis, build verification, visual regression, and QA reports."
+version: 1.0.0
+argument-hint: "[context] OR ui [url]"
+---
+
+# Testing & Quality Assurance
+
+Comprehensive testing framework covering unit/integration/e2e tests, UI/visual testing, coverage analysis, and structured QA reporting.
+
+## Default (No Arguments)
+
+If invoked without arguments, use `AskUserQuestion`:
+
+| Operation | Description |
+|-----------|-------------|
+| `(default)` | Run unit/integration/e2e tests |
+| `ui` | Run UI tests on a website |
+
+## Core Principle
+
+**NEVER IGNORE FAILING TESTS.** Fix root causes, not symptoms. No mocks/cheats to pass builds.
+
+## When to Use
+
+- **After implementation**: Validate new features or bug fixes
+- **Coverage checks**: Ensure coverage meets project thresholds (80%+)
+- **UI verification**: Visual regression, responsive layout, accessibility
+- **Build validation**: Verify build process, CI/CD compatibility
+- **Pre-commit/push**: Final quality gate
+
+## Workflows
+
+### 1. Code Testing (`references/test-execution-workflow.md`)
+Execute test suites, analyze results, generate coverage. Supports JS/TS (Jest/Vitest/Mocha), Python (pytest), Go, Rust, Flutter.
+
+**Load when:** Running unit/integration/e2e tests, checking coverage
+
+### 2. UI Testing (`references/ui-testing-workflow.md`)
+Browser-based visual testing via `chrome-devtools` skill. Screenshots, responsive checks, accessibility, console errors.
+
+**Load when:** Visual regression testing, UI bugs, responsive layout checks
+
+### 3. Report Format (`references/report-format.md`)
+Structured QA report template: results overview, coverage metrics, failed tests, recommendations.
+
+**Load when:** Generating test summary reports
+
+## Working Process
+
+1. Identify testing scope from recent changes
+2. Run typecheck/analyze commands first (catch syntax errors early)
+3. Execute appropriate test suites
+4. Analyze results — focus on failures
+5. Generate coverage reports if applicable
+6. For frontend: use `chrome-devtools` skill for UI testing
+7. Produce structured summary report
+
+## Tools Integration
+
+- **Test runners**: Jest, Vitest, pytest, go test, cargo test, flutter test
+- **Coverage**: Istanbul/c8, pytest-cov, go cover
+- **Browser**: `chrome-devtools` skill for visual testing
+- **Debugging**: `debugger` skill when tests reveal bugs requiring investigation
+- **Analysis**: `sequential-thinking` skill for complex test failure analysis
+
+## Quality Standards
+
+- All critical paths must have test coverage
+- Validate happy path AND error scenarios
+- Ensure test isolation — no interdependencies
+- Tests must be deterministic and reproducible
+- Never ignore failing tests to pass the build

package/agentic/opencode/.opencode/skills/test/references/report-format.md

@@ -0,0 +1,58 @@
+# Test Report Format
+
+Structured QA report template. Sacrifice grammar for concision.
+
+## Template
+
+```markdown
+# Test Report — {date} — {scope}
+
+## Test Results Overview
+- **Total**: X tests
+- **Passed**: X | **Failed**: X | **Skipped**: X
+- **Duration**: Xs
+
+## Coverage Metrics
+| Metric   | Value | Threshold | Status |
+|----------|-------|-----------|--------|
+| Lines    | X%    | 80%       | PASS/FAIL |
+| Branches | X%    | 70%       | PASS/FAIL |
+| Functions| X%    | 80%       | PASS/FAIL |
+
+## Failed Tests
+### `test/path/file.test.ts` — TestName
+- **Error**: Error message
+- **Stack**: Relevant stack trace (truncated)
+- **Cause**: Brief root cause analysis
+- **Fix**: Suggested resolution
+
+## UI Test Results (if applicable)
+- **Pages tested**: X
+- **Screenshots**: ./screenshots/
+- **Console errors**: none | [list]
+- **Responsive**: checked at [viewports] | skipped
+- **Performance**: LCP Xs, FID Xms, CLS X
+
+## Build Status
+- **Build**: PASS/FAIL
+- **Warnings**: none | [list]
+- **Dependencies**: all resolved | [issues]
+
+## Critical Issues
+1. [Blocking issue description + impact]
+
+## Recommendations
+1. [Actionable improvement with priority]
+
+## Unresolved Questions
+- [Any open questions, if any]
+```
+
+## Guidelines
+
+- Include ALL failed tests with error messages — don't summarize away details
+- Coverage: highlight specific uncovered files/functions, not just percentages
+- Screenshots: embed paths directly in report for easy access
+- Recommendations: prioritize by impact (critical > high > medium > low)
+- Keep report under 200 lines — split into sections if larger scope needed
+- Save report using naming pattern from `## Naming` section injected by hooks

package/agentic/opencode/.opencode/skills/test/references/test-execution-workflow.md

@@ -0,0 +1,103 @@
+# Test Execution Workflow
+
+## Step 1: Identify Scope
+
+Determine what to test based on recent changes:
+- New feature → full test suite + new test cases
+- Bug fix → regression tests + targeted fix validation
+- Refactor → existing test suite (no new tests unless gaps found)
+- Coverage check → full suite with coverage flags
+
+## Step 2: Pre-flight Checks
+
+Run syntax/type checks before tests to catch compile errors early:
+
+```bash
+# JavaScript/TypeScript
+npx tsc --noEmit          # TypeScript check
+npx eslint .              # Lint check
+
+# Python
+python -m py_compile file.py
+flake8 .
+
+# Flutter
+flutter analyze
+
+# Go
+go vet ./...
+
+# Rust
+cargo check
+```
+
+## Step 3: Execute Tests
+
+### JavaScript/TypeScript
+```bash
+npm test                    # or yarn test / pnpm test / bun test
+npm run test:coverage       # with coverage
+npx vitest run              # Vitest
+npx jest --coverage         # Jest with coverage
+```
+
+### Python
+```bash
+pytest                      # basic
+pytest --cov=src --cov-report=term-missing  # with coverage
+python -m unittest discover # unittest
+```
+
+### Go / Rust / Flutter
+```bash
+go test ./... -cover        # Go with coverage
+cargo test                  # Rust
+flutter test --coverage     # Flutter
+```
+
+## Step 4: Analyze Results
+
+Focus on:
+1. **Failing tests** — read error messages and stack traces carefully
+2. **Flaky tests** — tests that pass/fail intermittently indicate race conditions or state leaks
+3. **Slow tests** — identify bottlenecks (>5s per test is suspicious)
+4. **Skipped tests** — ensure skips are intentional, not hiding failures
+
+## Step 5: Coverage Analysis
+
+Thresholds:
+- **80%+** line coverage — standard minimum
+- **70%+** branch coverage — acceptable for most projects
+- Focus on critical paths: auth, payment, data mutations
+
+Identify gaps:
+- Uncovered error handlers
+- Missing edge case branches
+- Untested utility functions
+
+## Step 6: Build Verification
+
+```bash
+npm run build               # JS/TS production build
+python setup.py build       # Python
+go build ./...              # Go
+cargo build --release       # Rust
+flutter build               # Flutter
+```
+
+Check for:
+- Build warnings or deprecation notices
+- Unresolved dependencies
+- Production config correctness
+
+## Quality Checklist
+
+- [ ] All tests pass (zero failures)
+- [ ] Coverage meets project threshold
+- [ ] No flaky tests detected
+- [ ] Build completes without errors
+- [ ] Error scenarios tested
+- [ ] Test isolation verified (no shared state)
+- [ ] Test data cleaned up after execution
+- [ ] Mocks/stubs properly configured
+- [ ] Environment variables correctly set