@codyswann/lisa 2.38.0 → 2.39.1

package/plugins/lisa/skills/linear-write-issue/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "linear-write-issue"
-short_description: "Creates or updates a Linear work item — Project (Epic), Issue (Story), or sub-Issue (Sub-task) — following organizational best practices. Polymorphic: dispatches internally on issue_type to save_project (Epic) or save_issue (Story / Sub-task). Enforces description quality (three audiences), Gherkin acceptance criteria, project-as-parent for Stories, parentId for Sub-tasks, explicit relationship discovery (blocks / is blocked by / relates to / duplicates), labels, components-as-labels, project milestones for fix versions, native priority and estimate fields, and Validation Journey. Rejects thin items — use this skill any time a Linear work item is created or significantly edited."
+display_name: "Linear Write Issue"
+short_description: "Creates or updates a Linear work item — Project (Epic), Issue (Story), or sub-Issue (Sub-task) — following organizational best practices"
 default_prompt:
-  - "Use $linear-write-issue"
+  - "Use $linear-write-issue: Creates or updates a Linear work item — Project (Epic), Issue (Story), or sub-Issue (Sub-task) — following organizational best practices."

package/plugins/lisa/skills/lisa-review-implementation/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "lisa-review-implementation"
-short_description: "This skill should be used when comparing a project's Lisa-managed files against Lisa's source templates to identify drift. It reads the project manifest, locates source templates, generates diffs for drifted files, and offers to upstream improvements back to Lisa."
+display_name: "Lisa Review Implementation"
+short_description: "comparing a project's Lisa-managed files against Lisa's source templates to identify drift"
 default_prompt:
-  - "Use $lisa-review-implementation"
+  - "Use $lisa-review-implementation: comparing a project's Lisa-managed files against Lisa's source templates to identify drift."

package/plugins/lisa/skills/monitor/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "monitor"
-short_description: "Monitor application health across environments. Checks health endpoints, recent logs (CloudWatch / Sentry / browser console), error-rate spikes, performance hotspots, pending migrations, and runs Playwright smoke flows when relevant. Routes to the stack-specific ops-specialist agent (Expo, Rails, etc.). Also invoked as the post-deploy step of the lisa:verify skill."
+display_name: "Monitor"
+short_description: "Monitor application health across environments"
 default_prompt:
-  - "Use $monitor"
+  - "Use $monitor: Monitor application health across environments."

package/plugins/lisa/skills/nightly-add-test-coverage/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "nightly-add-test-coverage"
-short_description: "Nightly direct-execution skill for increasing test coverage. Receives pre-computed threshold data, writes tests targeting coverage gaps, updates thresholds, commits, and creates a PR."
+display_name: "Nightly Add Test Coverage"
+short_description: "Nightly direct-execution skill for increasing test coverage"
 default_prompt:
-  - "Use $nightly-add-test-coverage"
+  - "Use $nightly-add-test-coverage: Nightly direct-execution skill for increasing test coverage."

package/plugins/lisa/skills/nightly-improve-tests/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "nightly-improve-tests"
-short_description: "Nightly direct-execution skill for improving test quality. In nightly mode, focuses on tests for recently changed files. In general mode, scans all tests for the weakest ones. Commits and creates a PR."
+display_name: "Nightly Improve Tests"
+short_description: "Nightly direct-execution skill for improving test quality"
 default_prompt:
-  - "Use $nightly-improve-tests"
+  - "Use $nightly-improve-tests: Nightly direct-execution skill for improving test quality."

package/plugins/lisa/skills/nightly-lower-code-complexity/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "nightly-lower-code-complexity"
-short_description: "Nightly direct-execution skill for reducing code complexity thresholds. Receives pre-computed threshold data, refactors violations, updates thresholds, commits, and creates a PR."
+display_name: "Nightly Lower Code Complexity"
+short_description: "Nightly direct-execution skill for reducing code complexity thresholds"
 default_prompt:
-  - "Use $nightly-lower-code-complexity"
+  - "Use $nightly-lower-code-complexity: Nightly direct-execution skill for reducing code complexity thresholds."

package/plugins/lisa/skills/notion-access/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "notion-access"
-short_description: "Vendor-neutral access layer for Notion. Every notion-* skill MUST delegate through this skill rather than invoking the Notion REST API or any Notion MCP directly. Resolves a substrate per operation in this order: (1) Notion MCP if authenticated and the configured prdDatabaseId is fetchable through it (identity-match), (2) curl + Bearer auth + internal-integration token. Verifies the active connection matches `.lisa.config.json` before every operation — substrates authenticated as a different Notion workspace are skipped, not used."
+display_name: "Notion Access"
+short_description: "Vendor-neutral access layer for Notion"
 default_prompt:
-  - "Use $notion-access"
+  - "Use $notion-access: Vendor-neutral access layer for Notion."

package/plugins/lisa/skills/notion-prd-intake/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "notion-prd-intake"
-short_description: "Scans a Notion PRD database for pages in the configured `ready` status and runs each one through the dry-run validation pipeline. PRDs that pass every gate get tickets written and the status flipped to the configured `ticketed` value; PRDs that fail get clarifying-question comments and the status flipped to the configured `blocked` value. The skill is the runtime for the ready → in_review → blocked|ticketed lifecycle. Composes existing skills (notion-to-tracker, tracker-validate, tracker-source-artifacts, product-walkthrough); does not reimplement their logic."
+display_name: "Notion PRD Intake"
+short_description: "Scans a Notion PRD database for pages in the configured `ready` status and runs each one through the dry-run validation pipeline"
 default_prompt:
-  - "Use $notion-prd-intake"
+  - "Use $notion-prd-intake: Scans a Notion PRD database for pages in the configured `ready` status and runs each one through the dry-run validation pipeline."

package/plugins/lisa/skills/notion-to-tracker/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "notion-to-tracker"
+display_name: "Notion To Tracker"
 short_description: ">"
 default_prompt:
-  - "Use $notion-to-tracker"
+  - "Use $notion-to-tracker: >."

package/plugins/lisa/skills/performance-review/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "performance-review"
-short_description: "Performance review methodology. N+1 queries, inefficient algorithms, memory leaks, missing indexes, unnecessary re-renders, bundle size issues. Evidence-based recommendations."
+display_name: "Performance Review"
+short_description: "Performance review methodology"
 default_prompt:
-  - "Use $performance-review"
+  - "Use $performance-review: Performance review methodology."

package/plugins/lisa/skills/plan/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "plan"
-short_description: "Decompose a single PRD or specification into ordered work items in the configured tracker. Vendor-agnostic — the source can be a Notion PRD URL, a Confluence PRD URL, a Linear project URL, a GitHub Issue URL, an existing JIRA epic key, a markdown file, or a free-form description; the destination tracker is whatever the project is configured to use via `.lisa.config.json` `tracker` (JIRA, GitHub Issues, or Linear). Single-PRD mode only — for batch scanning of all Ready PRDs in a queue, use the lisa:intake skill."
+display_name: "Plan"
+short_description: "Decompose a single PRD or specification into ordered work items in the configured tracker"
 default_prompt:
-  - "Use $plan"
+  - "Use $plan: Decompose a single PRD or specification into ordered work items in the configured tracker."

package/plugins/lisa/skills/prd-backlink/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "prd-backlink"
-short_description: "Update a source PRD with a `## Tickets` section linking back to every work item created from it. Vendor-aware on the source side (Notion / Confluence / Linear / GitHub Issue / file) and tracker-agnostic on the ticket side. Idempotent — regenerates the section on each run rather than appending, so re-planning never accumulates stale links. Invoked by the *-to-tracker skills at the end of their pipeline and standalone if a PRD's Tickets section needs to be refreshed."
+display_name: "PRD Backlink"
+short_description: "Update a source PRD with a `## Tickets` section linking back to every work item created from it"
 default_prompt:
-  - "Use $prd-backlink"
+  - "Use $prd-backlink: Update a source PRD with a `## Tickets` section linking back to every work item created from it."

package/plugins/lisa/skills/prd-ticket-coverage/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "prd-ticket-coverage"
-short_description: "Verifies that every requirement in a PRD (Notion, Confluence, Linear, or GitHub Issues) is covered by at least one created destination ticket (JIRA, GitHub Issues, or Linear) — no silent drops. Parses the PRD into atomic items (goals, user stories, functional/non-functional requirements, acceptance criteria, important notes), maps each to the created tickets, and produces a coverage matrix and verdict (COMPLETE / COMPLETE_WITH_SCOPE_CREEP / GAPS_FOUND / NO_TICKETS_FOUND). Used by notion-prd-intake / confluence-prd-intake / linear-prd-intake / github-prd-intake post-write to gate the Ticketed transition; can also be invoked standalone for after-the-fact audits."
+display_name: "PRD Ticket Coverage"
+short_description: "Verifies that every requirement in a PRD (Notion, Confluence, Linear, or GitHub Issues) is covered by at least one created destination…"
 default_prompt:
-  - "Use $prd-ticket-coverage"
+  - "Use $prd-ticket-coverage: Verifies that every requirement in a PRD (Notion, Confluence, Linear, or GitHub Issues) is covered by at least one created destination…."

package/plugins/lisa/skills/product-walkthrough/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "product-walkthrough"
-short_description: "Methodology for evaluating the live product via a real browser (Playwright MCP) when planning work or evaluating a PRD. Reading a PRD or a mock without seeing the current product produces tickets that misjudge the change — this skill grounds the analysis in what actually exists today. Invoke this skill from notion-to-tracker (Phase 2b live-product walkthrough), jira-create, and any PRD intake flow whose work touches existing user-facing surfaces."
+display_name: "Product Walkthrough"
+short_description: "Methodology for evaluating the live product via a real browser (Playwright MCP) when planning work or evaluating a PRD"
 default_prompt:
-  - "Use $product-walkthrough"
+  - "Use $product-walkthrough: Methodology for evaluating the live product via a real browser (Playwright MCP) when planning work or evaluating a PRD."

package/plugins/lisa/skills/pull-request-review/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "pull-request-review"
-short_description: "This skill should be used when checking for code review comments on a pull request and implementing them if required. It fetches PR metadata and comments, generates a brief from unresolved feedback, and bootstraps a project to address the review comments."
+display_name: "Pull Request Review"
+short_description: "checking for code review comments on a pull request and implementing them if required"
 default_prompt:
-  - "Use $pull-request-review"
+  - "Use $pull-request-review: checking for code review comments on a pull request and implementing them if required."

package/plugins/lisa/skills/quality-review/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "quality-review"
-short_description: "Code quality review checklist. Correctness, coding philosophy compliance, test coverage, documentation quality. Findings ranked by severity in plain English."
+display_name: "Quality Review"
+short_description: "Code quality review checklist"
 default_prompt:
-  - "Use $quality-review"
+  - "Use $quality-review: Code quality review checklist."

package/plugins/lisa/skills/reproduce-bug/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "reproduce-bug"
-short_description: "How to create reliable bug reproduction scenarios. Covers failing tests, minimal scripts, environment verification, and reproduction evidence capture."
+display_name: "Reproduce Bug"
+short_description: "How to create reliable bug reproduction scenarios"
 default_prompt:
-  - "Use $reproduce-bug"
+  - "Use $reproduce-bug: How to create reliable bug reproduction scenarios."

package/plugins/lisa/skills/research/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "research"
-short_description: "Research a problem space and produce a PRD. Investigates the codebase, defines user flows, assesses technical feasibility, and outputs a specification ready to hand to the Plan flow. Vendor-agnostic — the resulting PRD lands wherever the configured destination is (Notion, Confluence, file, etc.)."
+display_name: "Research"
+short_description: "Research a problem space and produce a PRD"
 default_prompt:
-  - "Use $research"
+  - "Use $research: Research a problem space and produce a PRD."

package/plugins/lisa/skills/review-local/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "review-local"
-short_description: "This skill should be used when performing a code review on local changes on the current branch compared to the main branch. It uses multiple parallel agents to check for bugs, CLAUDE.md compliance, git history context, previous PR comments, and code comment adherence, then scores and filters findings by confidence level."
+display_name: "Review Local"
+short_description: "performing a code review on local changes on the current branch compared to the main branch"
 default_prompt:
-  - "Use $review-local"
+  - "Use $review-local: performing a code review on local changes on the current branch compared to the main branch."

package/plugins/lisa/skills/root-cause-analysis/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "root-cause-analysis"
-short_description: "Root cause analysis methodology. Evidence gathering from logs, execution path tracing, strategic log placement, and building irrefutable proof chains."
+display_name: "Root Cause Analysis"
+short_description: "Root cause analysis methodology"
 default_prompt:
-  - "Use $root-cause-analysis"
+  - "Use $root-cause-analysis: Root cause analysis methodology."

package/plugins/lisa/skills/security-review/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "security-review"
-short_description: "Security review methodology. STRIDE threat modeling, OWASP Top 10 vulnerability checks, auth/validation/secrets handling review, and mitigation recommendations."
+display_name: "Security Review"
+short_description: "Security review methodology"
 default_prompt:
-  - "Use $security-review"
+  - "Use $security-review: Security review methodology."

package/plugins/lisa/skills/security-zap-scan/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "security-zap-scan"
-short_description: "Run an OWASP ZAP baseline security scan locally using Docker. Checks for the ZAP baseline script, executes the scan, and summarizes findings by risk level with remediation recommendations."
+display_name: "Security ZAP Scan"
+short_description: "Run an OWASP ZAP baseline security scan locally using Docker"
 default_prompt:
-  - "Use $security-zap-scan"
+  - "Use $security-zap-scan: Run an OWASP ZAP baseline security scan locally using Docker."

package/plugins/lisa/skills/setup-atlassian/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "setup-atlassian"
-short_description: "Configure Atlassian access for this project. Installs acli if missing, runs the OAuth or API-token login, optionally enables the Atlassian MCP, resolves the cloudId for the active site, and writes the `atlassian` section into `.lisa.config.json`. Prerequisite for /lisa:setup:jira and /lisa:setup:confluence (both need atlassian.cloudId). Idempotent — re-running updates the existing section rather than duplicating it."
+display_name: "Setup Atlassian"
+short_description: "Configure Atlassian access for this project"
 default_prompt:
-  - "Use $setup-atlassian"
+  - "Use $setup-atlassian: Configure Atlassian access for this project."

package/plugins/lisa/skills/setup-confluence/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "setup-confluence"
-short_description: "Configure Confluence as the PRD source for this project. Writes `confluence.spaceKey` and/or `confluence.parentPageId` into `.lisa.config.json` and offers to set top-level `source: \\\"confluence\\\"`. Depends on /lisa:setup:atlassian — atlassian.cloudId must already be present. Idempotent."
+display_name: "Setup Confluence"
+short_description: "Configure Confluence as the PRD source for this project"
 default_prompt:
-  - "Use $setup-confluence"
+  - "Use $setup-confluence: Configure Confluence as the PRD source for this project."

package/plugins/lisa/skills/setup-github/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "setup-github"
-short_description: "Configure GitHub Issues as the destination tracker and/or the PRD source for this project. Verifies the gh CLI is installed and authenticated, resolves `org/repo`, scaffolds the build-queue label namespace (`status:*`) when GitHub is the tracker and/or the PRD-lifecycle label namespace (`prd-*` + sentinel) when GitHub is the PRD source, writes the `github` section into `.lisa.config.json`, and offers to set top-level `tracker: \\\"github\\\"` and/or `source: \\\"github\\\"`. Idempotent — re-running updates the existing section and reuses existing labels rather than duplicating. No /lisa:setup:atlassian prerequisite (GitHub auth is standalone)."
+display_name: "Setup Github"
+short_description: "Configure GitHub Issues as the destination tracker and/or the PRD source for this project"
 default_prompt:
-  - "Use $setup-github"
+  - "Use $setup-github: Configure GitHub Issues as the destination tracker and/or the PRD source for this project."

package/plugins/lisa/skills/setup-jira/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "setup-jira"
-short_description: "Configure JIRA as the destination tracker for this project. Writes `jira.project` into `.lisa.config.json` and offers to set top-level `tracker: \\\"jira\\\"`. Depends on /lisa:setup:atlassian — atlassian.cloudId must already be present, otherwise this skill stops and instructs the user to run setup-atlassian first. Idempotent."
+display_name: "Setup Jira"
+short_description: "Configure JIRA as the destination tracker for this project"
 default_prompt:
-  - "Use $setup-jira"
+  - "Use $setup-jira: Configure JIRA as the destination tracker for this project."

package/plugins/lisa/skills/setup-linear/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "setup-linear"
-short_description: "Configure Linear as the destination tracker and/or the PRD source for this project. Verifies Linear access (MCP OAuth or a personal API key in OS keychain), resolves the workspace slug and team key, scaffolds the build-queue issue-label namespace (`status:*`) when Linear is the tracker and/or the PRD-lifecycle project-label namespace (`prd-*` + issue-level sentinel) when Linear is the PRD source, writes the `linear` section into `.lisa.config.json`, and offers to set top-level `tracker: \\\"linear\\\"` and/or `source: \\\"linear\\\"`. Idempotent — re-running updates the existing section and reuses existing labels. No /lisa:setup:atlassian prerequisite."
+display_name: "Setup Linear"
+short_description: "Configure Linear as the destination tracker and/or the PRD source for this project"
 default_prompt:
-  - "Use $setup-linear"
+  - "Use $setup-linear: Configure Linear as the destination tracker and/or the PRD source for this project."

package/plugins/lisa/skills/setup-notion/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "setup-notion"
-short_description: "Configure Notion as the PRD source for this project. Walks the user through creating an internal integration in the target workspace, sharing the PRD database with it, stores the resulting `ntn_*` token in OS keychain (multi-workspace-safe — keyed by workspaceId), validates against the Notion API, and writes `notion.workspaceId`, `notion.prdDatabaseId`, and `notion.values` into `.lisa.config.json`. Idempotent — re-runs update the existing section rather than duplicating it. Offers to set top-level `source: \\\"notion\\\"`."
+display_name: "Setup Notion"
+short_description: "Configure Notion as the PRD source for this project"
 default_prompt:
-  - "Use $setup-notion"
+  - "Use $setup-notion: Configure Notion as the PRD source for this project."

package/plugins/lisa/skills/spec-conformance/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "spec-conformance"
-short_description: "Verifies that shipped work matches its spec section-by-section — acceptance criteria, Out of Scope, Technical Approach, Validation Journey assertions, and any explicit deliverables. Builds a coverage matrix mapping each requirement to evidence, flags scope creep separately from misses, and produces a verdict (CONFORMS / PARTIAL / DIVERGES). Runs during the verification phase alongside empirical system verification."
+display_name: "Spec Conformance"
+short_description: "Verifies that shipped work matches its spec section-by-section — acceptance criteria, Out of Scope, Technical Approach, Validation Journey…"
 default_prompt:
-  - "Use $spec-conformance"
+  - "Use $spec-conformance: Verifies that shipped work matches its spec section-by-section — acceptance criteria, Out of Scope, Technical Approach, Validation Journey…."

package/plugins/lisa/skills/task-decomposition/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "task-decomposition"
-short_description: "Methodology for breaking work into ordered tasks. Each task gets a single-repo scope, acceptance criteria, verification type, dependencies, and skills required."
+display_name: "Task Decomposition"
+short_description: "Methodology for breaking work into ordered tasks"
 default_prompt:
-  - "Use $task-decomposition"
+  - "Use $task-decomposition: Methodology for breaking work into ordered tasks."

package/plugins/lisa/skills/task-triage/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "task-triage"
-short_description: "8-step task triage and implementation workflow. Ensures tasks have clear requirements, dependencies, and verification plans before implementation begins."
+display_name: "Task Triage"
+short_description: "8-step task triage and implementation workflow"
 default_prompt:
-  - "Use $task-triage"
+  - "Use $task-triage: 8-step task triage and implementation workflow."

package/plugins/lisa/skills/tdd-implementation/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "tdd-implementation"
-short_description: "Test-Driven Development implementation workflow. RED: write failing test, GREEN: minimum code to pass, REFACTOR: clean up. Includes task metadata requirements, verification, and atomic commit practices."
+display_name: "TDD Implementation"
+short_description: "Test-Driven Development implementation workflow"
 default_prompt:
-  - "Use $tdd-implementation"
+  - "Use $tdd-implementation: Test-Driven Development implementation workflow."

package/plugins/lisa/skills/test-strategy/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "test-strategy"
-short_description: "Test strategy design. Coverage matrix, edge cases, TDD sequence planning, test quality review. Behavior-focused testing over implementation details."
+display_name: "Test Strategy"
+short_description: "Test strategy design"
 default_prompt:
-  - "Use $test-strategy"
+  - "Use $test-strategy: Test strategy design."

package/plugins/lisa/skills/ticket-triage/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "ticket-triage"
-short_description: "Analytical triage gate for tickets in the configured destination tracker (JIRA, GitHub Issues, or Linear). Detects requirement ambiguities, identifies edge cases from codebase analysis, and plans verification methodology. Posts findings to the ticket and produces a verdict (BLOCKED/PASSED_WITH_FINDINGS/PASSED) that gates whether implementation can proceed. Vendor-neutral: the caller (jira-agent or github-agent) is responsible for fetching the ticket via lisa:tracker-read, running the pre-flight gate via lisa:tracker-verify, and posting findings via the matching vendor comment tool."
+display_name: "Ticket Triage"
+short_description: "Analytical triage gate for tickets in the configured destination tracker (JIRA, GitHub Issues, or Linear)"
 default_prompt:
-  - "Use $ticket-triage"
+  - "Use $ticket-triage: Analytical triage gate for tickets in the configured destination tracker (JIRA, GitHub Issues, or Linear)."

package/plugins/lisa/skills/tracker-add-journey/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "tracker-add-journey"
-short_description: "Vendor-neutral wrapper for appending a Validation Journey section to an existing ticket/issue. Reads `tracker` from .lisa.config.json (default: jira) and dispatches to lisa:jira-add-journey, lisa:github-add-journey, or lisa:linear-add-journey."
+display_name: "Tracker Add Journey"
+short_description: "Vendor-neutral wrapper for appending a Validation Journey section to an existing ticket/issue"
 default_prompt:
-  - "Use $tracker-add-journey"
+  - "Use $tracker-add-journey: Vendor-neutral wrapper for appending a Validation Journey section to an existing ticket/issue."

package/plugins/lisa/skills/tracker-build-intake/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "tracker-build-intake"
-short_description: "Vendor-neutral wrapper for the build-queue batch scanner. Reads `tracker` from .lisa.config.json (default: jira) and dispatches to lisa:jira-build-intake (JQL/project-key queue), lisa:github-build-intake (GitHub repo queue keyed off the `status:ready` label), or lisa:linear-build-intake (Linear team queue keyed off the `status:ready` label). Every vendor scanner enforces the claim-time arm of the `leaf-only-lifecycle` rule — claim leaf work units only; skip or safe-block a container with open child work (or a childless Epic/Story/Spike) that carries a stale build-ready role. Counterpart to lisa:intake's PRD-side dispatchers."
+display_name: "Tracker Build Intake"
+short_description: "Vendor-neutral wrapper for the build-queue batch scanner"
 default_prompt:
-  - "Use $tracker-build-intake"
+  - "Use $tracker-build-intake: Vendor-neutral wrapper for the build-queue batch scanner."

package/plugins/lisa/skills/tracker-create/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "tracker-create"
-short_description: "Vendor-neutral wrapper for creating tickets/issues from code files or descriptions. Reads `tracker` from .lisa.config.json (default: jira) and dispatches to lisa:jira-create, lisa:github-create, or lisa:linear-create. Plans hierarchy structure (epic / story / sub-task), then delegates each individual write through the tracker-write shim."
+display_name: "Tracker Create"
+short_description: "Vendor-neutral wrapper for creating tickets/issues from code files or descriptions"
 default_prompt:
-  - "Use $tracker-create"
+  - "Use $tracker-create: Vendor-neutral wrapper for creating tickets/issues from code files or descriptions."

package/plugins/lisa/skills/tracker-evidence/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "tracker-evidence"
-short_description: "Vendor-neutral wrapper for posting verification evidence. Reads `tracker` from .lisa.config.json (default: jira) and dispatches to lisa:jira-evidence, lisa:github-evidence, or lisa:linear-evidence. Uploads evidence to the GitHub `pr-assets` release, updates the PR description, posts a comment on the originating ticket/issue, and transitions the ticket/issue to its post-build review state."
+display_name: "Tracker Evidence"
+short_description: "Vendor-neutral wrapper for posting verification evidence"
 default_prompt:
-  - "Use $tracker-evidence"
+  - "Use $tracker-evidence: Vendor-neutral wrapper for posting verification evidence."

package/plugins/lisa/skills/tracker-journey/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "tracker-journey"
-short_description: "Vendor-neutral wrapper for executing a ticket/issue's Validation Journey end-to-end. Reads `tracker` from .lisa.config.json (default: jira) and dispatches to lisa:jira-journey, lisa:github-journey, or lisa:linear-journey. Parses the journey, satisfies prerequisites, executes the steps, captures evidence at each marker, and posts results via tracker-evidence."
+display_name: "Tracker Journey"
+short_description: "Vendor-neutral wrapper for executing a ticket/issue's Validation Journey end-to-end"
 default_prompt:
-  - "Use $tracker-journey"
+  - "Use $tracker-journey: Vendor-neutral wrapper for executing a ticket/issue's Validation Journey end-to-end."

package/plugins/lisa/skills/tracker-read/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "tracker-read"
-short_description: "Vendor-neutral wrapper for fetching the full scope of a ticket/issue and its related graph. Reads `tracker` from .lisa.config.json (default: jira) and dispatches to lisa:jira-read-ticket, lisa:github-read-issue, or lisa:linear-read-issue. Returns a consolidated context bundle so downstream agents never act on a single ticket in isolation."
+display_name: "Tracker Read"
+short_description: "Vendor-neutral wrapper for fetching the full scope of a ticket/issue and its related graph"
 default_prompt:
-  - "Use $tracker-read"
+  - "Use $tracker-read: Vendor-neutral wrapper for fetching the full scope of a ticket/issue and its related graph."

package/plugins/lisa/skills/tracker-source-artifacts/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "tracker-source-artifacts"
-short_description: "Canonical, vendor-neutral taxonomy and rules for handling source artifacts (Figma, Lovable, Loom, screenshots, design docs, data samples) when generating or evaluating tracker tickets (JIRA, GitHub Issues, Linear). Defines: (1) artifact domains, (2) classification rules per tool, (3) source precedence (which artifact is authoritative for which question), (4) inheritance from epic to story to sub-task, (5) cross-axis conflict handling. Invoke this skill from any flow that extracts, attaches, or reasons about external design/UX/data artifacts so the rules don't drift across skills."
+display_name: "Tracker Source Artifacts"
+short_description: "Canonical, vendor-neutral taxonomy and rules for handling source artifacts (Figma, Lovable, Loom, screenshots, design docs, data samples)…"
 default_prompt:
-  - "Use $tracker-source-artifacts"
+  - "Use $tracker-source-artifacts: Canonical, vendor-neutral taxonomy and rules for handling source artifacts (Figma, Lovable, Loom, screenshots, design docs, data samples)…."

package/plugins/lisa/skills/tracker-sync/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "tracker-sync"
-short_description: "Vendor-neutral wrapper for posting milestone updates to the linked ticket/issue. Reads `tracker` from .lisa.config.json (default: jira) and dispatches to lisa:jira-sync, lisa:github-sync, or lisa:linear-sync. Posts at: plan created, implementation in progress, PR ready, PR merged. Suggests (never auto-transitions) the next status."
+display_name: "Tracker Sync"
+short_description: "Vendor-neutral wrapper for posting milestone updates to the linked ticket/issue"
 default_prompt:
-  - "Use $tracker-sync"
+  - "Use $tracker-sync: Vendor-neutral wrapper for posting milestone updates to the linked ticket/issue."

package/plugins/lisa/skills/tracker-validate/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "tracker-validate"
-short_description: "Vendor-neutral wrapper for the pre-write quality gate. Reads `tracker` from .lisa.config.json (default: jira) and dispatches to lisa:jira-validate-ticket, lisa:github-validate-issue, or lisa:linear-validate-issue. Read-only — never writes to any tracker. Used by tracker-write Phase 5.5 (pre-write gate), tracker-verify (post-write checks), and the *-to-tracker dry-run paths. Output is structured PASS/FAIL per gate so callers can parse it."
+display_name: "Tracker Validate"
+short_description: "Vendor-neutral wrapper for the pre-write quality gate"
 default_prompt:
-  - "Use $tracker-validate"
+  - "Use $tracker-validate: Vendor-neutral wrapper for the pre-write quality gate."

package/plugins/lisa/skills/tracker-verify/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "tracker-verify"
-short_description: "Vendor-neutral wrapper for the post-write verification gate. Reads `tracker` from .lisa.config.json (default: jira) and dispatches to lisa:jira-verify, lisa:github-verify, or lisa:linear-verify. Fetches the live ticket/issue and runs the validator gates against the stored state — catches anything dropped or reformatted on write. Read-only."
+display_name: "Tracker Verify"
+short_description: "Vendor-neutral wrapper for the post-write verification gate"
 default_prompt:
-  - "Use $tracker-verify"
+  - "Use $tracker-verify: Vendor-neutral wrapper for the post-write verification gate."

package/plugins/lisa/skills/tracker-write/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "tracker-write"
-short_description: "Vendor-neutral wrapper for ticket creation and updates. Reads `tracker` from .lisa.config.json (default: jira) and dispatches to lisa:jira-write-ticket, lisa:github-write-issue, or lisa:linear-write-issue. Callers in vendor-neutral skills (notion-to-tracker, linear-to-tracker, confluence-to-tracker, github-to-tracker, implement, verify) MUST invoke this skill instead of the vendor-specific ones — that is what makes the tracker switchable per project. The Phase-5.5 validate-pre-write gate, post-write verify, and Phase-8 announce-comment behavior live in the vendor skills; this shim is dispatch only."
+display_name: "Tracker Write"
+short_description: "Vendor-neutral wrapper for ticket creation and updates"
 default_prompt:
-  - "Use $tracker-write"
+  - "Use $tracker-write: Vendor-neutral wrapper for ticket creation and updates."

package/plugins/lisa/skills/verification-lifecycle/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "verification-lifecycle"
-short_description: "Verification lifecycle: confirm quality gates, classify types, discover tools, fail fast, plan, execute, codify (turn each passing verification into a regression test), spec conformance (verify shipped work matches the spec), loop. Quality gates (tests/typecheck/lint) are prerequisites, NOT verification. Verification means running the actual system and observing results."
+display_name: "Verification Lifecycle"
+short_description: "Verification lifecycle: confirm quality gates, classify types, discover tools, fail fast, plan, execute, codify (turn each passing…"
 default_prompt:
-  - "Use $verification-lifecycle"
+  - "Use $verification-lifecycle: Verification lifecycle: confirm quality gates, classify types, discover tools, fail fast, plan, execute, codify (turn each passing…."

package/plugins/lisa/skills/verify/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "verify"
-short_description: "Ship and verify code. Commits any pending changes, opens or updates the PR, handles the review loop, merges when green, monitors the deploy, and runs remote verification (health checks, Validation Journey replay, Sentry/log inspection) in the target environment. Folds in the legacy /ship alias."
+display_name: "Verify"
+short_description: "Ship and verify code"
 default_prompt:
-  - "Use $verify"
+  - "Use $verify: Ship and verify code."

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.38.0",
+  "version": "2.39.1",
   "description": "AWS CDK-specific plugin",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.38.0",
+  "version": "2.39.1",
   "description": "AWS CDK-specific Lisa plugin.",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-expo",
-  "version": "2.38.0",
+  "version": "2.39.1",
   "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.38.0",
+  "version": "2.39.1",
   "description": "Expo and React Native-specific skills, agents, rules, and MCP servers.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-expo/skills/apollo-client/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "apollo-client"
-short_description: "This skill should be used when writing or modifying GraphQL operations, hooks, or mutations using Apollo Client 3.10. It enforces best practices for optimistic responses, cache updates, and TypeScript type generation. Use this skill when creating new queries/mutations, reviewing Apollo code, or troubleshooting cache issues."
+display_name: "Apollo Client"
+short_description: "writing or modifying GraphQL operations, hooks, or mutations using Apollo Client 3.10"
 default_prompt:
-  - "Use $apollo-client"
+  - "Use $apollo-client: writing or modifying GraphQL operations, hooks, or mutations using Apollo Client 3.10."

package/plugins/lisa-expo/skills/atomic-design-gluestack/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "atomic-design-gluestack"
+display_name: "Atomic Design Gluestack"
 short_description: "|"
 default_prompt:
-  - "Use $atomic-design-gluestack"
+  - "Use $atomic-design-gluestack: |."

package/plugins/lisa-expo/skills/container-view-pattern/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "container-view-pattern"
-short_description: "This skill enforces the Container/View pattern for React components. It should be used when creating new components, validating existing components, or refactoring components to follow the separation of concerns pattern where Container handles logic and View handles presentation."
+display_name: "Container View Pattern"
+short_description: "This skill enforces the Container/View pattern for React components"
 default_prompt:
-  - "Use $container-view-pattern"
+  - "Use $container-view-pattern: This skill enforces the Container/View pattern for React components."

package/plugins/lisa-expo/skills/cross-platform-compatibility/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "cross-platform-compatibility"
-short_description: "This skill enforces cross-platform compatibility best practices for Expo apps targeting iOS, Android, and web. It should be used when creating new features, components, or screens to ensure they work correctly on all platforms. Use this skill when writing platform-specific code, using Platform.OS checks, creating platform-specific files (.web.tsx, .native.tsx, .ios.tsx, .android.tsx), or reviewing code for cross-platform issues."
+display_name: "Cross Platform Compatibility"
+short_description: "This skill enforces cross-platform compatibility best practices for Expo apps targeting iOS, Android, and web"
 default_prompt:
-  - "Use $cross-platform-compatibility"
+  - "Use $cross-platform-compatibility: This skill enforces cross-platform compatibility best practices for Expo apps targeting iOS, Android, and web."

package/plugins/lisa-expo/skills/directory-structure/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "directory-structure"
-short_description: "This skill enforces the project's directory structure standards when creating or moving files. Use this skill when creating new components, screens, features, hooks, utilities, or any other code files to ensure they are placed in the correct location with proper naming conventions. Also use when reviewing file placement or restructuring code."
+display_name: "Directory Structure"
+short_description: "This skill enforces the project's directory structure standards when creating or moving files"
 default_prompt:
-  - "Use $directory-structure"
+  - "Use $directory-structure: This skill enforces the project's directory structure standards when creating or moving files."

package/plugins/lisa-expo/skills/exploratory-qa/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "exploratory-qa"
-short_description: "Playwright-backed exploratory QA workflow for web apps. Use when asked to audit an app or project with Playwright/e2e tests, find human-noticeable bugs, identify gaps in automated test coverage, test responsive breakpoints, observe slow or unclear load states, exercise mutable workflows with cleanup, or produce a QA gaps report."
+display_name: "Exploratory QA"
+short_description: "Playwright-backed exploratory QA workflow for web apps"
 default_prompt:
-  - "Use $exploratory-qa"
+  - "Use $exploratory-qa: Playwright-backed exploratory QA workflow for web apps."

package/plugins/lisa-expo/skills/expo-env-config/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "expo-env-config"
-short_description: "This skill should be used when creating, modifying, or accessing environment variables in this Expo/React Native codebase. It enforces type-safe, validated environment configuration using Zod schemas. Use this skill when adding new environment variables, setting up env validation, or writing code that reads from process.env."
+display_name: "Expo Env Config"
+short_description: "creating, modifying, or accessing environment variables in this Expo/React Native codebase"
 default_prompt:
-  - "Use $expo-env-config"
+  - "Use $expo-env-config: creating, modifying, or accessing environment variables in this Expo/React Native codebase."

package/plugins/lisa-expo/skills/expo-router-best-practices/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "expo-router-best-practices"
-short_description: "This skill should be used when creating new routes, configuring navigation layouts, implementing deep linking, or organizing the app/ directory structure in Expo Router projects. It provides best practices for file-based routing patterns."
+display_name: "Expo Router Best Practices"
+short_description: "creating new routes, configuring navigation layouts, implementing deep linking, or organizing the app/ directory structure in Expo Router…"
 default_prompt:
-  - "Use $expo-router-best-practices"
+  - "Use $expo-router-best-practices: creating new routes, configuring navigation layouts, implementing deep linking, or organizing the app/ directory structure in Expo Router…."

package/plugins/lisa-expo/skills/gluestack-nativewind/agents/openai.yaml

@@ -1,4 +1,4 @@
-display_name: "gluestack-nativewind"
-short_description: "This skill enforces Gluestack UI v3 and NativeWind v4 design patterns for consistent, performant, and maintainable styling. It should be used when creating or reviewing components, fixing styling issues, or refactoring styles to follow the constrained design system."
+display_name: "Gluestack Nativewind"
+short_description: "This skill enforces Gluestack UI v3 and NativeWind v4 design patterns for consistent, performant, and maintainable styling"
 default_prompt:
-  - "Use $gluestack-nativewind"
+  - "Use $gluestack-nativewind: This skill enforces Gluestack UI v3 and NativeWind v4 design patterns for consistent, performant, and maintainable styling."