@lavralabs/lavra 0.7.0

package/plugins/lavra/gemini/commands/test-browser.toml

@@ -0,0 +1,307 @@
+# Generated by lavra v0.6.0
+# DO NOT EDIT - changes will be overwritten on next install
+
+description = "Run browser tests on pages affected by current PR or branch"
+
+prompt = """
+
+<objective>
+Run end-to-end browser tests on pages affected by a PR or branch changes using the agent-browser CLI, catching JavaScript integration bugs, CSS/layout regressions, user workflow breakages, and console errors.
+</objective>
+
+<execution_context>
+<test_target> {{args}} </test_target>
+</execution_context>
+
+<context>
+
+### Prerequisites
+
+- Local development server running (e.g., `bin/dev`, `rails server`, `npm run dev`)
+- agent-browser CLI installed (see Setup below)
+- Git repository with changes to test
+
+### Setup
+
+**Check installation:**
+```bash
+command -v agent-browser >/dev/null 2>&1 && echo "Installed" || echo "NOT INSTALLED"
+```
+
+**Install if needed:**
+```bash
+npm install -g agent-browser
+agent-browser install  # Downloads Chromium (~160MB)
+```
+
+See the `agent-browser` skill for detailed usage.
+
+### agent-browser CLI Reference
+
+```bash
+# Navigation
+agent-browser open <url>           # Navigate to URL
+agent-browser back                 # Go back
+agent-browser close                # Close browser
+
+# Snapshots (get element refs)
+agent-browser snapshot -i          # Interactive elements with refs (@e1, @e2, etc.)
+agent-browser snapshot -i --json   # JSON output
+
+# Interactions (use refs from snapshot)
+agent-browser click @e1            # Click element
+agent-browser fill @e1 "text"      # Fill input
+agent-browser type @e1 "text"      # Type without clearing
+agent-browser press Enter          # Press key
+
+# Screenshots
+agent-browser screenshot out.png       # Viewport screenshot
+agent-browser screenshot --full out.png # Full page screenshot
+
+# Headed mode (visible browser)
+agent-browser --headed open <url>      # Open with visible browser
+agent-browser --headed click @e1       # Click in visible browser
+
+# Wait
+agent-browser wait @e1             # Wait for element
+agent-browser wait 2000            # Wait milliseconds
+```
+
+</context>
+
+<guardrails>
+
+**DO NOT use Chrome MCP tools (mcp__claude-in-chrome__*).**
+
+This command uses the `agent-browser` CLI exclusively. The agent-browser CLI is a Bash-based tool from Vercel that runs headless Chromium. It is NOT the same as Chrome browser automation via MCP.
+
+If you find yourself calling `mcp__claude-in-chrome__*` tools, STOP. Use `agent-browser` Bash commands instead.
+
+</guardrails>
+
+<process>
+
+## 0. Verify agent-browser Installation
+
+Before starting ANY browser testing, verify agent-browser is installed:
+
+```bash
+command -v agent-browser >/dev/null 2>&1 && echo "Ready" || (echo "Installing..." && npm install -g agent-browser && agent-browser install)
+```
+
+If installation fails, inform the user and stop.
+
+## 1. Ask Browser Mode
+
+Before starting tests, ask user if they want to watch the browser:
+
+Use AskUserQuestion with:
+- Question: "Do you want to watch the browser tests run?"
+- Options:
+  1. **Headed (watch)** - Opens visible browser window so you can see tests run
+  2. **Headless (faster)** - Runs in background, faster but invisible
+
+Store the choice and use `--headed` flag when user selects "Headed".
+
+## 2. Determine Test Scope
+
+**If PR number provided:**
+```bash
+gh pr view [number] --json files -q '.files[].path'
+```
+
+**If 'current' or empty:**
+```bash
+git diff --name-only main...HEAD
+```
+
+**If branch name provided:**
+```bash
+git diff --name-only main...[branch]
+```
+
+## 3. Map Files to Routes
+
+Map changed files to testable routes:
+
+| File Pattern | Route(s) |
+|-------------|----------|
+| `app/views/users/*` | `/users`, `/users/:id`, `/users/new` |
+| `app/controllers/settings_controller.rb` | `/settings` |
+| `app/javascript/controllers/*_controller.js` | Pages using that Stimulus controller |
+| `app/components/*_component.rb` | Pages rendering that component |
+| `app/views/layouts/*` | All pages (test homepage at minimum) |
+| `app/assets/stylesheets/*` | Visual regression on key pages |
+| `app/helpers/*_helper.rb` | Pages using that helper |
+| `src/app/*` (Next.js) | Corresponding routes |
+| `src/components/*` | Pages using those components |
+
+Build a list of URLs to test based on the mapping.
+
+## 4. Verify Server is Running
+
+Before testing, verify the local server is accessible:
+
+```bash
+agent-browser open http://localhost:3000
+agent-browser snapshot -i
+```
+
+If server is not running, inform user:
+```markdown
+**Server not running**
+
+Please start your development server:
+- Rails: `bin/dev` or `rails server`
+- Node/Next.js: `npm run dev`
+
+Then run `/test-browser` again.
+```
+
+## 5. Test Each Affected Page
+
+For each affected route, use agent-browser CLI commands (NOT Chrome MCP):
+
+**Step 1: Navigate and capture snapshot**
+```bash
+agent-browser open "http://localhost:3000/[route]"
+agent-browser snapshot -i
+```
+
+**Step 2: For headed mode (visual debugging)**
+```bash
+agent-browser --headed open "http://localhost:3000/[route]"
+agent-browser --headed snapshot -i
+```
+
+**Step 3: Verify key elements**
+- Use `agent-browser snapshot -i` to get interactive elements with refs
+- Page title/heading present
+- Primary content rendered
+- No error messages visible
+- Forms have expected fields
+
+**Step 4: Test critical interactions**
+```bash
+agent-browser click @e1  # Use ref from snapshot
+agent-browser snapshot -i
+```
+
+**Step 5: Take screenshots**
+```bash
+agent-browser screenshot page-name.png
+agent-browser screenshot --full page-name-full.png  # Full page
+```
+
+## 6. Human Verification (When Required)
+
+Pause for human input when testing touches:
+
+| Flow Type | What to Ask |
+|-----------|-------------|
+| OAuth | "Please sign in with [provider] and confirm it works" |
+| Email | "Check your inbox for the test email and confirm receipt" |
+| Payments | "Complete a test purchase in sandbox mode" |
+| SMS | "Verify you received the SMS code" |
+| External APIs | "Confirm the [service] integration is working" |
+
+Use AskUserQuestion:
+```markdown
+**Human Verification Needed**
+
+This test touches the [flow type]. Please:
+1. [Action to take]
+2. [What to verify]
+
+Did it work correctly?
+1. Yes - continue testing
+2. No - describe the issue
+```
+
+## 7. Handle Failures
+
+When a test fails:
+
+1. **Document the failure:**
+   - Screenshot the error state: `agent-browser screenshot error.png`
+   - Note the exact reproduction steps
+
+2. **Ask user how to proceed:**
+   ```markdown
+   **Test Failed: [route]**
+
+   Issue: [description]
+   Console errors: [if any]
+
+   How to proceed?
+   1. Fix now - I'll help debug and fix
+   2. Create bead - Add as a bead for later
+   3. Skip - Continue testing other pages
+   ```
+
+3. **If "Fix now":**
+   - Investigate the issue
+   - Propose a fix
+   - Apply fix
+   - Re-run the failing test
+
+4. **If "Create bead":**
+   - Create bead: `bd create "Browser test failure: {description}" --type bug --priority 1`
+   - Continue testing
+
+5. **If "Skip":**
+   - Log as skipped
+   - Continue testing
+
+## 8. Test Summary
+
+After all tests complete, present summary:
+
+```markdown
+## Browser Test Results
+
+**Test Scope:** PR #[number] / [branch name]
+**Server:** http://localhost:3000
+
+### Pages Tested: [count]
+
+| Route | Status | Notes |
+|-------|--------|-------|
+| `/users` | Pass | |
+| `/settings` | Pass | |
+| `/dashboard` | Fail | Console error: [msg] |
+| `/checkout` | Skip | Requires payment credentials |
+
+### Console Errors: [count]
+- [List any errors found]
+
+### Human Verifications: [count]
+- OAuth flow: Confirmed
+- Email delivery: Confirmed
+
+### Failures: [count]
+- `/dashboard` - [issue description]
+
+### Created Beads: [count]
+- BD-XXX: Browser test failure - dashboard error
+
+### Result: [PASS / FAIL / PARTIAL]
+```
+
+</process>
+
+<success_criteria>
+- [ ] All affected pages tested with agent-browser CLI
+- [ ] Each page has a Pass/Fail/Skip status
+- [ ] Console errors captured and reported
+- [ ] Screenshots taken for key pages
+- [ ] Failures documented with reproduction steps
+</success_criteria>
+
+<handoff>
+1. **Run `/lavra-review`** - Full code review of the changes
+2. **Fix failures** - Address test failures now
+3. **Done** - Accept results
+</handoff>
+
+"""

package/plugins/lavra/gemini/commands/xcode-test.toml

@@ -0,0 +1,289 @@
+# Generated by beads-compound v0.6.0
+# DO NOT EDIT - changes will be overwritten on next install
+
+description = "Build and test iOS apps on simulator using XcodeBuildMCP"
+
+prompt = """
+
+<objective>
+Build, install, and test iOS apps on the simulator using XcodeBuildMCP. Captures screenshots, logs, and verifies app behavior.
+</objective>
+
+<context>
+
+### Prerequisites
+
+- Xcode installed with command-line tools
+- XcodeBuildMCP server connected
+- Valid Xcode project or workspace
+- At least one iOS Simulator available
+
+### Integration with /beads-review
+
+When reviewing PRs that touch iOS code, the `/beads-review` command can spawn this as a subagent:
+
+```
+Task general-purpose("Run /xcode-test for scheme [name]. Build, install on simulator, test key screens, check for crashes.")
+```
+
+</context>
+
+<process>
+
+## 0. Verify XcodeBuildMCP is Installed
+
+**First, check if XcodeBuildMCP tools are available.**
+
+Try calling:
+```
+mcp__xcodebuildmcp__list_simulators({})
+```
+
+**If the tool is not found or errors:**
+
+Tell the user:
+```markdown
+**XcodeBuildMCP not installed**
+
+Please install the XcodeBuildMCP server first:
+
+\`\`\`bash
+claude mcp add XcodeBuildMCP -- npx xcodebuildmcp@latest
+\`\`\`
+
+Then restart Claude Code and run `/xcode-test` again.
+```
+
+**Do NOT proceed** until XcodeBuildMCP is confirmed working.
+
+## 1. Discover Project and Scheme
+
+**Find available projects:**
+```
+mcp__xcodebuildmcp__discover_projs({})
+```
+
+**List schemes for the project:**
+```
+mcp__xcodebuildmcp__list_schemes({ project_path: "/path/to/Project.xcodeproj" })
+```
+
+**If argument provided:**
+- Use the specified scheme name
+- Or "current" to use the default/last-used scheme
+
+## 2. Boot Simulator
+
+**List available simulators:**
+```
+mcp__xcodebuildmcp__list_simulators({})
+```
+
+**Boot preferred simulator (iPhone 15 Pro recommended):**
+```
+mcp__xcodebuildmcp__boot_simulator({ simulator_id: "[uuid]" })
+```
+
+**Wait for simulator to be ready:**
+Check simulator state before proceeding with installation.
+
+## 3. Build the App
+
+**Build for iOS Simulator:**
+```
+mcp__xcodebuildmcp__build_ios_sim_app({
+  project_path: "/path/to/Project.xcodeproj",
+  scheme: "[scheme_name]"
+})
+```
+
+**Handle build failures:**
+- Capture build errors
+- Create P1 bead for each build error
+- Report to user with specific error details
+
+**On success:**
+- Note the built app path for installation
+- Proceed to installation step
+
+## 4. Install and Launch
+
+**Install app on simulator:**
+```
+mcp__xcodebuildmcp__install_app_on_simulator({
+  app_path: "/path/to/built/App.app",
+  simulator_id: "[uuid]"
+})
+```
+
+**Launch the app:**
+```
+mcp__xcodebuildmcp__launch_app_on_simulator({
+  bundle_id: "[app.bundle.id]",
+  simulator_id: "[uuid]"
+})
+```
+
+**Start capturing logs:**
+```
+mcp__xcodebuildmcp__capture_sim_logs({
+  simulator_id: "[uuid]",
+  bundle_id: "[app.bundle.id]"
+})
+```
+
+## 5. Test Key Screens
+
+For each key screen in the app:
+
+**Take screenshot:**
+```
+mcp__xcodebuildmcp__take_screenshot({
+  simulator_id: "[uuid]",
+  filename: "screen-[name].png"
+})
+```
+
+**Review screenshot for:**
+- UI elements rendered correctly
+- No error messages visible
+- Expected content displayed
+- Layout looks correct
+
+**Check logs for errors:**
+```
+mcp__xcodebuildmcp__get_sim_logs({ simulator_id: "[uuid]" })
+```
+
+Look for:
+- Crashes
+- Exceptions
+- Error-level log messages
+- Failed network requests
+
+## 6. Human Verification (When Required)
+
+Pause for human input when testing touches:
+
+| Flow Type | What to Ask |
+|-----------|-------------|
+| Sign in with Apple | "Please complete Sign in with Apple on the simulator" |
+| Push notifications | "Send a test push and confirm it appears" |
+| In-app purchases | "Complete a sandbox purchase" |
+| Camera/Photos | "Grant permissions and verify camera works" |
+| Location | "Allow location access and verify map updates" |
+
+Use AskUserQuestion:
+```markdown
+**Human Verification Needed**
+
+This test requires [flow type]. Please:
+1. [Action to take on simulator]
+2. [What to verify]
+
+Did it work correctly?
+1. Yes - continue testing
+2. No - describe the issue
+```
+
+## 7. Handle Failures
+
+When a test fails:
+
+1. **Document the failure:**
+   - Take screenshot of error state
+   - Capture console logs
+   - Note reproduction steps
+
+2. **Ask user how to proceed:**
+   ```markdown
+   **Test Failed: [screen/feature]**
+
+   Issue: [description]
+   Logs: [relevant error messages]
+
+   How to proceed?
+   1. Fix now - I'll help debug and fix
+   2. Create bead - Add as a bead for later
+   3. Skip - Continue testing other screens
+   ```
+
+3. **If "Fix now":**
+   - Investigate the issue in code
+   - Propose a fix
+   - Rebuild and retest
+
+4. **If "Create bead":**
+   - Create bead: `bd create "Xcode test failure: {description}" --type bug --priority 1`
+   - Continue testing
+
+## 8. Test Summary
+
+After all tests complete, present summary:
+
+```markdown
+## Xcode Test Results
+
+**Project:** [project name]
+**Scheme:** [scheme name]
+**Simulator:** [simulator name]
+
+### Build: Success / Failed
+
+### Screens Tested: [count]
+
+| Screen | Status | Notes |
+|--------|--------|-------|
+| Launch | Pass | |
+| Home | Pass | |
+| Settings | Fail | Crash on tap |
+| Profile | Skip | Requires login |
+
+### Console Errors: [count]
+- [List any errors found]
+
+### Human Verifications: [count]
+- Sign in with Apple: Confirmed
+- Push notifications: Confirmed
+
+### Failures: [count]
+- Settings screen - crash on navigation
+
+### Created Beads: [count]
+- BD-XXX: Xcode test failure - settings crash
+
+### Result: [PASS / FAIL / PARTIAL]
+```
+
+## 9. Cleanup
+
+After testing:
+
+**Stop log capture:**
+```
+mcp__xcodebuildmcp__stop_log_capture({ simulator_id: "[uuid]" })
+```
+
+**Optionally shut down simulator:**
+```
+mcp__xcodebuildmcp__shutdown_simulator({ simulator_id: "[uuid]" })
+```
+
+</process>
+
+<success_criteria>
+- [ ] XcodeBuildMCP confirmed working before proceeding
+- [ ] App builds successfully for simulator
+- [ ] App installs and launches on simulator
+- [ ] Key screens tested with screenshots captured
+- [ ] Console logs checked for crashes and errors
+- [ ] Test summary report with Pass/Fail/Skip per screen
+</success_criteria>
+
+<handoff>
+1. **Run `/beads-review`** - Full code review of the changes
+2. **Fix failures** - Address test failures now
+3. **Done** - Accept results
+</handoff>
+
+"""

package/plugins/lavra/gemini/docs/MCP_SETUP.md

@@ -0,0 +1,41 @@
+# MCP Server Configuration for Gemini CLI
+
+The lavra plugin uses the Context7 MCP server for framework documentation.
+
+## Manual Configuration Required
+
+Gemini CLI does not support automatic MCP server installation. You need to manually add the server to your Gemini configuration.
+
+### Configuration File
+
+Add to `~/.config/gemini/settings.json`:
+
+```json
+{
+  "mcpServers": {
+    "context7": {
+      "command": "npx",
+      "args": ["-y", "@upwithcrowd/context7-mcp@latest"],
+      "env": {}
+    }
+  }
+}
+```
+
+### What Context7 Provides
+
+- Semantic search across PostgreSQL and TimescaleDB documentation
+- Framework-specific best practices and patterns
+- API reference lookups
+
+### Usage in Gemini CLI
+
+Once configured, use the `@context7` MCP tool to search documentation:
+
+```
+@context7 search_docs source=postgres query="create hypertable" search_type=semantic
+```
+
+## Security Note
+
+The Context7 MCP server runs as a subprocess with access to your environment. Only install if you trust the source.