@codyswann/lisa 2.119.1 → 2.121.1

package/plugins/lisa-cursor/commands/improve/max-lines-per-function.md

@@ -0,0 +1,7 @@
+---
+description: "Reduce max lines per function threshold and fix violations"
+allowed-tools: ["Skill"]
+argument-hint: "<max-lines-per-function-value>"
+---
+
+Use the /lisa:improve-max-lines-per-function skill to reduce max function lines. $ARGUMENTS

package/plugins/lisa-cursor/commands/improve/max-lines.md

@@ -0,0 +1,7 @@
+---
+description: "Reduce max file lines threshold and fix violations"
+allowed-tools: ["Skill"]
+argument-hint: "<max-lines-value>"
+---
+
+Use the /lisa:improve-max-lines skill to reduce max lines. $ARGUMENTS

package/plugins/lisa-cursor/commands/improve/test-coverage.md

@@ -0,0 +1,7 @@
+---
+description: "Increase test coverage to a specified threshold percentage"
+allowed-tools: ["Skill"]
+argument-hint: "<threshold-percentage>"
+---
+
+Use the /lisa:improve-test-coverage skill to increase test coverage. $ARGUMENTS

package/plugins/lisa-cursor/commands/improve/tests.md

@@ -0,0 +1,7 @@
+---
+description: "Improve test quality by analyzing and strengthening weak, brittle, or poorly-written tests"
+allowed-tools: ["Skill"]
+argument-hint: "<target-description>"
+---
+
+Use the /lisa:improve-tests skill to improve test quality. $ARGUMENTS

package/plugins/lisa-cursor/commands/intake-explain.md

@@ -0,0 +1,31 @@
+---
+description: "Inspect one PRD or build item, explain how Lisa classifies it right now, and report the exact intake or repair gate affecting it. Read-only by default."
+argument-hint: "<item-ref>"
+---
+
+Use the /lisa:intake-explain skill to inspect a single repo-scoped PRD or build item, explain its current lifecycle role, and report whether Lisa would intake it, repair it, hold it, skip it, or leave it product-owned. $ARGUMENTS
+
+Common operator usage:
+
+- `/lisa:intake-explain https://github.com/acme/repo/issues/123`
+- `/lisa:intake-explain PRD-456`
+- `/lisa:intake-explain https://linear.app/acme/issue/ENG-123/example`
+
+The diagnosis uses stable verdicts:
+
+- `ELIGIBLE_FOR_INTAKE`: run `/lisa:intake <queue>` when normal pickup is the next move.
+- `ELIGIBLE_FOR_REPAIR`: run `/lisa:repair-intake <queue>` when Lisa-owned stuck work is actionable.
+- `WAITING_ON_STALENESS`: wait and re-check after the configured freshness window.
+- `HELD_BY_BLOCKERS`: clear the listed dependency or blocker before rerunning intake.
+- `NON_LEAF_CONTAINER`: decompose the item or move build-ready status to leaf work.
+- `PRODUCT_OWNED_STATE`: finish product clarification, promotion, or verification first.
+- `MISCONFIGURED`: fix lifecycle labels, repo scope, or queue configuration before relying on automation.
+
+Use it for these operator workflows:
+
+- Intake triage: confirm whether one item would be picked up by `/lisa:intake` right now.
+- Repair triage: decide whether a blocked or in-progress item is stale enough for `/lisa:repair-intake`.
+- Product follow-up: distinguish product-owned draft/shipped/verified states from Lisa-owned work.
+- Queue cleanup: identify leaf-only, repo-scope, dependency, or lifecycle-adoption fixes without mutating the item.
+
+This surface is read-only in v1. It never claims, relabels, comments on, repairs, or decomposes the item; it only reports the item facts, verdict, decisive gate, and smallest useful next action before an operator chooses `/lisa:intake`, `/lisa:repair-intake`, `/lisa:queue-status`, or a tracker-native fix.

package/plugins/lisa-cursor/commands/intake.md

@@ -0,0 +1,6 @@
+---
+description: "Vendor-agnostic batch scanner for Ready queues. Notion PRD database URL → finds Status=Ready PRDs and runs lisa:plan per item. Confluence space or parent-page URL → finds prd-ready PRDs and runs lisa:plan per item. Linear workspace or team URL → finds prd-ready Linear projects and runs lisa:plan per item. GitHub repo URL or org/repo token → finds prd-ready GitHub issues and runs lisa:plan per item (PRD-source mode), or finds status:ready issues and runs lisa:implement per item when tracker=github (build-queue mode). JIRA project key or JQL → finds Ready tickets and runs lisa:implement per item. Designed as the cron target for /schedule."
+argument-hint: "<Notion-PRD-database-URL | Confluence-space-URL | Confluence-parent-page-URL | Linear-workspace-URL | Linear-team-URL | GitHub-repo-URL | org/repo | JIRA-project-key | JQL-filter>"
+---
+
+Use the /lisa:intake skill to scan the queue for Ready items and dispatch one eligible Ready item per invocation through the appropriate single-item lifecycle skill — and, on the PRD side, close the loop by dispatching /lisa:verify-prd for one shipped PRD per cycle (shipped → verified on pass, or re-opened to ticketed with build-ready fix tickets that auto-build and re-verify on fail — never blocked). $ARGUMENTS

package/plugins/lisa-cursor/commands/monitor.md

@@ -0,0 +1,6 @@
+---
+description: "Monitor application health across environments. Health endpoints, recent logs, error-rate spikes, performance, optional browser UAT. Routes to the stack-specific ops-specialist."
+argument-hint: "[environment]"
+---
+
+Use the /lisa:monitor skill to check application health, logs, errors, and performance for the named environment. $ARGUMENTS

package/plugins/lisa-cursor/commands/plan.md

@@ -0,0 +1,6 @@
+---
+description: "Plan work from a single PRD or specification. Decomposes into ordered work items in the configured tracker (JIRA, GitHub Issues, or Linear per .lisa.config.json). Source can be a Notion / Confluence / Linear / GitHub Issue URL, a JIRA epic key, a markdown file, or a free-form description. For batch scanning of all Ready PRDs in a queue, use /lisa:intake instead."
+argument-hint: "<single-PRD-url | GitHub-issue-url | @file | ticket-id-or-url | description>"
+---
+
+Use the /lisa:plan skill to decompose the PRD/spec into ordered work items in the configured tracker. $ARGUMENTS

package/plugins/lisa-cursor/commands/plugin-sync-explain.md

@@ -0,0 +1,8 @@
+---
+description: "Explain plugin source/generated drift and marketplace registration gaps without modifying the working tree."
+argument-hint: "[path]"
+---
+
+Use the /lisa:plugin-sync-explain skill to inspect plugin source/generated synchronization for the current Lisa repo. $ARGUMENTS
+
+This command is read-only. It reports source-not-built edits, generated-only edits, marketplace registration drift, and the next source-first remediation step before an operator runs `bun run build:plugins` or `bun run check:plugins`.

package/plugins/lisa-cursor/commands/product-walkthrough.md

@@ -0,0 +1,7 @@
+---
+description: "Walk through the live product via a real browser (Playwright MCP) to ground PRD evaluation or ticket creation in what exists today. Captures current behavior, design-vs-product divergence, reuse candidates, and behavioral surprises."
+allowed-tools: ["Skill"]
+argument-hint: "<route or feature area to walk>"
+---
+
+Use the /lisa:product-walkthrough skill to walk through the live product, capture current state, and produce findings that ground PRD/ticket reasoning. $ARGUMENTS

package/plugins/lisa-cursor/commands/project-ideation.md

@@ -0,0 +1,6 @@
+---
+description: "Generate persona-grounded, verifiable product ideas for the host project, then create PRDs for the selected build-ready ideas via lisa:research. First derives the personas the project actually serves (from its docs, code, data model, and releases — never invented), ideates per persona, and gates each idea on an obtainable data/source path and an empirical verification plan. Creates one PRD by default (top-ranked idea); max_prds widens the batch. prd_ready=true creates them prd-ready for auto-pickup by lisa:intake; default is draft for human review."
+argument-hint: "[target path | external product] [prd_ready=true|false] [max_prds=<n>|all]"
+---
+
+Use the /lisa:project-ideation skill to derive evidence-grounded personas, ideate per persona, gate the ideas, and create PRDs for the selected build-ready ideas via lisa:research — in draft state by default, or prd-ready when prd_ready=true; one PRD by default, more with max_prds. $ARGUMENTS

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

@@ -0,0 +1,7 @@
+---
+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-cursor/commands/queue-status.md

@@ -0,0 +1,34 @@
+---
+description: "Inspect the current project's PRD and build queues, summarize lifecycle counts, and surface actionable queue-health signals without mutating work."
+---
+
+Use the /lisa:queue-status skill to inspect the current project's configured PRD source and build tracker, report queue-health verdicts, and highlight actionable backlog or stuck-state signals. $ARGUMENTS
+
+Common operator usage:
+
+- `/lisa:queue-status`
+- `/lisa:queue-status queue=prd`
+- `/lisa:queue-status queue=build`
+
+Use this when you need to answer:
+
+- Is the queue actually idle, or is Lisa misconfigured?
+- Which queue item is the most actionable next?
+- Should the next command be `/lisa:intake`, `/lisa:repair-intake`, `/lisa:automation-status`, or `/lisa:verify-prd`?
+
+This surface is read-only in v1. Use it to understand whether the repo's PRD and build queues are idle, healthy, attention-needed, or misconfigured before deciding whether to run `/lisa:intake`, `/lisa:repair-intake`, `/lisa:automation-status`, `/lisa:verify-prd`, or deeper tracker-native investigation.
+
+Quick interpretation guide:
+
+- `IDLE`: the queue resolved correctly and nothing actionable is waiting. No immediate Lisa action is required.
+- `HEALTHY`: the queue resolved correctly and normal work is present. Follow the highlighted next step, usually `/lisa:intake`.
+- `ATTENTION_NEEDED`: blocked, stalled, or aging work needs operator follow-up. Use the highlighted item and remediation hint to choose the next command, usually `/lisa:repair-intake`.
+- `MISCONFIGURED`: queue resolution or lifecycle adoption is broken. Fix config, labels/statuses, or scheduler drift before trusting queue state.
+
+Highlighted-item semantics:
+
+- A highlighted item is the single oldest or most actionable queue item for that section, not a full dump of all matching work.
+- `ready` highlights usually point to `/lisa:intake`.
+- `blocked`, stalled, or long-claimed highlights usually point to `/lisa:repair-intake`.
+- Shipped PRD highlights usually point to `/lisa:verify-prd`.
+- If queue behavior looks wrong for both PRD and build lanes, inspect `/lisa:automation-status` before assuming the queue itself is the problem.

package/plugins/lisa-cursor/commands/repair-intake.md

@@ -0,0 +1,6 @@
+---
+description: "Repair counterpart to /lisa:intake. Vendor-agnostic batch scanner that finds stuck or half-closed work — items left in `blocked`, stalled in an in-progress role (build `claimed`, PRD `in_review`), terminal-labeled items still natively open, and rollups whose children are all terminal — across the same queues /lisa:intake serves (Notion / Confluence / Linear / GitHub PRDs; JIRA / GitHub / Linear build issues). Repairs every materially actionable candidate inside the `max_candidates` cap: resumes stalled in-progress work in place — but for a stalled build it first diagnoses the PR/deploy state and, if the PR cannot merge (conflict, rebase, failing checks, unaddressed CodeRabbit/changes-requested) or a deploy failed, files a build-ready fix ticket and moves the item to `blocked` (blocked by it) instead of re-dispatching — re-validates blocked PRDs, re-dispatches blocked build items whose blockers have cleared, performs terminal native closure, and closes out completed rollups. Cron-safe and bounded; default GitHub intake_mode is both and default max_candidates is 100."
+argument-hint: "<Notion-PRD-database-URL | Confluence-space-URL | Confluence-parent-page-URL | Linear-workspace-URL | Linear-team-URL | GitHub-repo-URL | org/repo | JIRA-project-key | JQL-filter> [intake_mode=prd|build|both] [stale_after=2h] [max_candidates=100] [force=true]"
+---
+
+Use the /lisa:repair-intake skill to scan the queue for stuck or half-closed items and repair every materially actionable candidate inside `max_candidates` (default 100). For GitHub queues, default `intake_mode` to `both` when the caller omits it. $ARGUMENTS

package/plugins/lisa-cursor/commands/research.md

@@ -0,0 +1,6 @@
+---
+description: "Research a problem space and create a PRD in the configured PRD source. Investigates the codebase, defines user flows, assesses technical feasibility, synthesizes the spec, then creates it in the source (Notion / Confluence / GitHub / Linear) via lisa:prd-source-write — no loose document. prd_ready=true creates it prd-ready for auto-pickup by lisa:intake; default is draft for the Plan flow / human review."
+argument-hint: "<problem-statement-or-feature-idea> [prd_ready=true|false]"
+---
+
+Use the /lisa:research skill to research the problem and create a PRD in the configured source — in draft state by default, or prd-ready when prd_ready=true. $ARGUMENTS

package/plugins/lisa-cursor/commands/review/local.md

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

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

@@ -0,0 +1,6 @@
+---
+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-cursor/commands/setup/atlassian.md

@@ -0,0 +1,7 @@
+---
+description: "Set up Atlassian (cloudId + acli profile) for this project. Writes the `atlassian` section of `.lisa.config.json` and enables the Atlassian MCP and/or installs acli as needed. Prerequisite for /lisa:setup:jira and /lisa:setup:confluence."
+allowed-tools: ["Skill"]
+argument-hint: "[--site=<site>] [--email=<email>]"
+---
+
+Use the /lisa:setup-atlassian skill to configure Atlassian access for this project. $ARGUMENTS

package/plugins/lisa-cursor/commands/setup/confluence.md

@@ -0,0 +1,7 @@
+---
+description: "Set up Confluence as the PRD source for this project. Writes the `confluence` section of `.lisa.config.json` (spaceKey and/or parentPageId) and offers to set top-level `source: \"confluence\"`. Depends on /lisa:setup:atlassian."
+allowed-tools: ["Skill"]
+argument-hint: "[--space=<KEY>] [--parent=<pageId>]"
+---
+
+Use the /lisa:setup-confluence skill to configure Confluence as the PRD source. $ARGUMENTS

package/plugins/lisa-cursor/commands/setup/github.md

@@ -0,0 +1,7 @@
+---
+description: "Set up GitHub Issues as the tracker and/or PRD source for this project. Verifies the gh CLI, resolves org/repo, scaffolds the `status:*` (build) and/or `prd-*` (PRD) label namespaces, writes the `github` section of `.lisa.config.json`, and can document optional GitHub ProjectV2 coordination before offering top-level `tracker: \"github\"` / `source: \"github\"`. No /lisa:setup:atlassian prerequisite."
+allowed-tools: ["Skill"]
+argument-hint: "[--repo=<org/repo>]"
+---
+
+Use the /lisa:setup-github skill to configure GitHub as the tracker and/or PRD source. $ARGUMENTS

package/plugins/lisa-cursor/commands/setup/jira.md

@@ -0,0 +1,7 @@
+---
+description: "Set up JIRA as the tracker for this project. Writes `jira.project` and offers to set top-level `tracker: \"jira\"` in `.lisa.config.json`. Depends on /lisa:setup:atlassian (needs cloudId)."
+allowed-tools: ["Skill"]
+argument-hint: "[--project=<KEY>]"
+---
+
+Use the /lisa:setup-jira skill to configure JIRA as the project tracker. $ARGUMENTS

package/plugins/lisa-cursor/commands/setup/linear.md

@@ -0,0 +1,7 @@
+---
+description: "Set up Linear as the tracker and/or PRD source for this project. Verifies Linear access (MCP OAuth or a personal API key in keychain), resolves the workspace slug and team key, scaffolds the `status:*` issue-label (build) and/or `prd-*` project-label (PRD) namespaces, writes the `linear` section of `.lisa.config.json`, and offers to set top-level `tracker: \"linear\"` / `source: \"linear\"`. No /lisa:setup:atlassian prerequisite."
+allowed-tools: ["Skill"]
+argument-hint: "[--workspace=<slug>] [--team=<KEY>]"
+---
+
+Use the /lisa:setup-linear skill to configure Linear as the tracker and/or PRD source. $ARGUMENTS

package/plugins/lisa-cursor/commands/setup/notion.md

@@ -0,0 +1,7 @@
+---
+description: "Set up Notion as the PRD source for this project. Walks the user through creating a workspace-scoped internal-integration token, sharing the PRD database with it, and stores the token in OS keychain. Writes `notion.workspaceId`, `notion.prdDatabaseId`, and `notion.values` into `.lisa.config.json`. Offers to set top-level `source: \"notion\"`."
+allowed-tools: ["Skill"]
+argument-hint: "[--database=<uuid>] [--workspace=<slug>]"
+---
+
+Use the /lisa:setup-notion skill to configure Notion as the PRD source. $ARGUMENTS

package/plugins/lisa-cursor/commands/setup-automations.md

@@ -0,0 +1,6 @@
+---
+description: "Set up the recurring Lisa automations on the local workstation using the runtime's native scheduler (Codex automations / Claude /schedule): intake-repair (60 min), intake PRD (60 min), intake tickets (10 min), exploratory-bugs (daily), exploratory-prds (daily). A declarative spec — it states what to schedule and how often; the runtime's native automation mechanism does the creating. auto-start-prds / auto-start-tickets control whether ideated PRDs / filed bug tickets are created auto-pickup-ready (default: left for human review)."
+argument-hint: "[auto-start-prds=true|false] [auto-start-tickets=true|false]"
+---
+
+Use the /lisa:setup-automations skill to create the five recurring Lisa automations via this runtime's native scheduler (Codex automations / Claude /schedule), passing the auto-start-prds / auto-start-tickets flags through to the exploratory automations. $ARGUMENTS

package/plugins/lisa-cursor/commands/tear-down-automations.md

@@ -0,0 +1,6 @@
+---
+description: "Remove the recurring Lisa automations /setup-automations created for this project (the lisa-auto-<project>-* set) using the runtime's native scheduler (Codex automations / Claude /schedule). A declarative spec — it states which automations to remove; the runtime's native mechanism does the removing. Removes only this project's Lisa automations, never others."
+argument-hint: ""
+---
+
+Use the /lisa:tear-down-automations skill to remove this project's lisa-auto-<project>-* automations via this runtime's native scheduler (Codex automations / Claude /schedule), leaving other projects' and non-Lisa automations untouched. $ARGUMENTS

package/plugins/lisa-cursor/commands/verify-prd.md

@@ -0,0 +1,6 @@
+---
+description: "Initiative-level PRD acceptance gate. Reads a shipped PRD and its generated child work, confirms all generated top-level work is terminal, then runs spec-conformance against the PRD plus empirical verification of the shipped surface. On a CONFORMS verdict with all checks passing it transitions the PRD shipped → verified with evidence; on a conformance miss (PARTIAL/DIVERGES) or any failing empirical check it re-opens the PRD shipped → ticketed (never blocked), creates build-ready fix tickets for the gaps, and posts a failure report — the fix tickets auto-build, the PRD re-ships, and it re-verifies (a self-healing loop). Idempotent across re-runs."
+argument-hint: "<prd>"
+---
+
+Use the /lisa:verify-prd skill to read the PRD, confirm its generated top-level work is terminal, run spec-conformance against the PRD and empirical verification of the shipped surface, then transition the PRD shipped → verified with evidence on a pass, or — on a fail — re-open it shipped → ticketed (never blocked) and create build-ready fix tickets that auto-build and trigger a re-verify. $ARGUMENTS

package/plugins/lisa-cursor/commands/verify.md

@@ -0,0 +1,6 @@
+---
+description: "Ship and verify code. Commits, opens PR, handles review loop, merges, monitors deploy, and runs remote verification in target environment. Folds in /ship."
+argument-hint: "[commit-message-hint]"
+---
+
+Use the /lisa:verify skill to commit, push, PR, merge, deploy, and verify in the target environment. $ARGUMENTS

package/plugins/lisa-cursor/commands/wiki/install.md

@@ -0,0 +1,7 @@
+---
+description: "Enable the LLM Wiki kernel (lisa-wiki plugin) in this project so its setup skill becomes discoverable. Edits .claude/settings.json to enable lisa-wiki@lisa and confirm the CodySwannGT/lisa marketplace, then verifies the Codex overlay (.codex/skills/lisa) already carries the wiki kernel. Does NOT scaffold the wiki itself — after install, reload the runtime and run /setup:wiki (Claude) or $lisa-wiki-setup (Codex)."
+allowed-tools: ["Skill"]
+argument-hint: ""
+---
+
+Use the /lisa:wiki-install skill to enable the lisa-wiki plugin in this project. $ARGUMENTS

package/plugins/lisa-cursor/hooks/block-no-verify.sh

@@ -0,0 +1,37 @@
+#!/usr/bin/env bash
+# PreToolUse hook for Bash: blocks any command containing --no-verify.
+# --no-verify on git commit/push (and equivalents) bypasses pre-commit/pre-push
+# hooks that exist for a reason. The fix is to address the underlying issue,
+# not silence the check. See feedback_never_no_verify in user memory.
+#
+# Word-boundary match avoids false positives on flags like --no-verify-ssl,
+# --no-verify-host, etc.
+set -euo pipefail
+
+input="$(cat)"
+
+tool_name="$(printf '%s' "$input" | jq -r '.tool_name // empty')"
+if [ "$tool_name" != "Bash" ]; then
+  exit 0
+fi
+
+command_str="$(printf '%s' "$input" | jq -r '.tool_input.command // empty')"
+if [ -z "$command_str" ]; then
+  exit 0
+fi
+
+# Match --no-verify bounded by non-token characters (not alphanumeric, _, or -).
+# This catches all syntactic positions including subshells (e.g. `(git commit --no-verify)`)
+# while excluding longer flags like --no-verify-ssl, --no-verify-host, etc.
+if printf '%s' "$command_str" | grep -Eq '(^|[^[:alnum:]_-])--no-verify($|[^[:alnum:]_-])'; then
+  cat >&2 <<'EOF'
+Blocked: --no-verify bypasses pre-commit/pre-push hooks. Fix the underlying
+issue (lint error, failing test, formatting) or ask the user before bypassing.
+
+If the user has explicitly authorized the bypass for this specific command,
+re-run after they confirm.
+EOF
+  exit 2
+fi
+
+exit 0

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

@@ -0,0 +1,69 @@
+#!/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
+
+# The tools below use Linux-specific binaries and paths — skip on other platforms.
+if [ "$(uname -s)" != "Linux" ]; then
+  exit 0
+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-cursor/hooks/notify-ntfy.sh

@@ -0,0 +1,183 @@
+#!/bin/bash
+# This file is managed by Lisa.
+# Do not edit directly — changes will be overwritten on the next `lisa` run.
+# =============================================================================
+# ntfy.sh Notification Hook for Claude Code
+# =============================================================================
+# Sends desktop and mobile notifications via ntfy.sh when Claude needs
+# attention or finishes a task.
+#
+# Setup:
+#   1. Install ntfy app on mobile (iOS App Store / Android Play Store)
+#   2. Subscribe to your unique topic in the app
+#   3. Set NTFY_TOPIC environment variable (e.g., in ~/.bashrc or ~/.zshrc):
+#      export NTFY_TOPIC="my-claude-alerts-xyz123"
+#
+# @see https://ntfy.sh
+# =============================================================================
+
+# Read JSON input from stdin
+INPUT=$(cat)
+
+# Extract hook event name
+HOOK_EVENT=$(echo "$INPUT" | grep -o '"hook_event_name"[[:space:]]*:[[:space:]]*"[^"]*"' | sed 's/.*: *"//' | sed 's/"$//')
+
+# Extract notification type (for Notification hooks)
+NOTIFICATION_TYPE=$(echo "$INPUT" | grep -o '"notification_type"[[:space:]]*:[[:space:]]*"[^"]*"' | sed 's/.*: *"//' | sed 's/"$//')
+
+# Extract message if available
+MESSAGE=$(echo "$INPUT" | grep -o '"message"[[:space:]]*:[[:space:]]*"[^"]*"' | sed 's/.*: *"//' | sed 's/"$//')
+
+# Extract session ID (first 8 chars for brevity)
+FULL_SESSION_ID=$(echo "$INPUT" | grep -o '"session_id"[[:space:]]*:[[:space:]]*"[^"]*"' | sed 's/.*: *"//' | sed 's/"$//')
+SESSION_ID="${FULL_SESSION_ID:0:8}"
+
+# Extract transcript path for task summary
+TRANSCRIPT_PATH=$(echo "$INPUT" | grep -o '"transcript_path"[[:space:]]*:[[:space:]]*"[^"]*"' | sed 's/.*: *"//' | sed 's/"$//')
+
+# Determine source (Web vs Local)
+if [ "$CLAUDE_CODE_REMOTE" = "true" ]; then
+    SOURCE="Web"
+else
+    SOURCE="Local"
+fi
+
+# Get project name from current directory
+PROJECT_NAME=$(basename "$CLAUDE_PROJECT_DIR" 2>/dev/null || basename "$(pwd)")
+
+# Load NTFY_TOPIC from local config if not already set
+if [ -z "$NTFY_TOPIC" ]; then
+    # Check for project-local config (gitignored)
+    if [ -f "$CLAUDE_PROJECT_DIR/.claude/env.local" ]; then
+        # shellcheck source=/dev/null
+        source "$CLAUDE_PROJECT_DIR/.claude/env.local"
+    fi
+    # Check for user-global config
+    if [ -z "$NTFY_TOPIC" ] && [ -f "$HOME/.claude/env.local" ]; then
+        # shellcheck source=/dev/null
+        source "$HOME/.claude/env.local"
+    fi
+fi
+
+# Exit silently if still not configured
+if [ -z "$NTFY_TOPIC" ]; then
+    exit 0
+fi
+
+# Extract task summary from transcript (last assistant message, truncated)
+TASK_SUMMARY=""
+if [ -n "$TRANSCRIPT_PATH" ] && [ -f "$TRANSCRIPT_PATH" ]; then
+    # Get the last assistant message from the JSONL transcript
+    # The transcript contains lines with "type":"assistant" and "message" content
+    # Use awk for cross-platform compatibility (tac is not available on macOS)
+    LAST_ASSISTANT=$(awk '/"type"[[:space:]]*:[[:space:]]*"assistant"/{line=$0} END{if(line) print line}' "$TRANSCRIPT_PATH" 2>/dev/null)
+    if [ -n "$LAST_ASSISTANT" ]; then
+        # Extract the message content - look for text content in the message
+        # Format: {"message":{"content":[{"type":"text","text":"..."}]}}
+        # Use jq for robust JSON parsing when available, fallback to grep/sed
+        if command -v jq >/dev/null 2>&1; then
+            RAW_SUMMARY=$(echo "$LAST_ASSISTANT" | jq -r '.message.content[] | select(.type == "text") | .text' 2>/dev/null | head -1)
+        else
+            # Fallback: simple regex extraction (may fail on escaped quotes)
+            RAW_SUMMARY=$(echo "$LAST_ASSISTANT" | grep -o '"text"[[:space:]]*:[[:space:]]*"[^"]*"' | head -1 | sed 's/.*: *"//' | sed 's/"$//')
+        fi
+        if [ -n "$RAW_SUMMARY" ]; then
+            # Truncate to 100 chars and clean up newlines
+            TASK_SUMMARY=$(echo "$RAW_SUMMARY" | tr '\n' ' ' | cut -c1-100)
+            # Add ellipsis if truncated
+            if [ ${#RAW_SUMMARY} -gt 100 ]; then
+                TASK_SUMMARY="${TASK_SUMMARY}..."
+            fi
+        fi
+    fi
+fi
+
+# Build session info string (shown in body)
+SESSION_INFO=""
+if [ -n "$SESSION_ID" ]; then
+    SESSION_INFO="Session: $SESSION_ID"
+fi
+
+# Determine notification title and body based on hook type
+case "$HOOK_EVENT" in
+    "Notification")
+        case "$NOTIFICATION_TYPE" in
+            "permission_prompt")
+                TITLE="Claude [$SOURCE] - Permission Required"
+                BODY="${MESSAGE:-Claude needs your permission to continue}"
+                if [ -n "$SESSION_INFO" ]; then
+                    BODY="$SESSION_INFO
+$BODY"
+                fi
+                PRIORITY="high"
+                TAGS="warning"
+                ;;
+            "idle_prompt")
+                TITLE="Claude [$SOURCE] - Waiting"
+                BODY="${MESSAGE:-Claude is waiting for your input}"
+                if [ -n "$SESSION_INFO" ]; then
+                    BODY="$SESSION_INFO
+$BODY"
+                fi
+                PRIORITY="default"
+                TAGS="hourglass"
+                ;;
+            *)
+                TITLE="Claude [$SOURCE] - Attention"
+                BODY="${MESSAGE:-Claude needs your attention}"
+                if [ -n "$SESSION_INFO" ]; then
+                    BODY="$SESSION_INFO
+$BODY"
+                fi
+                PRIORITY="default"
+                TAGS="bell"
+                ;;
+        esac
+        ;;
+    "Stop")
+        TITLE="Claude [$SOURCE] - Finished"
+        BODY="$PROJECT_NAME"
+        if [ -n "$SESSION_INFO" ]; then
+            BODY="$SESSION_INFO | $BODY"
+        fi
+        if [ -n "$TASK_SUMMARY" ]; then
+            BODY="$BODY
+$TASK_SUMMARY"
+        fi
+        PRIORITY="default"
+        TAGS="white_check_mark"
+        ;;
+    "SubagentStop")
+        TITLE="Claude [$SOURCE] - Subagent Done"
+        BODY="$PROJECT_NAME"
+        if [ -n "$SESSION_INFO" ]; then
+            BODY="$SESSION_INFO | $BODY"
+        fi
+        if [ -n "$TASK_SUMMARY" ]; then
+            BODY="$BODY
+$TASK_SUMMARY"
+        fi
+        PRIORITY="low"
+        TAGS="checkered_flag"
+        ;;
+    *)
+        TITLE="Claude [$SOURCE]"
+        BODY="${MESSAGE:-Event: $HOOK_EVENT}"
+        if [ -n "$SESSION_INFO" ]; then
+            BODY="$SESSION_INFO
+$BODY"
+        fi
+        PRIORITY="default"
+        TAGS="robot"
+        ;;
+esac
+
+# Send notification via ntfy.sh
+curl -s \
+    -H "Title: $TITLE" \
+    -H "Priority: $PRIORITY" \
+    -H "Tags: $TAGS" \
+    -d "$BODY" \
+    "https://ntfy.sh/$NTFY_TOPIC" > /dev/null 2>&1
+
+exit 0

package/plugins/lisa-cursor/hooks/setup-jira-cli.sh

@@ -0,0 +1,51 @@
+#!/usr/bin/env bash
+##
+# Writes the JIRA CLI config file from environment variables.
+# Runs on SessionStart so the config is available for every session.
+#
+# Required env vars (must be created in your Claude Code Web environment):
+#   JIRA_INSTALLATION - cloud or local
+#   JIRA_SERVER       - Atlassian instance URL
+#   JIRA_LOGIN        - login email
+#   JIRA_PROJECT      - default project key
+#   JIRA_API_TOKEN    - already expected by jira-cli natively
+#
+# Optional env vars:
+#   JIRA_BOARD        - default board name
+##
+
+set -euo pipefail
+
+# Fix jira-cli installation if install-pkgs.sh failed to extract correctly.
+# Only attempt on Linux — the binary download is Linux-only.
+if [[ "$(uname -s)" == "Linux" ]] && ! command -v jira &>/dev/null; then
+  JIRA_CLI_VERSION="1.7.0"
+  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 "${TMPDIR}"
+  cp "${TMPDIR}/jira_${JIRA_CLI_VERSION}_linux_x86_64/bin/jira" /usr/local/bin/jira
+  chmod +x /usr/local/bin/jira
+  rm -rf "${TMPDIR}"
+fi
+
+CONFIG_DIR="${HOME}/.config/.jira"
+CONFIG_FILE="${CONFIG_DIR}/.config.yml"
+
+# Skip config write if required vars are missing
+if [[ -z "${JIRA_SERVER:-}" || -z "${JIRA_LOGIN:-}" ]]; then
+  exit 0
+fi
+
+mkdir -p "${CONFIG_DIR}"
+
+cat > "${CONFIG_FILE}" << EOF
+installation: ${JIRA_INSTALLATION:-cloud}
+server: ${JIRA_SERVER}
+login: ${JIRA_LOGIN}
+project: ${JIRA_PROJECT:-}
+board: "${JIRA_BOARD:-}"
+auth_type: basic
+epic:
+  name: Epic Name
+  link: Epic Link
+EOF