@codyswann/lisa 1.56.1 → 1.56.2

package/plugins/lisa-expo/agents/web-search-researcher.md

@@ -1,112 +0,0 @@
----
-name: web-search-researcher
-description: Do you find yourself desiring information that you don't quite feel well-trained (confident) on? Information that is modern and potentially only discoverable on the web? Use the web-search-researcher subagent_type today to find any and all answers to your questions! It will research deeply to figure out and attempt to answer your questions! If you aren't immediately satisfied you can get your money back! (Not really - but you can re-run web-search-researcher with an altered prompt in the event you're not satisfied the first time)
-color: yellow
-model: inherit
----
-
-You are an expert web research specialist focused on finding accurate, relevant information from web sources. Your primary tools are WebSearch and WebFetch, which you use to discover and retrieve information based on user queries.
-
-## Core Responsibilities
-
-When you receive a research query, you will:
-
-1. **Analyze the Query**: Break down the user's request to identify:
-   - Key search terms and concepts
-   - Types of sources likely to have answers (documentation, blogs, forums, academic papers)
-   - Multiple search angles to ensure comprehensive coverage
-
-2. **Execute Strategic Searches**:
-   - Start with broad searches to understand the landscape
-   - Refine with specific technical terms and phrases
-   - Use multiple search variations to capture different perspectives
-   - Include site-specific searches when targeting known authoritative sources (e.g., "site:docs.stripe.com webhook signature")
-
-3. **Fetch and Analyze Content**:
-   - Use WebFetch to retrieve full content from promising search results
-   - Prioritize official documentation, reputable technical blogs, and authoritative sources
-   - Extract specific quotes and sections relevant to the query
-   - Note publication dates to ensure currency of information
-
-4. **Synthesize Findings**:
-   - Organize information by relevance and authority
-   - Include exact quotes with proper attribution
-   - Provide direct links to sources
-   - Highlight any conflicting information or version-specific details
-   - Note any gaps in available information
-
-## Search Strategies
-
-### For API/Library Documentation:
-
-- Search for official docs first: "[library name] official documentation [specific feature]"
-- Look for changelog or release notes for version-specific information
-- Find code examples in official repositories or trusted tutorials
-
-### For Best Practices:
-
-- Search for recent articles (include year in search when relevant)
-- Look for content from recognized experts or organizations
-- Cross-reference multiple sources to identify consensus
-- Search for both "best practices" and "anti-patterns" to get full picture
-
-### For Technical Solutions:
-
-- Use specific error messages or technical terms in quotes
-- Search Stack Overflow and technical forums for real-world solutions
-- Look for GitHub issues and discussions in relevant repositories
-- Find blog posts describing similar implementations
-
-### For Comparisons:
-
-- Search for "X vs Y" comparisons
-- Look for migration guides between technologies
-- Find benchmarks and performance comparisons
-- Search for decision matrices or evaluation criteria
-
-## Output Format
-
-Structure your findings as:
-
-```
-## Summary
-[Brief overview of key findings]
-
-## Detailed Findings
-
-### [Topic/Source 1]
-**Source**: [Name with link]
-**Relevance**: [Why this source is authoritative/useful]
-**Key Information**:
-- Direct quote or finding (with link to specific section if possible)
-- Another relevant point
-
-### [Topic/Source 2]
-[Continue pattern...]
-
-## Additional Resources
-- [Relevant link 1] - Brief description
-- [Relevant link 2] - Brief description
-
-## Gaps or Limitations
-[Note any information that couldn't be found or requires further investigation]
-```
-
-## Quality Guidelines
-
-- **Accuracy**: Always quote sources accurately and provide direct links
-- **Relevance**: Focus on information that directly addresses the user's query
-- **Currency**: Note publication dates and version information when relevant
-- **Authority**: Prioritize official sources, recognized experts, and peer-reviewed content
-- **Completeness**: Search from multiple angles to ensure comprehensive coverage
-- **Transparency**: Clearly indicate when information is outdated, conflicting, or uncertain
-
-## Search Efficiency
-
-- Start with 2-3 well-crafted searches before fetching content
-- Fetch only the most promising 3-5 pages initially
-- If initial results are insufficient, refine search terms and try again
-- Use search operators effectively: quotes for exact phrases, minus for exclusions, site: for specific domains
-- Consider searching in different forms: tutorials, documentation, Q&A sites, and discussion forums
-
-Remember: You are the user's expert guide to web information. Be thorough but efficient, always cite your sources, and provide actionable information that directly addresses their needs. Think deeply as you work.

package/plugins/lisa-expo/commands/git/commit-and-submit-pr.md

@@ -1,7 +0,0 @@
----
-description: "Create conventional commits for current changes and submits the current branch as a PR for code review"
-allowed-tools: ["Skill"]
-argument-hint: "[commit-message-hint]"
----
-
-Use the /lisa:git-commit-and-submit-pr skill to commit and submit a PR. $ARGUMENTS

package/plugins/lisa-expo/commands/git/commit-submit-pr-and-verify.md

@@ -1,7 +0,0 @@
----
-description: "Create conventional commits for current changes and submits the current branch as a PR for code review. Then follows the pr to make sure all checks pass and comments are resolved."
-allowed-tools: ["Skill"]
-argument-hint: "[commit-message-hint]"
----
-
-Use the /lisa:git-commit-submit-pr-and-verify skill on $ARGUMENTS

package/plugins/lisa-expo/commands/git/commit-submit-pr-deploy-and-verify.md

@@ -1,7 +0,0 @@
----
-description: "Create conventional commits for current changes and submits the current branch as a PR for code review. Then follows the pr to make sure all checks pass and comments are resolved. And then makes sure the resultant deploy is successful."
-allowed-tools: ["Skill"]
-argument-hint: "[commit-message-hint]"
----
-
-Use the /lisa:git-commit-submit-pr-deploy-and-verify skill on $ARGUMENTS

package/plugins/lisa-expo/commands/git/commit.md

@@ -1,7 +0,0 @@
----
-description: "Create conventional commits for current changes"
-allowed-tools: ["Skill"]
-argument-hint: "[commit-message-hint]"
----
-
-Use the /lisa:git-commit skill to create conventional commits for current changes. $ARGUMENTS

package/plugins/lisa-expo/commands/git/prune.md

@@ -1,6 +0,0 @@
----
-description: "Prune local branches that have been deleted on remote"
-allowed-tools: ["Skill"]
----
-
-Use the /lisa:git-prune skill to prune local branches that have been deleted on remote.

package/plugins/lisa-expo/commands/git/submit-pr.md

@@ -1,7 +0,0 @@
----
-description: "Push changes and create or update a pull request"
-allowed-tools: ["Skill"]
-argument-hint: "[pr-title-or-description-hint]"
----
-
-Use the /lisa:git-submit-pr skill to push changes and create or update a pull request. $ARGUMENTS

package/plugins/lisa-expo/commands/jira/fix.md

@@ -1,7 +0,0 @@
----
-description: "Fix a bug described in a JIRA ticket"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET-ID-OR-URL>"
----
-
-Use the /lisa:jira-fix skill to fix the bug described in the JIRA ticket. $ARGUMENTS

package/plugins/lisa-expo/commands/jira/implement.md

@@ -1,7 +0,0 @@
----
-description: "Implement requirements from a JIRA ticket"
-allowed-tools: ["Skill"]
-argument-hint: "<TICKET-ID-OR-URL>"
----
-
-Use the /lisa:jira-implement skill to implement the requirements in the JIRA ticket. $ARGUMENTS

package/plugins/lisa-expo/commands/jira/sync.md

@@ -1,7 +0,0 @@
----
-description: "Sync plan progress to a linked JIRA ticket"
-allowed-tools: ["Skill"]
-argument-hint: "<ticket-id>"
----
-
-Use the /lisa:jira-sync skill to sync plan progress to the linked JIRA ticket. $ARGUMENTS

package/plugins/lisa-expo/commands/plan/create.md

@@ -1,6 +0,0 @@
----
-description: "Creates an implementation plan from a ticket URL, file path, or text description"
-argument-hint: "<ticket-url | @file-path | description>"
----
-
-Use the /lisa:plan-execute skill on $ARGUMENTS

package/plugins/lisa-expo/commands/plan/execute.md

@@ -1,7 +0,0 @@
----
-description: "Deploys an agent team to research, implement, review and deploy a plan"
-argument-hint: "<ticket-url | @file-path | description>"
----
-
-
-Use the /lisa:plan-execute skill on $ARGUMENTS

package/plugins/lisa-expo/commands/plan/local-code-review.md

@@ -1,6 +0,0 @@
----
-description: "Review local branch changes compared to main"
-allowed-tools: ["Skill"]
----
-
-Use the /lisa:plan-local-code-review skill to review local changes.

package/plugins/lisa-expo/commands/pull-request/review.md

@@ -1,7 +0,0 @@
----
-description: "Checks for code review comments on a PR and implements them if required."
-allowed-tools: ["Skill"]
-argument-hint: "<github-pr-link>"
----
-
-Use the /lisa:pull-request-review skill to check for code review comments and implement them. $ARGUMENTS

package/plugins/lisa-expo/commands/review/implementation.md

@@ -1,7 +0,0 @@
----
-description: "Compare project's Lisa-managed files against Lisa source templates and offer to upstream changes"
-allowed-tools: ["Skill"]
-argument-hint: "[lisa-dir]"
----
-
-Use the /lisa:lisa-review-implementation skill to compare project files against Lisa templates. $ARGUMENTS

package/plugins/lisa-expo/commands/security/zap-scan.md

@@ -1,6 +0,0 @@
----
-description: "Run an OWASP ZAP baseline security scan locally using Docker"
-allowed-tools: ["Skill"]
----
-
-Use the /lisa:security-zap-scan skill to run an OWASP ZAP baseline security scan.

package/plugins/lisa-expo/commands/sonarqube/check.md

@@ -1,6 +0,0 @@
----
-description: "Uses SonarQube / SonarCloud to get the reason that last pull request failed to pass checks"
-allowed-tools: ["Skill"]
----
-
-Use the /lisa:sonarqube-check skill to check why the last PR failed SonarQube quality gates.

package/plugins/lisa-expo/commands/sonarqube/fix.md

@@ -1,6 +0,0 @@
----
-description: "Run SonarQube check, fix failures, and commit"
-allowed-tools: ["Skill"]
----
-
-Use the /lisa:sonarqube-fix skill to check, fix, and commit SonarQube quality gate failures.

package/plugins/lisa-expo/commands/tasks/load.md

@@ -1,7 +0,0 @@
----
-description: "Load tasks from a project directory into the current session"
-allowed-tools: ["Skill"]
-argument-hint: "<project-name>"
----
-
-Use the /lisa:tasks-load skill to load tasks from a project directory. $ARGUMENTS

package/plugins/lisa-expo/commands/tasks/sync.md

@@ -1,7 +0,0 @@
----
-description: "Sync current session tasks to a project directory"
-allowed-tools: ["Skill"]
-argument-hint: "<project-name>"
----
-
-Use the /lisa:tasks-sync skill to sync current session tasks to a project directory. $ARGUMENTS

package/plugins/lisa-expo/hooks/debug-hook.sh

@@ -1,47 +0,0 @@
-#!/bin/bash
-##
-# Debug hook that logs all hook events when CLAUDE_DEBUG=1
-# This script is a no-op when CLAUDE_DEBUG is not set or set to 0
-##
-
-# Exit immediately if debug mode is not enabled
-if [[ "${CLAUDE_DEBUG:-0}" != "1" ]]; then
-  exit 0
-fi
-
-# Read JSON input from stdin
-INPUT=$(cat)
-
-# Parse hook event info using jq
-HOOK_EVENT=$(echo "$INPUT" | jq -r '.hook_event_name // "unknown"')
-TOOL_NAME=$(echo "$INPUT" | jq -r '.tool_name // "N/A"')
-SESSION_ID=$(echo "$INPUT" | jq -r '.session_id // "unknown"')
-CWD=$(echo "$INPUT" | jq -r '.cwd // "unknown"')
-PERMISSION_MODE=$(echo "$INPUT" | jq -r '.permission_mode // "unknown"')
-
-# Create debug log directory if it doesn't exist
-DEBUG_LOG_DIR="${CLAUDE_PROJECT_DIR:-.}/.claude/debug"
-mkdir -p "$DEBUG_LOG_DIR"
-
-# Log file with session ID
-LOG_FILE="$DEBUG_LOG_DIR/hooks-${SESSION_ID}.log"
-
-# Timestamp
-TIMESTAMP=$(date '+%Y-%m-%d %H:%M:%S')
-
-# Log the event
-{
-  echo "[$TIMESTAMP] Hook: $HOOK_EVENT"
-  echo "  Tool: $TOOL_NAME"
-  echo "  Session: $SESSION_ID"
-  echo "  CWD: $CWD"
-  echo "  Permission Mode: $PERMISSION_MODE"
-  echo "  Full Input:"
-  echo "$INPUT" | jq '.' | sed 's/^/    /'
-  echo "---"
-} >> "$LOG_FILE"
-
-# Also output to stderr in verbose mode (won't affect Claude)
-echo "[DEBUG] Hook fired: $HOOK_EVENT (tool: $TOOL_NAME)" >&2
-
-exit 0

package/plugins/lisa-expo/hooks/enforce-plan-rules.sh

@@ -1,15 +0,0 @@
-#!/bin/bash
-# Reinjects plan-mode rules on every prompt when Claude is in plan mode.
-# Wired as a UserPromptSubmit hook in .claude/settings.json.
-
-INPUT=$(cat)
-PERMISSION_MODE=$(echo "$INPUT" | jq -r '.permission_mode // "default"')
-
-if [ "$PERMISSION_MODE" = "plan" ]; then
-  PLAN_RULES="$CLAUDE_PROJECT_DIR/.claude/rules/plan.md"
-  if [ -f "$PLAN_RULES" ]; then
-    echo "PLAN MODE RULES (reinforced):"
-    cat "$PLAN_RULES"
-  fi
-fi
-exit 0

package/plugins/lisa-expo/hooks/format-on-edit.sh

@@ -1,76 +0,0 @@
-#!/bin/bash
-# This file is managed by Lisa.
-# Do not edit directly — changes will be overwritten on the next `lisa` run.
-
-# Hook script to format files with Prettier after Claude edits them
-# This script receives JSON input via stdin with tool information
-# Reference: https://docs.claude.com/en/docs/claude-code/hooks
-
-# Read the JSON input from stdin
-JSON_INPUT=$(cat)
-
-# Extract the file path from the tool_input
-# The Edit tool input contains a "file_path" field in the tool_input object
-FILE_PATH=$(echo "$JSON_INPUT" | grep -o '"tool_input":{[^}]*"file_path":"[^"]*"' | grep -o '"file_path":"[^"]*"' | cut -d'"' -f4)
-
-# Check if we successfully extracted a file path
-if [ -z "$FILE_PATH" ]; then
-    echo "⚠ Skipping Prettier: Could not extract file path from Edit tool input" >&2
-    exit 0  # Exit gracefully to not interrupt Claude's workflow
-fi
-
-# Check if the file exists
-if [ ! -f "$FILE_PATH" ]; then
-    echo "⚠ Skipping Prettier: File does not exist: $FILE_PATH" >&2
-    exit 0  # Exit gracefully
-fi
-
-# Get the file extension
-FILE_EXT="${FILE_PATH##*.}"
-
-# Check if this is a TypeScript or JavaScript file that should be formatted
-# Based on package.json format command: "prettier --write \"src/**/*.ts\" \"test/**/*.ts\""
-case "$FILE_EXT" in
-    ts|tsx|js|jsx|json)
-        # File type is supported for formatting
-        ;;
-    *)
-        echo "ℹ Skipping Prettier: File type .$FILE_EXT is not configured for auto-formatting"
-        exit 0
-        ;;
-esac
-
-# Change to the project directory to ensure package manager commands work
-cd "$CLAUDE_PROJECT_DIR" || exit 0
-
-# Detect package manager based on lock file presence
-detect_package_manager() {
-    if [ -f "bun.lockb" ] || [ -f "bun.lock" ]; then
-        echo "bun"
-    elif [ -f "pnpm-lock.yaml" ]; then
-        echo "pnpm"
-    elif [ -f "yarn.lock" ]; then
-        echo "yarn"
-    elif [ -f "package-lock.json" ]; then
-        echo "npm"
-    else
-        echo "npm"  # Default fallback
-    fi
-}
-
-PKG_MANAGER=$(detect_package_manager)
-
-# Run Prettier on the specific file
-echo "🎨 Running Prettier on: $FILE_PATH"
-$PKG_MANAGER prettier --write "$FILE_PATH" 2>&1 | grep -v "run v" | grep -v "Done in"
-
-# Check the exit status
-if [ ${PIPESTATUS[0]} -eq 0 ]; then
-    echo "✓ Successfully formatted: $(basename "$FILE_PATH")"
-else
-    echo "⚠ Prettier formatting failed for: $FILE_PATH" >&2
-    echo "  You may need to run '$PKG_MANAGER run format' manually to fix formatting issues." >&2
-fi
-
-# Always exit successfully to not interrupt Claude's workflow
-exit 0

package/plugins/lisa-expo/hooks/install-pkgs.sh

@@ -1,64 +0,0 @@
-#!/bin/bash
-# This file is managed by Lisa.
-# Do not edit directly — changes will be overwritten on the next `lisa` run.
-
-# Only run package installation when node_modules are missing.
-# This covers remote environments, new worktrees, fresh clones, and CI.
-if [ -d "node_modules" ]; then
-  exit 0
-fi
-
-# Detect package manager based on lock file presence
-if [ -f "bun.lockb" ] || [ -f "bun.lock" ]; then
-  bun install
-elif [ -f "pnpm-lock.yaml" ]; then
-  pnpm install
-elif [ -f "yarn.lock" ]; then
-  yarn install
-elif [ -f "package-lock.json" ]; then
-  npm install
-else
-  npm install
-fi
-
-# Install Gitleaks for secret detection (pre-commit hook)
-echo "Installing Gitleaks for secret detection..."
-GITLEAKS_VERSION="8.18.4"
-curl -sSfL "https://github.com/gitleaks/gitleaks/releases/download/v${GITLEAKS_VERSION}/gitleaks_${GITLEAKS_VERSION}_linux_x64.tar.gz" | tar -xz -C /usr/local/bin gitleaks
-echo "Gitleaks installed: $(gitleaks version)"
-
-# Install jira-cli for JIRA integration
-# The tarball nests the binary at jira_VERSION_linux_x86_64/bin/jira,
-# so we extract to a temp dir and copy the binary out.
-echo "Installing jira-cli for JIRA integration..."
-JIRA_CLI_VERSION="1.7.0"
-JIRA_TMPDIR=$(mktemp -d)
-curl -sSfL "https://github.com/ankitpokhrel/jira-cli/releases/download/v${JIRA_CLI_VERSION}/jira_${JIRA_CLI_VERSION}_linux_x86_64.tar.gz" \
-  | tar -xz -C "${JIRA_TMPDIR}"
-cp "${JIRA_TMPDIR}/jira_${JIRA_CLI_VERSION}_linux_x86_64/bin/jira" /usr/local/bin/jira
-chmod +x /usr/local/bin/jira
-rm -rf "${JIRA_TMPDIR}"
-echo "jira-cli installed: $(jira version)"
-
-# Install Chromium for Lighthouse CI (pre-push hook)
-# Playwright's bundled Chromium works with @lhci/cli
-echo "Installing Chromium for Lighthouse CI..."
-npx playwright install chromium
-
-# Find and export CHROME_PATH for Lighthouse CI
-# Use sort to ensure deterministic selection of the latest version
-CHROME_PATH=$(find ~/.cache/ms-playwright -name "chrome" -type f 2>/dev/null | grep "chrome-linux" | sort | tail -n 1)
-if [ -n "$CHROME_PATH" ]; then
-  # Append to ~/.bashrc for shell sessions (idempotent)
-  if ! grep -q "export CHROME_PATH=" ~/.bashrc 2>/dev/null; then
-    echo "export CHROME_PATH=\"$CHROME_PATH\"" >> ~/.bashrc
-  else
-    # Update existing CHROME_PATH in bashrc
-    sed -i "s|^export CHROME_PATH=.*|export CHROME_PATH=\"$CHROME_PATH\"|" ~/.bashrc
-  fi
-
-  export CHROME_PATH="$CHROME_PATH"
-  echo "Chromium installed at: $CHROME_PATH"
-fi
-
-exit 0

package/plugins/lisa-expo/hooks/lint-on-edit.sh

@@ -1,81 +0,0 @@
-#!/bin/bash
-# This file is managed by Lisa.
-# Do not edit directly — changes will be overwritten on the next `lisa` run.
-# =============================================================================
-# ESLint Lint-on-Edit Hook (PostToolUse - Write|Edit)
-# =============================================================================
-# Runs ESLint --fix with --quiet --cache on each edited TypeScript file.
-# Part of the inline self-correction pipeline: prettier → ast-grep → eslint.
-#
-# Behavior:
-#   - Exit 0: lint passes or auto-fix resolved all errors
-#   - Exit 2: unfixable errors remain — blocks Claude so it fixes them immediately
-#
-# @see .claude/rules/verfication.md "Self-Correction Loop" section
-# =============================================================================
-
-# Extract file path from JSON input
-FILE_PATH=$(cat | grep -o '"file_path":"[^"]*"' | head -1 | cut -d'"' -f4)
-
-if [ -z "$FILE_PATH" ] || [ ! -f "$FILE_PATH" ]; then
-    exit 0
-fi
-
-# Check if file type is supported (TypeScript only)
-case "${FILE_PATH##*.}" in
-    ts|tsx) ;;
-    *) exit 0 ;;
-esac
-
-# Validate project directory
-if [ -z "${CLAUDE_PROJECT_DIR:-}" ]; then
-    exit 0
-fi
-
-# Check if file is in a source directory
-RELATIVE_PATH="${FILE_PATH#$CLAUDE_PROJECT_DIR/}"
-case "$RELATIVE_PATH" in
-    src/*|apps/*|libs/*|test/*|tests/*|features/*|components/*|hooks/*|screens/*|app/*|constants/*|utils/*|providers/*|stores/*) ;;
-    *) exit 0 ;;
-esac
-
-cd "$CLAUDE_PROJECT_DIR" || exit 0
-
-# Detect package manager
-if [ -f "bun.lockb" ] || [ -f "bun.lock" ]; then
-    PKG_MANAGER="bun"
-elif [ -f "pnpm-lock.yaml" ]; then
-    PKG_MANAGER="pnpm"
-elif [ -f "yarn.lock" ]; then
-    PKG_MANAGER="yarn"
-else
-    PKG_MANAGER="npm"
-fi
-
-# Run ESLint with --fix --quiet --cache on the specific file
-# --quiet: suppress warnings, only show errors
-# --cache: use ESLint cache for performance
-echo "Running ESLint --fix on: $FILE_PATH"
-
-# First pass: attempt auto-fix
-OUTPUT=$($PKG_MANAGER eslint --fix --quiet --cache "$FILE_PATH" 2>&1)
-FIX_EXIT=$?
-
-if [ $FIX_EXIT -eq 0 ]; then
-    echo "ESLint: No errors in $(basename "$FILE_PATH")"
-    exit 0
-fi
-
-# Auto-fix resolved some issues but errors remain — re-run to get remaining errors
-OUTPUT=$($PKG_MANAGER eslint --quiet --cache "$FILE_PATH" 2>&1)
-LINT_EXIT=$?
-
-if [ $LINT_EXIT -eq 0 ]; then
-    echo "ESLint: Auto-fixed all errors in $(basename "$FILE_PATH")"
-    exit 0
-fi
-
-# Unfixable errors remain — block with feedback
-echo "ESLint found unfixable errors in: $FILE_PATH" >&2
-echo "$OUTPUT" >&2
-exit 2