@lavralabs/lavra 0.7.0

package/plugins/lavra/commands/optional/reproduce-bug.md

@@ -0,0 +1,97 @@
+---
+name: reproduce-bug
+description: "Reproduce and investigate a bug using logs, console inspection, and browser screenshots"
+argument-hint: [GitHub issue number]
+disable-model-invocation: true
+---
+
+<objective>
+Reproduce and investigate a bug by reading the GitHub issue, analyzing logs, visually reproducing it in a browser, and documenting findings with screenshots and code references.
+</objective>
+
+<execution_context>
+Look at github issue #$ARGUMENTS and read the issue description and comments.
+</execution_context>
+
+<process>
+
+## Phase 1: Log Investigation
+
+Run the following agents in parallel to investigate the bug:
+
+1. Task rails-console-explorer(issue_description)
+2. Task appsignal-log-investigator(issue_description)
+
+Think about the places it could go wrong looking at the codebase. Look for logging output we can look for.
+
+Run the agents again to find any logs that could help us reproduce the bug.
+
+Keep running these agents until you have a good idea of what is going on.
+
+## Phase 2: Visual Reproduction with Playwright
+
+If the bug is UI-related or involves user flows, use Playwright to visually reproduce it:
+
+### Step 1: Verify Server is Running
+
+```bash
+agent-browser open "http://localhost:3000"
+agent-browser snapshot -i
+```
+
+If server not running, inform user to start `bin/dev`.
+
+### Step 2: Navigate to Affected Area
+
+Based on the issue description, navigate to the relevant page:
+
+```bash
+agent-browser open "http://localhost:3000/[affected_route]"
+agent-browser snapshot -i
+```
+
+### Step 3: Capture Screenshots
+
+Take screenshots at each step of reproducing the bug:
+
+```bash
+agent-browser screenshot "bug-[issue]-step-1.png"
+```
+
+### Step 4: Follow User Flow
+
+Reproduce the exact steps from the issue:
+
+1. **Read the issue's reproduction steps**
+2. **Execute each step using agent-browser:**
+   - `agent-browser click @e1` for clicking elements
+   - `agent-browser fill @e1 "text"` for filling forms
+   - `agent-browser snapshot -i` to see the current state
+   - `agent-browser screenshot` to capture evidence
+
+## Phase 3: Document Findings
+
+- [ ] Document all research findings with specific file paths (e.g., `app/services/example_service.rb:42`)
+- [ ] Include screenshots showing the bug reproduction
+- [ ] List console errors if any
+- [ ] Document the exact reproduction steps
+
+## Phase 4: Report Back
+
+Add a comment to the issue with:
+
+1. **Findings** - What you discovered about the cause
+2. **Reproduction Steps** - Exact steps to reproduce (verified)
+3. **Screenshots** - Visual evidence of the bug (upload captured screenshots)
+4. **Relevant Code** - File paths and line numbers
+5. **Suggested Fix** - If you have one
+
+</process>
+
+<success_criteria>
+- [ ] GitHub issue read and understood
+- [ ] Log investigation completed (rails console + appsignal)
+- [ ] Bug visually reproduced (if UI-related) with screenshots
+- [ ] Findings documented with specific file paths and line numbers
+- [ ] Comment added to the GitHub issue with findings
+</success_criteria>

package/plugins/lavra/commands/optional/xcode-test.md

@@ -0,0 +1,287 @@
+---
+name: xcode-test
+description: Build and test iOS apps on simulator using XcodeBuildMCP
+argument-hint: [scheme name or 'current' to use default]
+disable-model-invocation: true
+---
+
+<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 /lavra-review
+
+When reviewing PRs that touch iOS code, the `/lavra-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 `/lavra-review`** - Full code review of the changes
+2. **Fix failures** - Address test failures now
+3. **Done** - Accept results
+</handoff>

package/plugins/lavra/commands/report-bug.md

@@ -0,0 +1,155 @@
+---
+name: report-bug
+description: Report a bug in the lavra plugin
+argument-hint: [optional: brief description of the bug]
+disable-model-invocation: true
+---
+
+<objective>
+Report bugs encountered while using the lavra plugin by gathering structured information and creating a GitHub issue for the maintainer.
+</objective>
+
+<process>
+
+## Step 1: Gather Bug Information
+
+Use the AskUserQuestion tool to collect the following information:
+
+**Question 1: Bug Category**
+- What type of issue are you experiencing?
+- Options: Agent not working, Command not working, Skill not working, MCP server issue, Installation problem, Other
+
+**Question 2: Specific Component**
+- Which specific component is affected?
+- Ask for the name of the agent, command, skill, or MCP server
+
+**Question 3: What Happened (Actual Behavior)**
+- Ask: "What happened when you used this component?"
+- Get a clear description of the actual behavior
+
+**Question 4: What Should Have Happened (Expected Behavior)**
+- Ask: "What did you expect to happen instead?"
+- Get a clear description of expected behavior
+
+**Question 5: Steps to Reproduce**
+- Ask: "What steps did you take before the bug occurred?"
+- Get reproduction steps
+
+**Question 6: Error Messages**
+- Ask: "Did you see any error messages? If so, please share them."
+- Capture any error output
+
+## Step 2: Collect Environment Information
+
+Automatically gather:
+```bash
+# Get plugin version
+cat ~/.claude/plugins/installed_plugins.json 2>/dev/null | grep -A5 "lavra" | head -10 || echo "Plugin info not found"
+
+# Get Claude Code version
+claude --version 2>/dev/null || echo "Claude CLI version unknown"
+
+# Get OS info
+uname -a
+```
+
+## Step 3: Format the Bug Report
+
+Create a well-structured bug report with:
+
+```markdown
+## Bug Description
+
+**Component:** [Type] - [Name]
+**Summary:** [Brief description from argument or collected info]
+
+## Environment
+
+- **Plugin Version:** [from installed_plugins.json]
+- **Claude Code Version:** [from claude --version]
+- **OS:** [from uname]
+
+## What Happened
+
+[Actual behavior description]
+
+## Expected Behavior
+
+[Expected behavior description]
+
+## Steps to Reproduce
+
+1. [Step 1]
+2. [Step 2]
+3. [Step 3]
+
+## Error Messages
+
+```
+[Any error output]
+```
+
+## Additional Context
+
+[Any other relevant information]
+
+---
+*Reported via `/report-bug` command*
+```
+
+## Step 4: Create GitHub Issue
+
+Use the GitHub CLI to create the issue:
+
+```bash
+gh issue create \
+  --repo rbm/lavra \
+  --title "[lavra] Bug: [Brief description]" \
+  --body "[Formatted bug report from Step 3]" \
+  --label "bug"
+```
+
+**Note:** If labels don't exist, create without labels:
+```bash
+gh issue create \
+  --repo rbm/lavra \
+  --title "[lavra] Bug: [Brief description]" \
+  --body "[Formatted bug report]"
+```
+
+## Step 5: Confirm Submission
+
+After the issue is created:
+1. Display the issue URL to the user
+2. Thank them for reporting the bug
+3. Let them know the maintainer will be notified
+
+</process>
+
+<success_criteria>
+- [ ] All six bug information questions answered
+- [ ] Environment information collected automatically
+- [ ] Bug report formatted with all sections
+- [ ] GitHub issue created successfully
+- [ ] Issue URL displayed to user
+</success_criteria>
+
+<guardrails>
+
+## Error Handling
+
+- If `gh` CLI is not authenticated: Prompt user to run `gh auth login` first
+- If issue creation fails: Display the formatted report so user can manually create the issue
+- If required information is missing: Re-prompt for that specific field
+
+## Privacy Notice
+
+This command does NOT collect:
+- Personal information
+- API keys or credentials
+- Private code from your projects
+- File paths beyond basic OS info
+
+Only technical information about the bug is included in the report.
+
+</guardrails>