@codyswann/lisa 2.232.0 → 2.233.0

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

@@ -0,0 +1,69 @@
+---
+name: lisa-qa-queue
+description: "QA acceptance queue for human testers. Serves the next ticket awaiting QA verdict from the configured QA queue status as a plain-language acceptance brief — what the ticket promises, how to exercise it on the QA environment, in words a non-technical tester can follow. On 'pass', transitions the ticket to the configured certified status. On 'fail', delegates to lisa-qa-fail for the structured failure report, expectation-gap diagnosis, and return to the build-ready status. The conversational front door for human QA acceptance on any coding agent: testers say 'what's the next item?' / 'pass' / 'fail — here's what I saw'."
+allowed-tools: ["Skill", "Bash", "Read", "Glob", "Grep"]
+---
+
+# QA Queue: $ARGUMENTS
+
+Serve one ticket at a time to a human QA tester and record their verdict. The tester is
+assumed **non-technical**: everything you present must be readable by an intern on their
+first day — no stack traces, no jargon, no internal identifiers without explanation.
+
+## Config resolution
+
+Read `.lisa.config.json`:
+
+- **QA queue status** — `jira.workflow.qa.queue`, falling back to `jira.workflow.done.staging`
+  (whatever status the project uses for "deployed to the environment QA tests against").
+  If neither exists, stop and report the missing config.
+- **Certified status** — `jira.workflow.qa.certified` (the project's "passed QA, ships
+  with the next release" status). Required for the pass path; if missing, stop and
+  instruct the operator to add it — never guess a terminal status.
+- **Build-ready status** — `jira.workflow.ready` (fail path, via `lisa-qa-fail`).
+- **Tracker dispatch** — as everywhere: `tracker` decides JIRA / GitHub / Linear surfaces;
+  status names above map to labels/states on non-JIRA trackers.
+
+## Serving the next item
+
+1. Query the QA queue: tickets in the queue status, oldest first, excluding tickets
+   already carrying an unresolved `[lisa-qa-fail]` verdict from this sweep. Skip tickets
+   whose repo is listed in `qa.nonUserFacingRepos` — those belong to `lisa-qa-clear`,
+   not a human tester; note any encountered so the operator knows to run the clear.
+2. Fetch the full context bundle via `lisa-tracker-read` (never serve from a bare summary).
+3. Present ONE ticket as an **acceptance brief**:
+   - **What changed, in user terms** — one or two sentences, translated from the ticket's
+     stakeholder section.
+   - **How to try it** — concrete steps on the QA environment (the `exploration` /
+     Validation Journey config supplies the URL and test credentials): where to go, what
+     to click or type, which account to use.
+   - **What success looks like** — each acceptance criterion rewritten as an observable
+     check ("you should see …"), numbered so the tester can cite one on failure.
+   - **Worth poking at** — up to three edge probes drawn from the ticket's edge-case
+     triage findings, phrased as actions ("try it with an empty search box").
+4. End with: "Say **pass**, or describe what you saw if it failed."
+
+## Recording the verdict
+
+- **Pass** — transition the ticket to the certified status via the tracker access layer,
+  post a brief `[lisa-qa-queue] QA pass` comment naming who verified and when, and offer
+  the next item.
+- **Fail** — invoke `lisa-qa-fail` with the ticket key and the tester's own words
+  (verbatim — do not paraphrase away detail; attach any screenshots they provided). That
+  skill owns the failure report, the expectation-gap diagnosis, the `qa-fail` label, and
+  the transition back to build-ready. When it completes, confirm to the tester in one
+  plain sentence what was recorded and offer the next item.
+- **Unclear / can't test** — if the tester cannot exercise the ticket (missing access,
+  feature flag off, no test data), do NOT guess a verdict. Post a
+  `[lisa-qa-queue] QA blocked: <reason>` comment, leave the status untouched, flag it in
+  the session summary for the operator, and serve the next item.
+
+## Rules
+
+- One ticket at a time — never dump the queue on the tester.
+- The tester's verbatim description is evidence; preserve it exactly in whatever is posted.
+- Never transition to certified without an explicit "pass" from the tester.
+- All tracker writes go through the access layer / `lisa-qa-fail` — this skill never
+  hand-crafts tracker mutations beyond the pass transition and its comment.
+- Session summary on request ("how did we do?"): counts of passed / failed / blocked /
+  remaining in queue.

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

@@ -24,9 +24,9 @@ If none confirm, output `## Verdict: NOT_REWORK` and stop — this skill takes n
 first-attempt work.
 
 1. **Status history shows a post-implementation regression transition.** The ticket's
-   changelog contains a transition from a post-build state (the configured `claimed`, any
-   `done.*` environment state — e.g. `On Dev`, `On Stg` — or a review state) back to the
-   configured `ready` state.
+   changelog contains a transition from a post-build state (the configured `claimed`,
+   any configured `done.*` environment state, or a review state) back to the configured
+   `ready` state.
    - JIRA: fetch the changelog via the `lisa-atlassian-access` REST substrate —
      `GET /rest/api/3/issue/<KEY>/changelog` — and scan `items[].field == "status"` entries.
    - GitHub: `gh issue view <n> --json timelineItems` (or the timeline API) — scan for the

package/plugins/lisa-expo/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Expo/React Native-specific skills, agents, rules, and MCP servers",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-harper-fabric-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Harper/Fabric-specific rules for TypeScript component apps",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "NestJS-specific skills and migration write-protection hooks.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "NestJS-specific skills (GraphQL, TypeORM) and hooks (migration write-protection)",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-openclaw-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Connect staff roles to Telegram or Slack via OpenClaw — facilitator/specialist hub-and-spoke routing and repo-coding topics, for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-phaser-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-phaser",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Phaser 4 game-development rules for TypeScript projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Ruby on Rails-specific skills and hooks for RuboCop and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "TypeScript-specific hooks for formatting, linting, and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-typescript-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-typescript",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "TypeScript-specific hooks — Prettier formatting, ESLint linting, ast-grep scanning, and error-suppression blocking on edit",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "Distributable LLM Wiki kernel — ingest, query, lint, and maintain a git-native markdown knowledge base across Claude and Codex.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-copilot/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-wiki-cursor/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa-wiki",
-  "version": "2.232.0",
+  "version": "2.233.0",
   "description": "LLM Wiki — a distributable, git-native markdown knowledge base for Claude Code and Codex",
   "author": {
     "name": "Cody Swann"

package/plugins/src/base/commands/qa-checklist.md

@@ -0,0 +1,6 @@
+---
+description: "Serve the current manual regression checklist: curated journeys minus live automated E2E coverage, in plain language."
+argument-hint: ""
+---
+
+Use the /lisa-qa-checklist skill to serve the manual regression checklist. $ARGUMENTS

package/plugins/src/base/commands/qa-clear.md

@@ -0,0 +1,6 @@
+---
+description: "Bulk-move QA-queue tickets scoped entirely to non-user-facing repos to the configured certified status, with an auditable moved-list report."
+argument-hint: ""
+---
+
+Use the /lisa-qa-clear skill to clear non-human-verifiable tickets from the QA queue. $ARGUMENTS

package/plugins/src/base/commands/qa-fail.md

@@ -0,0 +1,6 @@
+---
+description: "File a QA failure: find the right ticket (never a duplicate), write the structured failure report, diagnose the expectation gap, label qa-fail, and return the ticket to build-ready."
+argument-hint: "[ticket-key] <what you saw, in your own words>"
+---
+
+Use the /lisa-qa-fail skill to file this QA failure. $ARGUMENTS

package/plugins/src/base/commands/qa-queue.md

@@ -0,0 +1,6 @@
+---
+description: "Serve the next ticket awaiting QA verdict as a plain-language acceptance brief; record pass (→ certified) or fail (→ structured report via lisa-qa-fail)."
+argument-hint: "[pass | fail <description> | next]"
+---
+
+Use the /lisa-qa-queue skill to serve the QA acceptance queue. $ARGUMENTS

package/plugins/src/base/skills/lisa-qa-checklist/SKILL.md

@@ -0,0 +1,70 @@
+---
+name: lisa-qa-checklist
+description: "Serve the current manual regression checklist to a human QA tester. Reads the project's curated journey list, cross-references it against what the automated suites (Playwright web E2E, Maestro native E2E) actually cover by scanning the spec files, and serves only the journeys that still need human eyes — each as plain-language steps. Keeps a single source of truth so testers never work from a stale personal copy, and shrinks automatically as automated coverage grows."
+allowed-tools: ["Bash", "Read", "Glob", "Grep", "Write", "Edit"]
+---
+
+# QA Checklist: $ARGUMENTS
+
+The manual regression sweep exists to catch what automation does not. Its checklist must
+therefore be computed, not remembered: curated journeys minus automated coverage, at the
+moment the tester asks.
+
+## Sources
+
+1. **Curated journey list** — `qa.checklistFile` in `.lisa.config.json`, default
+   `.lisa/qa-checklist.md`. Format: one `## Journey: <name>` section per user journey,
+   with plain-language steps and an optional `automation:` line naming the covering spec
+   file(s) once one exists. If the file does not exist, offer to bootstrap it: derive
+   candidate journeys from the app's route map and the existing E2E suites' describe
+   blocks, write the draft, and ask the operator to curate it once. Never invent
+   journeys silently.
+2. **Automated coverage** — scan the repo's E2E suites (Playwright specs, Maestro flows;
+   locate via the project's e2e/test directories). An `automation:` line must name BOTH
+   the spec file and the specific test within it (the Playwright `describe`/`test` title
+   or Maestro flow name): `automation: <spec-path> :: <test-or-flow-name>`. A journey
+   counts as covered only when that spec file exists, the named test/flow is present in
+   it, and it is not skipped (`test.skip`, commented-out flow, or excluded from CI). A
+   file-only line, a named test that no longer matches, or any ambiguous mapping is
+   treated as **uncovered** — a live filename proves nothing about what the spec
+   exercises. A deleted, renamed, or skipped test silently un-covers its journey — the
+   very regression this check exists to catch; call it out loudly.
+
+## Serving the sweep
+
+Present two lists, human-first:
+
+```text
+## Manual sweep — <n> journeys need your eyes
+1. <Journey name> — <plain-language steps>
+   Why manual: <no automation | automation skipped/stale: <spec>>
+...
+
+## Covered by automation — <n> journeys (skim, don't re-test)
+- <Journey name> — <spec file> (<playwright|maestro>)
+```
+
+Rules for the served text: steps an intern can follow, no spec-file jargon in the manual
+section beyond the "why manual" line, and stable journey ordering (file order) so testers
+can resume mid-sweep.
+
+## Maintaining the list
+
+- Tester or operator adds/edits journeys in plain language → edit the checklist file
+  (this skill may apply the edit on request; it is a repo file, so changes ride normal
+  review).
+- When a journey gains automation (e.g. `lisa-codify-verification` lands a spec), add its
+  `automation: <spec-path> :: <test-or-flow-name>` line — on request this skill locates
+  the covering spec and test, confirms the named test actually drives the journey's
+  steps, and writes the line itself.
+- Never maintain per-tester copies; the file is the single source of truth and the
+  computed view is always derived fresh.
+
+## Rules
+
+- Coverage claims must point at an existing, non-skipped spec — "there's a test somewhere"
+  does not count.
+- Serving is read-only by default; file edits happen only on explicit request.
+- If the automated-coverage scan finds specs exercising a journey that is missing from
+  the curated list entirely, surface it as a suggested addition — the human curates, the
+  skill proposes.