@codyswann/lisa 2.189.7 → 2.189.8

package/plugins/lisa-cursor/skills/epic-triage/SKILL.md

@@ -1,28 +0,0 @@
----
-name: epic-triage
-description: "9-step epic triage and 5-step implementation workflow. Ensures epics are fully scoped, broken down, and ordered before execution begins."
----
-
-# Epic Triage
-
-Follow this 9-step triage process before implementing any epic. Do not skip triage.
-
-## Triage Steps
-
-1. Verify you have all information needed to understand the full scope of this epic (goals, acceptance criteria, impacted systems, design specs, dependencies, etc.). Do not make assumptions. If anything is missing, stop and ask before proceeding.
-2. Verify the epic is broken down into concrete, well-scoped bugs, tasks, and/or stories that are each fully triaged. If ambiguities exist, stop and resolve them before breaking it down.
-3. Identify all cross-cutting concerns (auth, performance, security, data migrations, third-party integrations) that need to be addressed across the epic.
-4. Identify all dependencies between tasks within the epic, or on external epics, teams, or services. Determine the correct order of execution.
-5. Verify you have access to the tools, environments, and permissions needed to deploy and verify all tasks within this epic (e.g. CI/CD pipelines, deployment targets, logging/monitoring systems, API access, database access). If any are missing or inaccessible, stop and raise them before proceeding.
-6. Define the overall test strategy for the epic (unit, integration, end-to-end, load testing).
-7. Define the documentation that will need to be created or updated to cover the full scope of the epic so another developer understands the architecture, design decisions, and implementation.
-8. Define measurable acceptance criteria that confirm the epic is fully complete.
-9. Define how you will verify the epic is fully delivered beyond a shadow of a doubt (e.g. deploy to the target environment, walk through all acceptance criteria end-to-end, confirm all child tasks/stories are closed, confirm no regressions).
-
-## Implementation
-
-1. Use the output of the triage steps above as your guide. Do not skip triage.
-2. Work through each task and/or story in the order defined during triage, respecting dependencies.
-3. Apply the Bug Implementation and Task Implementation processes to each child bug or task, respectively, as you work through them.
-4. Continuously update the epic and its child issues in JIRA as progress is made.
-5. Do not consider the epic complete until all acceptance criteria are verified in the target environment and all child issues are resolved.

package/plugins/lisa-cursor/skills/exploratory-qa/SKILL.md

@@ -1,91 +0,0 @@
----
-name: exploratory-qa
-description: First-time-user exploratory QA pass for ANY product type (DOM web app, HTTP/API backend, canvas game, CLI/library, IaC/CDK) that FEEDS THE LIFECYCLE. Use when asked to experience a product the way a brand-new end user would — driving its real consumer-facing interface via the `use-the-product` core (which detects the product type, resolves the per-environment mutation policy from .lisa.config.json so production data is never mutated by accident, and explores through the project's personas when it defines them) to find anything confusing, broken, or hard to use (unclear purpose, human-facing jargon, machine-style labels, contextless data, wrong control semantics, dead-end flows, incomplete end-states, clipped/unreachable controls, slow loads). Static route scans, HTTP fetches, screenshots alone, or console/network checks alone are not sufficient evidence. Instead of writing a report file, it files every finding as a tracked work item via lisa:tracker-write. A `ready` parameter controls whether those tickets are created build-ready (auto-picked-up by lisa:intake) or left in the backlog for human triage (default). For gaps in the automated test suite, use e2e-coverage-gaps instead.
----
-
-# Exploratory QA
-
-## Overview
-
-Experience the product the way a **brand-new end user** would: drive its real consumer-facing interface and actually try to use it, then surface anything **confusing, broken, or hard to understand**. This is a usability/experience pass, **not** a test-coverage audit (for that, use `e2e-coverage-gaps`). Every finding is filed as a tracked work item so it enters the Lisa lifecycle — no static report file.
-
-**How you drive the product is owned by the `use-the-product` core skill.** Invoke it first: it detects the product type (web / API / game / CLI / IaC), resolves the target environment and its **mutation policy** (so you never mutate production without an explicit, justified opt-in), and discovers the project's **personas** so you can explore as each one. This skill supplies the **QA lens** — what to look for and how to file it.
-
-## Parameters
-
-- **`target-url | env`** (first positional) — what to explore (passed through to `use-the-product`).
-- **`ready=true|false`** — the build-ready state for the tickets this pass creates.
-  - `ready=true` → created build-ready, so `lisa:intake` / the build-intake scanner auto-picks them up.
-  - `ready=false` (**default**) → created in the backlog for a human to review and promote.
-
-## 1. Set up
-
-- **Invoke `use-the-product`** to detect the product type, resolve the environment + mutation policy, and discover personas/subagents. Everything about *how* to drive the product, *where*, and *how much you may mutate* comes from there — do not re-derive it.
-- **Confirm the tracker is configured.** Findings are filed as tickets, so read `tracker` from `.lisa.config.json` (local overrides global). If unset, stop and report that the tracker must be configured (`/lisa:setup:jira` / `:github` / `:linear`) before exploratory QA can file findings — do not silently fall back to a report file.
-- Read the `ready` flag (default `false`).
-
-## 2. Arrive cold and use it like a human
-
-- Start with **no prior knowledge** — do not pre-read the codebase to learn the intended flows; discover them the way a user would. Form a first impression: is it obvious what this product is, what to do first, and where to go next?
-- Then actually attempt real tasks through the interface (per `use-the-product`'s per-type playbook), exercising representative controls/endpoints/commands — a first-time user explores, makes mistakes, and tries the obvious thing.
-
-## 3. The QA lens — what to look for
-
-Cover at least these dimensions unless the user narrows scope. Most are universal; the web-specific ones are marked and have per-type equivalents in §4.
-
-- **Comprehension & labeling:** user-facing copy must read like something a normal first-time user understands. Flag machine-style/developer labels (raw IDs, enum keys, `snake_case`, `null`/`undefined`, untranslated i18n keys), admin/database terms ("metadata", "rows", "record", "entity"), unexplained jargon, unclear button/menu names, and meaningless icons. If a label would make a non-technical user ask "what does that mean?", file a clarity ticket.
-- **Data usefulness & context:** facts, metrics, and tables must help a person understand the surface, not just prove extraction happened. If a user can't tell what a number or field refers to without rereading the raw source, file a ticket to add context (excerpts, labels, grouping, provenance) or hide it.
-- **Data volume & trust:** compare visible data to what the surface promises. A rich view with only a few items can read as broken/filtered/still-loading. File a finding when sparse data isn't explained (result counts, active filters, reset affordances, coverage status, sample labeling).
-- **Controls & mental model:** controls must match what they do (sort ≠ filter; search ≠ facet; finite domains want selects/typeaheads, not blank text inputs). Flag controls that make users guess spelling/casing, hide the option universe, or use the wrong component.
-- **Flow completeness & expected counterparts:** a screen that gates access or shows one side of a standard paired flow must offer the other side, or a clear path to it. A new user must never hit a dead end with no next step. Flag: **sign-in with no sign-up** (or vice-versa), **no account recovery** ("Forgot password?", resend verification), **no exit from a state** (no sign-out; a modal/wizard with no back/close/cancel), **one-way actions** (create with no edit/delete where both are expected), **unreachable entry points** (a feature only reachable by guessing a URL; an empty state with no primary action). When the missing counterpart makes a core task impossible for a class of users, file a `Bug`; otherwise a usability `Improvement`.
-- **Action preconditions & incomplete end-states:** an action that needs multiple inputs or a prerequisite (compare, merge, bulk-edit) should guide the user to satisfy it — disable/explain until met, collect inputs first, or give the destination an in-place control. Actually trigger these and watch where they land; flag when a primary action fires under-satisfied and strands the user, lands on an empty/partial end-state with no next step, or is offered where it cannot succeed. Left unable to finish → `Bug`; works but confusing → `Improvement`.
-- **Navigation clarity:** is it obvious how to get somewhere and back? Flag dead ends, hidden entry points, surprising redirects, broken links, no clear "home", and duplicated nav that competes for space without page-specific value.
-- **Behavior correctness:** does the obvious action do what a user expects? Confusing errors, silent failures, disabled controls with no explanation, state that doesn't persist.
-- **Affordance clarity:** can the user tell what is clickable, required, in-progress, or complete?
-- **Load & responsiveness:** long/unclear loads, blank or skeleton-only shells, spinners with no progress. Flag surfaces that report "loaded" but where meaningful content arrives much later. Capture user-perceived timings (shell visible, first meaningful content, stable content); if the delay is noticeable, file it even when the eventual content is correct.
-- **Visual/layout quality (DOM web):** cut-off/truncated text, overlap, cramped density, offscreen controls, accidental horizontal scroll. **Do not judge by eyeballing a screenshot alone** — confirm with the layout-integrity sweep in §4.
-- **Consistency / standard UX:** components, spacing, terminology, and interaction patterns should be consistent and follow common conventions. Flag anything non-standard or screen-to-screen drift.
-
-## 4. Type-specific depth
-
-- **DOM web app — breakpoints & layout integrity.** Sweep a range of widths, including the *in-between* ones where clipping appears (e.g. 360, 390, 414, 600, 768, 834, 1024, 1280, 1440 plus ~900–1180 steps), and re-walk key paths at each. At every width, in addition to looking, take DOM measurements and treat as findings: **container overflow** (`documentElement.scrollWidth > clientWidth`); **clipped/offscreen controls** (a control's `getBoundingClientRect()` falling outside the viewport or an `overflow:hidden|clip|auto|scroll` ancestor — e.g. a submit button cut off by its filter card); **truncated meaningful text** (`scrollWidth > clientWidth` / ellipsis on text that carries meaning); **colliding controls** (label overlapping an adjacent control with no gap). A primary/interactive control that is clipped, offscreen, or unreachable is a **`Bug`**, not an Improvement.
-- **HTTP / API backend.** Judge the *contract as a consumer experiences it*: unclear/inconsistent status codes, error responses with no actionable message, payloads exposing internal shapes (raw enums, DB column names), missing pagination/among-counts, endpoints that 500 on obvious edge inputs. A broken/incorrect response is a `Bug`; a confusing-but-working contract is an `Improvement`.
-- **Canvas game.** Judge readability at gameplay scale, input responsiveness/latency, game-feel, unclear objectives, and silent state changes — not DOM breakpoints. A soft-lock or lost progress is a `Bug`; unclear-but-playable friction is an `Improvement`.
-- **CLI / library.** Judge help/output clarity, error messages, discoverability of commands, and surprising side effects. A wrong result / crash is a `Bug`; confusing UX is an `Improvement`.
-- **IaC / CDK (read-only).** From `cdk synth`/`diff`: over-broad IAM, missing/opaque stack outputs, resources that don't serve their stated purpose, drift. A security-relevant misconfiguration is a `Bug`; unclear-but-correct infra is an `Improvement`.
-
-## 5. Mutation
-
-Whether you may create/edit/delete — and as which account — is set by the `use-the-product` mutation policy (`read-only` vs `full`, `identity`, production rules). Follow its **Mutation Discipline** when the policy is `full` (prefixed test data, identify + verify cleanup, record residue). Never mutate an env the policy marks `read-only` or `forbidden`; if a finding can only be confirmed by a forbidden mutation, file it as observed-and-blocked rather than escalating.
-
-## 6. File findings as tracked work
-
-No report file. Every finding becomes a **leaf work item** via `lisa:tracker-write` (the vendor-neutral writer — it dispatches to the configured tracker and runs the validation gate; never call a vendor `*-write-*` skill directly):
-
-| Finding | `issue_type` | `build_ready` |
-|---|---|---|
-| User-visible **bug** (broken behavior) | `Bug` | the `ready` flag (default `false`) |
-| **Usability / UX / clarity issue** | `Improvement` | the `ready` flag (default `false`) |
-
-Each finding is a flat leaf, so `build_ready` applies directly — pass it explicitly on every create. Each ticket MUST be a complete spec (the validator rejects thin tickets): a **three-audience description**; for a **bug**, exact reproduction steps, observed-vs-expected, the env / account / interface it occurred at, and evidence; for a **usability issue**, the observed friction, who it affects, **where**, and the proposed improvement; and **Gherkin acceptance criteria** for the fixed behavior.
-
-### Idempotency — don't spam duplicates
-
-Re-running a pass must not refile the same finding. Before creating a ticket, search the tracker for an **open** ticket carrying a stable marker `[lisa-exploratory-qa] <finding-key>` in its body (the `<finding-key>` is a stable slug of surface + symptom, e.g. `settings-modal/horizontal-overflow@tablet`). If one exists, reference/update it instead; only create when none exists. **Match by the marker, never by title.** A *closed* prior ticket does not suppress a new one — a recurrence after a fix is a genuine regression.
-
-## Output
-
-No report file. Emit a concise in-session summary:
-
-- **Scope:** product type, target env + mutation level, persona(s) explored as, tool, build/version if visible, date.
-- **First impression:** could a new user tell what the product is and what to do first?
-- **Findings filed**, bucketed by type — each with its **created or referenced ticket ref** and **build-ready state**.
-- **Observed but not filed:** anything noticed but intentionally not ticketed (including forbidden-mutation blocks), with why.
-
-## Quality bar
-
-- Explore as a true first-time user — judge clarity, not whether you (who can read the code) can figure it out.
-- Every ticket must stand alone for an implementer who was not in the session.
-- Do not claim cleanup succeeded unless verified.
-- File per the `ready` flag (default: backlog for human triage).
-- Route automated-coverage gaps to `e2e-coverage-gaps`; preserve unrelated repo changes.

package/plugins/lisa-cursor/skills/fix-linter-error/SKILL.md

@@ -1,45 +0,0 @@
----
-name: fix-linter-error
-description: This skill should be used when fixing all violations of one or more ESLint rules across the codebase. It runs the linter, groups violations by rule and file, generates a brief with fix strategies, and creates a plan with tasks to implement the fixes.
-allowed-tools: ["Read", "Bash", "Glob", "Grep"]
-
----
-
-# Fix Linter Errors
-
-Target rules: $ARGUMENTS
-
-If no arguments provided, prompt the user for at least one lint rule name.
-
-## Step 1: Gather Requirements
-
-1. **Parse rules** from $ARGUMENTS (space-separated)
-2. **Run linter** to collect all violations:
-   ```bash
-   bun run lint 2>&1
-   ```
-3. **Group violations** by rule, then by file, noting:
-   - File path and line numbers
-   - Violation count per file
-   - Sample error messages
-
-## Step 2: Compile Brief and Delegate
-
-Compile the gathered information into a structured brief:
-
-```
-Fix ESLint violations for rules: $ARGUMENTS
-
-Violations by rule:
-- [rule-name-1]: X total violations across Y files
-  - [file]: N violations (lines: ...)
-  - ...
-- [rule-name-2]: X total violations across Y files
-  - ...
-
-Fix strategies: extract functions, early returns, apply formatting, add types
-
-Verification: `bun run lint 2>&1 | grep -E "($ARGUMENTS)" | wc -l` → Expected: 0
-```
-
-Invoke `/implement` with this brief to create the implementation plan.

package/plugins/lisa-cursor/skills/generate-claude-remote-build-script/SKILL.md

@@ -1,224 +0,0 @@
----
-name: generate-claude-remote-build-script
-description: "Generate the setup/build script (and env-var template) to paste into a Claude Code remote routine environment so this repo runs in the cloud. Runs /lisa:analyze-claude-remote to inventory needs, then writes an idempotent, detect-before-install bash script that installs the required CLIs/binaries and package manager for both Lisa and the host project, plus a commented environment-variable template (names only, never real secrets) and a list of custom domains to allowlist. The script is fast (fits the ~5-minute environment-cache budget), re-runnable, and cloud-proxy aware."
-allowed-tools: ["Skill", "Bash", "Read", "Write", "Glob", "Grep"]
----
-
-# Generate Claude Remote Build Script: $ARGUMENTS
-
-Produce the artifacts a user pastes into a **Claude Code remote routine environment** so this repo
-runs in the cloud: a setup/build script that installs everything the environment needs, plus an
-environment-variable template and a network-allowlist list.
-
-## Purpose
-
-A routine's cloud environment lets you configure a **setup script** (runs once, cached) and
-**environment variables**. This skill turns the read-only inventory from
-`/lisa:analyze-claude-remote` into those concrete artifacts so the user doesn't hand-assemble them.
-
-This skill ships in the base Lisa plugin and is distributed to every host project, so the generated
-script must reflect **what this repo actually needs** — Lisa's startup hooks and configured
-tracker/source, plus the host project's own package manager and tooling — not a hardcoded list.
-
-## Inputs
-
-- Optional flags in `$ARGUMENTS`:
-  - `--out=<path>` — where to write the script. Default `scripts/claude-remote-setup.sh`.
-  - `--include-optional` — also install `OPTIONAL` (dormant-stack) tools. Default: required only.
-  - `--print` — print the script to stdout instead of writing a file.
-
-## Procedure
-
-1. **Inventory.** Invoke `/lisa:analyze-claude-remote --json` and parse its machine-readable
-   inventory block (`packageManager`, `tools`, `env`, `mcp`, `gaps`, `platform`,
-   `networkAccess`, `allowlistDomains`, `awsProfiles`). If the analysis cannot run, stop and report why — never
-   emit a script from guesses.
-
-2. **Compose the setup script** from the inventory. The script must be:
-   - **Idempotent & detect-before-install** — every install guarded by a `command -v <tool>` check
-     so re-runs are no-ops and already-present tools are skipped.
-   - **Fast** — fits the ~5-minute environment-cache budget; avoid heavyweight installs unless
-     `REQUIRED`. Long/optional installs (docker images, chromium, ruby) go in a clearly-marked
-     optional section gated by `--include-optional`.
-   - **PATH-correct** — export the package manager's bin dir (e.g. `$HOME/.bun/bin`) after install
-     so subsequent steps and the cached environment resolve it.
-   - **Cloud-proxy aware** — when the package manager is flagged `RISK` (bun), add a comment
-     documenting the known proxy package-fetch issue and, where safe, run the install with retries
-     so a transient proxy failure doesn't poison the cache. Do not silently swap package managers if
-     `engines` forbids it; surface the risk as a comment instead.
-   - **Non-fatal on optional tools** — `REQUIRED` tool failures should exit non-zero (so the env
-     build fails loudly); `OPTIONAL` tool failures should warn and continue.
-
-3. **Emit the environment-variable template.** Write a commented block listing every `env` entry
-   from the inventory grouped by integration, marked `REQUIRED`/`OPTIONAL` and `secret`/`plain`,
-   with the reason. **Never write real secret values** — only names and placeholders, because the
-   environment config is visible to anyone who can edit it. Entries flagged `providedBy: settings.json`
-   (the committed `.claude/settings.json` `env` flags, e.g. `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS`) are
-   **already applied from the committed file** — list them under an `# Already provided by committed
-   .claude/settings.json — no UI entry needed` heading, not as values to set. The "set in the
-   environment UI" template is for **secrets only**. For every secret entry that carries
-   `acquireUrl`/`accessScope`/`headlessSubstrate` (the
-   active tracker/source credentials from the analysis's group 4a), render those as comment lines
-   directly above the name — `# Acquire: <url>` and `# Access: <scope>` — so the user knows exactly
-   where to get the token and what permissions it needs. Emit only the **env-var form** of the name
-   that the analysis reported (including any per-account suffixed form like `LINEAR_API_KEY_<slug>`);
-   never emit a keychain instruction — keychain does not exist in a cloud routine.
-   When the entry is `GH_TOKEN`, add a comment from `platform.githubProxy` clarifying that the token
-   is for `gh` CLI commands against the project/Lisa repos, not for raw git clone/fetch/push or
-   sibling repos reachable through the routine's GitHub proxy.
-   For OPTIONAL non-tracker MCP recovery entries discovered by
-   `/lisa:analyze-claude-remote`, preserve the same names-only behavior:
-   include `JAM_PAT`, `SONAR_TOKEN`, or similar documented substrate env vars
-   only as optional secrets, with their acquire/scope comments when the analysis
-   supplied them. Never invent values or promote dormant substrates to required.
-   When AWS entries are present, list `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, optional
-   `AWS_SESSION_TOKEN`, and `AWS_DEFAULT_REGION` exactly as the analysis reported. State that these
-   bootstrap credentials are for STS assume-role only; do not emit or recommend `aws sso login`.
-
-3a. **Emit substrate setup snippets.** When the inventory marks an MCP
-   `headlessUsable: true` through a documented substrate, render the matching
-   wiring guidance as commented, opt-in setup:
-   - CLI substrates: emit the detected install/login commands gated on the
-     optional env var. For Jam, this means `curl -fsSL https://native.jam.dev/install | bash`,
-     `export PATH="$HOME/.local/bin:$PATH"`, `printf '%s' "$JAM_PAT" | jam auth login --token`,
-     and `jam skills install`, all inside `[ -n "${JAM_PAT:-}" ] && ...` guards so missing
-     optional secrets do not fail the environment build.
-   - REST substitute substrates: do not install an MCP. Emit comments naming the
-     REST host and env var (for example `SONAR_TOKEN` with `https://sonarcloud.io/api/`) and
-     rely on the access skill or generated consumer to call the API.
-   - PAT-bearer MCP substrates: print a commented `.mcp.json` `headers` snippet from the
-     inventory's `mcpHeaders`. Use this only when the analysis explicitly says the same MCP
-     transport supports static-token auth. Do not print a Jam `.mcp.json` header snippet because
-     Jam's preferred headless substrate is its PAT-authenticated CLI.
-
-3b. **Emit AWS assume-role profile setup.** When the inventory includes `awsProfiles`, write an
-   idempotent `~/.aws/config` block gated on `[ -n "${AWS_ACCESS_KEY_ID:-}" ]`. The generated block
-   must:
-   - `mkdir -p "$HOME/.aws"` and create or append profile stanzas without writing secrets.
-   - Emit one `[profile <name>]` stanza per inventory profile with `role_arn`,
-     `credential_source = Environment`, `region` when present, and `external_id` when present.
-   - Keep regions and ExternalIds as non-secret project metadata from the inventory; never invent
-     account IDs, role names, profile names, regions, or ExternalIds.
-   - Warn and skip profile writing when AWS profile metadata is absent, while still listing the
-     required `AWS_*` env var names in the secret template.
-   - Include a comment that agents should use `aws --profile <name> ...` and must not run
-     `aws sso login` in headless routines.
-
-4. **Emit the allowlist + gaps notice.** List any custom domains the setup or runtime reaches
-   (from `networkAccess.allowlistDomains`, falling back to legacy `allowlistDomains`) that the user
-   must add when the environment needs Custom network access. Do not include default Trusted domains
-   such as GitHub, npm/PyPI registries, or Docker Hub. Echo the `gaps` from the analysis
-   (auto-memory not synced, interactive-auth/stdio-MCP unavailable, etc.) and the
-   `platform.secretsVisibility` warning as a header comment so the user knows what the script
-   **cannot** fix.
-
-5. **Write and report.** Write the script to `--out` (default `scripts/claude-remote-setup.sh`),
-   `chmod +x` it, and print: the path, a one-line summary of what it installs and which env vars to
-   set, and the exact next step (paste its contents — or a `bash scripts/claude-remote-setup.sh`
-   invocation — into the routine environment's setup script, and add the env vars in the
-   environment config). When `--print` is passed, print to stdout and do not write a file.
-
-## Generated script shape
-
-The emitted script should follow this skeleton (populated from the live inventory — this is the
-shape, not a fixed payload):
-
-```bash
-#!/usr/bin/env bash
-# Claude Code remote-routine setup for <repo>. Generated by /lisa:generate-claude-remote-build-script.
-# Paste into your routine environment's setup script. Re-runnable and idempotent.
-#
-# GAPS this script cannot fix (configure separately):
-#   - <gaps from analysis, e.g. auto-memory is machine-local and not synced to cloud routines>
-# Already provided by committed .claude/settings.json (applied automatically — no UI entry needed):
-#   - CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS, ENABLE_LSP_TOOL, BASH_DEFAULT_TIMEOUT_MS, BASH_MAX_TIMEOUT_MS
-# SECRETS to set in the environment config (names only — set real values there, not here):
-#   # --- credentials for the active tracker/source (set in the environment UI) ---
-#   # Acquire: https://github.com/settings/personal-access-tokens
-#   # Access:  fine-grained PAT on target repo: Contents R/W, Issues R/W, Pull requests R/W, Metadata R
-#   # Note: GH_TOKEN is for gh CLI only. Raw git uses Claude's connected-GitHub proxy/identity;
-#   # sibling repos reached only by raw git do not need to be in this token scope.
-#   - GH_TOKEN=<token>                          # REQUIRED, github is the active tracker+source
-#   - AWS_ACCESS_KEY_ID=<access-key-id>          # REQUIRED when AWS inventory is active
-#   - AWS_SECRET_ACCESS_KEY=<secret-access-key>  # REQUIRED when AWS inventory is active
-#   - AWS_SESSION_TOKEN=<session-token>          # OPTIONAL for temporary bootstrap creds
-# NETWORK: set the environment to Custom and allowlist these non-default domains if not on Full:
-#   - <networkAccess.allowlistDomains, if any>
-set -uo pipefail
-
-need() { command -v "$1" >/dev/null 2>&1; }
-require() { need "$1" || { echo "FATAL: required tool '$1' missing and install failed" >&2; exit 1; }; }
-
-# --- package manager (REQUIRED) ---
-# Resolve the PM from packageManager/engines/lockfiles — emit the manager the
-# `packageManager` inventory field reported, NEVER a hardcoded bun. An npm-only
-# project (engines.bun = "please-use-npm") must install with npm; emitting
-# `bun install` would create a stray bun.lock and break it (the SE-5221
-# regression). Only install/PATH-export the manager actually selected below.
-detect_package_manager() {
-  _field="" _forced="" _forbidden=""
-  if [ -f package.json ] && command -v jq >/dev/null 2>&1; then
-    _field=$(jq -r '(.packageManager // "") | sub("@.*$";"")' package.json 2>/dev/null)
-    _forced=$(jq -r 'first((.engines // {})[] | strings | capture("please-use-(?<pm>bun|npm|yarn|pnpm)")?.pm) // ""' package.json 2>/dev/null)
-    _forbidden=$(jq -r '[(.engines // {}) | to_entries[] | select(((.value|strings) // "") | test("please-use|do-not-use";"i")) | .key] | join(" ")' package.json 2>/dev/null)
-  fi
-  case "$_field" in bun | npm | yarn | pnpm) printf '%s\n' "$_field"; return 0 ;; esac
-  case "$_forced" in bun | npm | yarn | pnpm) printf '%s\n' "$_forced"; return 0 ;; esac
-  _pm_allowed() { case " $_forbidden " in *" $1 "*) return 1 ;; *) return 0 ;; esac; }
-  { [ -f bun.lockb ] || [ -f bun.lock ]; } && _pm_allowed bun && { printf 'bun\n'; return 0; }
-  [ -f pnpm-lock.yaml ] && _pm_allowed pnpm && { printf 'pnpm\n'; return 0; }
-  [ -f yarn.lock ] && _pm_allowed yarn && { printf 'yarn\n'; return 0; }
-  [ -f package-lock.json ] && _pm_allowed npm && { printf 'npm\n'; return 0; }
-  printf 'npm\n'
-}
-PM="$(detect_package_manager)"
-if [ "$PM" = "bun" ] && ! need bun; then
-  curl -fsSL https://bun.sh/install | bash
-  export PATH="$HOME/.bun/bin:$PATH"
-fi
-# NOTE: bun has known proxy package-fetch issues in cloud sessions; retry to survive transient proxy errors.
-for i in 1 2 3; do "$PM" install && break || sleep 5; done
-
-# --- required CLIs ---
-need gh || (sudo apt-get update -y && sudo apt-get install -y gh)
-need jq || sudo apt-get install -y jq
-require gh; require jq
-
-# --- AWS assume-role profiles, when inventory includes awsProfiles ---
-if [ -n "${AWS_ACCESS_KEY_ID:-}" ]; then
-  mkdir -p "$HOME/.aws"
-  # Generated stanzas use credential_source=Environment and contain no secrets.
-  # Agents should run: aws --profile <profile> ...
-  # Do not run aws sso login in headless routines; SSO requires an interactive browser/device flow.
-fi
-
-# --- optional, only with --include-optional ---
-# (docker / ruby / chromium / etc., guarded)
-```
-
-## Confirmation policy
-
-Writing the script file is the deliverable — do not ask whether to proceed. Default to writing
-`scripts/claude-remote-setup.sh`, then report the path and next steps. The only legitimate reasons
-to stop are: the analysis could not run, or the `--out` path is not writable.
-
-## Rules
-
-- Always derive the script from a fresh `/lisa:analyze-claude-remote` run — never from a stale or
-  assumed inventory.
-- Never write real secret values into the script or template — names and placeholders only.
-- For active tracker/source credentials, carry the analysis's `Acquire:` URL and `Access:` scope into
-  the template as comments, and emit only the env-var form of the name — never a keychain command.
-- For `GH_TOKEN`, preserve the analysis's GitHub proxy split: it is for `gh` CLI commands only, and
-  raw git/cross-repo clone guidance must not expand the token scope to sibling repositories.
-- Never emit an install for a tool the analysis did not surface, and never install `OPTIONAL` tools
-  unless `--include-optional` is set.
-- When AWS is in the inventory, generate environment-backed assume-role profile stanzas from
-  `awsProfiles`; never emit `aws sso login` as a remote setup step.
-- Prefer `networkAccess.allowlistDomains` over legacy top-level `allowlistDomains`; never emit
-  domains already covered by the routine environment's default Trusted list.
-- Keep the script idempotent and detect-before-install so it is safe to re-run and cache.
-- Preserve the inventory's `REQUIRED` vs `OPTIONAL` distinction in both fail-behavior (fatal vs
-  warn) and section placement.
-- Surface, never hide, the `gaps` — a generated script must not imply it makes a repo fully
-  cloud-ready when known constraints remain.

package/plugins/lisa-cursor/skills/git-commit/SKILL.md

@@ -1,48 +0,0 @@
----
-name: git-commit
-description: This skill should be used when creating conventional commits for current changes. It groups related changes into logical commits, ensures all files are committed, and verifies the working directory is clean afterward.
-allowed-tools: ["Bash"]
----
-
-# Git Commit Workflow
-
-Create conventional commits for current changes. Optional hint: $ARGUMENTS
-
-## Workflow
-
-### See what has changed
-
-!git status
-!git diff --stat
-
-### Apply these requirements
-
-1. **Branch Check**: If on `dev`, `staging`, or `main`, create a feature branch named after the changes
-2. **Commit Strategy**: Group related changes into logical conventional commits (feat, fix, chore, docs, etc.)
-3. **Commit ALL Files**: Every file must be assigned to a commit group - no file gets left out or unstaged
-4. **Commit Creation**: Stage and commit each group with clear messages
-5. **Verification**: Run `git status` to confirm working directory is clean - must show "nothing to commit"
-
-### Use conventional commit format
-
-- `feat:` for new features
-- `fix:` for bug fixes
-- `docs:` for documentation
-- `chore:` for maintenance
-- `style:` for formatting
-- `refactor:` for code restructuring
-- `test:` for test additions
-
-### Never
-
-- use `--no-verify` flag
-- attempt to bypass tests or quality checks
-- skip tests or quality checks
-- stash changes - ALL changes must be committed
-- skip or exclude any files from the commit - even if they're unrelated
-- leave uncommitted changes in the working directory
-- ask the user which files to commit - commit everything
-
-## Execute
-
-Execute the workflow now.

package/plugins/lisa-cursor/skills/git-prune/SKILL.md

@@ -1,35 +0,0 @@
----
-name: git-prune
-description: This skill should be used when pruning local branches that have been deleted on the remote. It fetches remote changes, identifies stale local branches, and safely deletes them.
-allowed-tools: ["Bash"]
----
-
-# Git Prune Local Branches
-
-Remove local branches whose upstream tracking branches have been deleted on remote.
-
-## Workflow
-
-### Fetch and prune remote-tracking references
-
-!git fetch --prune
-
-### Find and delete stale local branches
-
-!git branch -vv | grep ': gone]' | awk '{print $1}'
-
-### Apply these requirements
-
-1. **Preview**: Show which branches will be deleted before deleting
-2. **Safe Delete**: Use `-d` (safe delete) which refuses to delete unmerged branches
-3. **Report**: Show summary of deleted branches
-
-### Never
-
-- Force delete (`-D`) without user confirmation
-- Delete the current branch
-- Delete protected branches (dev, staging, main)
-
-## Execute
-
-Execute the workflow now.

package/plugins/lisa-cursor/skills/git-submit-pr/SKILL.md

@@ -1,113 +0,0 @@
----
-name: git-submit-pr
-description: This skill should be used when pushing changes and creating or updating a pull request. It verifies the branch state, pushes to remote, creates or updates a PR with a comprehensive description, optionally coordinates the resulting Pull Request into the configured GitHub ProjectV2, and enables auto-merge.
-allowed-tools: ["Bash", "Skill", "mcp__github__create_pull_request", "mcp__github__get_pull_request", "mcp__github__update_pull_request"]
----
-
-# Submit Pull Request Workflow
-
-Push current branch and create or update a pull request. Optional hint: $ARGUMENTS
-
-Recognized optional hints:
-
-- `work_item_ref=<ref>` — source tracker item for native development linkage. Examples: `CodySwannGT/lisa#614`, `https://github.com/CodySwannGT/lisa/issues/614`, `ENG-123`, `PROJ-456`.
-- `target_branch=<branch>` or `base=<branch>` — intended PR base branch, used to decide whether a GitHub closing keyword is safe.
-- `tracker_provider=<github|linear|jira|none>` — explicit provider when the ref shape is ambiguous.
-- `pr_url=<url>` — live pull request URL, only needed when updating tracker backlinks from an existing PR context.
-
-## Workflow
-
-### Check current state
-
-!git status
-!git log --oneline -10
-
-### Apply these requirements
-
-1. **Branch Check**: Verify not on `dev`, `staging`, or `main` (cannot create PR from protected branches)
-2. **Commit Check**: Ensure all changes are committed before pushing
-3. **Push**: Push current branch to remote with `-u` flag and the following environment variable - GIT_SSH_COMMAND="ssh -o ServerAliveInterval=30 -o ServerAliveCountMax=5"
-4. **PR Management**:
-   - Check for existing PR on this branch
-   - If exists: Update description with latest changes
-   - If not: Create PR with comprehensive description (not a draft)
-   - Include native development linkage for the source work item when `work_item_ref` can be inferred from `$ARGUMENTS`, the current branch name, an existing PR body, or the issue/ticket context passed by the caller.
-   - After the PR exists, ensure the source work item has a backlink to the PR: invoke `lisa:tracker-sync` with the work item, milestone `pr-ready`, the live `pr_url`, and `tracker_provider` when known. This makes ticket -> PR linkage mandatory, not just a best-effort milestone comment.
-   - After the PR exists, re-resolve the live Pull Request node id and, when `github.projects.v2` is enabled, invoke `lisa:github-project-v2` with `operation: ensure-item` and `content_node_id: <pull-request-node-id>` so linked pull requests join the configured shared Project without replacing the PR as the durable review/merge surface.
-5. **Auto-merge**: Choose merge strategy by PR type:
-   - **Promotion PRs** (env → env, e.g. `dev` → `staging`): use `gh pr merge --auto --merge` (never squash). Squashing flattens the constituent `chore(release): X.Y.Z [skip ci]` commits into one commit titled with the PR title, stripping the `[skip ci]` markers and breaking the release workflow's promotion-detection regex — the destination branch then double-bumps its version. `--merge` keeps each `chore(release)` commit (and its `[skip ci]` marker) intact under a clean merge commit subject the workflow can recognize.
-   - **Feature PRs** (anything → `dev`): use `gh pr merge --auto --merge`.
-6. **Drive to merge**: Opening the PR and enabling auto-merge is not terminal. Delegate the full mergeability loop to the `drive-pr-to-merge` skill — invoke it with the PR number and `merge_method=merge` (and `verify_commit=<pushed head sha>` for the ancestry check). That skill is the single source of truth for clearing every blocker: auto-merge with direct-merge fallback, `BEHIND` re-sync, conflict resolution, failing-check fixes, human + bot (CodeRabbit) review-comment handling with GraphQL thread resolution, stale `CHANGES_REQUESTED` dismissal, and post-merge ancestry verification. It runs inline and uses plain `gh`/`git` so Claude and Codex behave identically. Do not re-implement the loop here.
-
-### Native Development Linkage
-
-Add provider-appropriate linkage to the PR title and/or body without changing the status lifecycle:
-
-- **GitHub Issues**:
-  - If `work_item_ref` is a GitHub issue URL, `org/repo#<n>`, or `#<n>`, add a dedicated issue reference line to the PR body.
-  - Use a closing keyword such as `Closes #<n>` only when merging this PR to the base branch represents terminal delivery for that issue. This is true when the target branch is the repository default branch or the configured production branch from `.lisa.config.json` `deploy.branches.production`.
-  - If the target branch is a non-terminal environment branch such as `dev` or `staging`, use a non-closing reference such as `Refs #<n>` so GitHub links the PR in the issue's Development / linked pull requests surface without prematurely closing the issue.
-  - For cross-repo issue refs, use the fully qualified form, for example `Closes CodySwannGT/lisa#614` or `Refs CodySwannGT/lisa#614`.
-- **Linear**:
-  - Ensure the Linear issue identifier appears in the branch name when the branch is created upstream by `lisa:implement`.
-  - Include the identifier in the PR title or body, for example `Linear: ENG-123`, so Linear's GitHub integration can attach the PR.
-- **JIRA**:
-  - Ensure the JIRA issue key appears in the branch name when the branch is created upstream by `lisa:implement`.
-  - Include the key in the PR title or body, for example `JIRA: PROJ-456`, so the GitHub-JIRA integration can attach the PR.
-- **No supported provider**: Skip this section without error; do not invent references.
-
-When updating an existing PR, preserve any existing linkage line unless the new `work_item_ref` is more specific. Do not duplicate equivalent references.
-
-### Work Item Backlink
-
-After creating or updating the PR, always make the reverse link durable on the source work item when `work_item_ref` is available:
-
-1. Resolve the live PR URL with `gh pr view <pr-number> --json url --jq .url`.
-2. Invoke `lisa:tracker-sync` with the original work item ref, milestone `pr-ready`, `pr_url=<url>`, and `tracker_provider=<provider>` when known.
-3. The vendor sync skill must prefer the provider's native development-link primitive where one is available and verifiable.
-4. If native linkage is unavailable, unconfigured, or cannot be verified, the vendor sync skill must create or update a single managed `[lisa-pr-link]` comment on the work item containing the PR URL. The fallback comment is not optional; it is the ticket-side half of the two-way link.
-5. When the PR later merges, invoke `lisa:tracker-sync` again with milestone `pr-merged`, the same `pr_url`, and the merge SHA when available, so the managed backlink reflects the final state.
-
-Do not report PR submission as fully synced while the PR body references the ticket but the ticket has neither a verified native PR link nor the managed backlink comment.
-
-### GitHub ProjectV2 Coordination
-
-After PR creation or update, resolve the live Pull Request node id:
-
-```bash
-gh pr view <pr-number> --json id,url --jq '{ id, url }'
-```
-
-When `github.projects.v2` is enabled, delegate membership to `lisa:github-project-v2`:
-
-```text
-operation: ensure-item
-content_node_id: <pull-request-node-id>
-```
-
-Branch on the shared utility outcome exactly as GitHub Issue writers do:
-
-- `outcome: disabled` — no Project configured; continue normally.
-- `outcome: added` or `outcome: reused` — PR membership is now present; continue normally.
-- `outcome: warning` with `required: false` — preserve the exact Project error, keep the underlying PR creation/update as the durable success, and continue the normal auto-merge/watch flow.
-- `outcome: blocked` with `required: true` — surface the exact Project failure and treat the submit flow as blocked even if the PR already exists, so operators can fix Project access/config before reporting full success.
-
-Never inline separate `gh api graphql` ProjectV2 mutations here. All Pull Request membership coordination goes through `lisa:github-project-v2` so linked-PR flows and Issue writers stay in parity.
-
-### PR Description Format
-
-Include in the PR description:
-
-- **Summary**: Brief overview of changes (1-3 bullet points)
-- **Test plan**: How to verify the changes work correctly
-- **Issue / Tracker link**: The provider-specific native linkage line when a source work item is available, placed after the summary and before the test plan.
-
-### Never
-
-- use `--force` push without explicit user request
-- create PR from protected branches (dev, staging, main)
-- skip pushing before PR creation
-
-## Execute
-
-Execute the workflow now.