@codyswann/lisa 2.36.0 → 2.38.0

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $spec-conformance"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $task-decomposition"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $task-triage"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $tdd-implementation"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $test-strategy"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $ticket-triage"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $tracker-add-journey"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $tracker-build-intake"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $tracker-create"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $tracker-evidence"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $tracker-journey"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $tracker-read"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $tracker-source-artifacts"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $tracker-sync"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $tracker-validate"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $tracker-verify"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $tracker-write"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $verification-lifecycle"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $verify"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-cdk",
-  "version": "2.36.0",
+  "version": "2.38.0",
   "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.36.0",
+  "version": "2.38.0",
   "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.36.0",
+  "version": "2.38.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.36.0",
+  "version": "2.38.0",
   "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

@@ -0,0 +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."
+default_prompt:
+  - "Use $apollo-client"

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

@@ -0,0 +1,4 @@
+display_name: "atomic-design-gluestack"
+short_description: "|"
+default_prompt:
+  - "Use $atomic-design-gluestack"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $container-view-pattern"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $cross-platform-compatibility"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $directory-structure"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $exploratory-qa"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $expo-env-config"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $expo-router-best-practices"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $gluestack-nativewind"

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

@@ -0,0 +1,4 @@
+display_name: "jira-add-journey"
+short_description: "Add a Validation Journey section to an existing JIRA ticket by reading the ticket description, understanding the feature, and generating the journey steps, viewports, and assertions."
+default_prompt:
+  - "Use $jira-add-journey"

package/plugins/lisa-expo/skills/jira-create/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "jira-create"
+short_description: "This skill should be used when creating JIRA epics, stories, and tasks from code files or descriptions. It analyzes the provided input, determines the appropriate issue hierarchy, and creates issues with comprehensive quality requirements including test-first development and documentation."
+default_prompt:
+  - "Use $jira-create"

package/plugins/lisa-expo/skills/jira-evidence/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "jira-evidence"
+short_description: "Upload screenshots to GitHub pr-assets release, update PR description with evidence, upload attachments to JIRA, post wiki markup comment, and move ticket to Code Review. Reusable by any skill that captures screenshots and generates evidence/comment.txt + evidence/comment.md."
+default_prompt:
+  - "Use $jira-evidence"

package/plugins/lisa-expo/skills/jira-journey/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "jira-journey"
+short_description: "Read a JIRA ticket's Validation Journey section, execute the steps using Playwright MCP browser tools across all defined viewports, capture screenshots at each marker, generate evidence templates, and post to JIRA + GitHub PR using the jira-evidence skill."
+default_prompt:
+  - "Use $jira-journey"

package/plugins/lisa-expo/skills/jira-verify/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "jira-verify"
+short_description: "This skill should be used when verifying that a JIRA ticket meets organizational standards for epic relationships, description quality, and (for UI tickets) Validation Journey presence. It fetches the live ticket and delegates the gate checks to jira-validate-ticket so the bar matches what jira-write-ticket enforces pre-write."
+default_prompt:
+  - "Use $jira-verify"

package/plugins/lisa-expo/skills/local-state/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "local-state"
+short_description: "This skill should be used when implementing local state management in this React Native/Expo codebase. It covers Apollo Client Reactive Variables for in-memory reactive state and React Native AsyncStorage for persistent storage. Use this skill when creating feature flags, user preferences, session state, or any client-only state that needs to survive component unmounts or app restarts."
+default_prompt:
+  - "Use $local-state"

package/plugins/lisa-expo/skills/ops-browser-uat/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "ops-browser-uat"
+short_description: "Browser-based user acceptance testing via Playwright MCP tools. Logs into the application, navigates through features, and captures visual proof with screenshots."
+default_prompt:
+  - "Use $ops-browser-uat"

package/plugins/lisa-expo/skills/ops-check-logs/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "ops-check-logs"
+short_description: "Check application logs from local processes, browser console, React Native device logs, or remote AWS CloudWatch. Supports log tailing, filtering, and error searching across all platforms."
+default_prompt:
+  - "Use $ops-check-logs"

package/plugins/lisa-expo/skills/ops-db-ops/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "ops-db-ops"
+short_description: "Database migrations, reverts, schema generation, and GraphQL codegen for Expo + serverless backend projects. Operates on the backend (TypeORM) and frontend (GraphQL code generation)."
+default_prompt:
+  - "Use $ops-db-ops"

package/plugins/lisa-expo/skills/ops-deploy/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "ops-deploy"
+short_description: "Deploy Expo frontend (EAS Update/Build) or serverless backend (Serverless Framework) to dev, staging, or production environments."
+default_prompt:
+  - "Use $ops-deploy"

package/plugins/lisa-expo/skills/ops-monitor-errors/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "ops-monitor-errors"
+short_description: "Monitor Sentry for unresolved errors in frontend and backend projects. Supports filtering by project, environment, and time range."
+default_prompt:
+  - "Use $ops-monitor-errors"

package/plugins/lisa-expo/skills/ops-performance/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "ops-performance"
+short_description: "Performance analysis for Expo + serverless backend projects. Runs Lighthouse audits, bundle size analysis, and k6 load tests."
+default_prompt:
+  - "Use $ops-performance"

package/plugins/lisa-expo/skills/ops-run-local/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "ops-run-local"
+short_description: "Manage the local development environment for Expo + serverless backend projects. Supports start, stop, restart, and status for the full stack or individual services."
+default_prompt:
+  - "Use $ops-run-local"

package/plugins/lisa-expo/skills/ops-verify-health/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "ops-verify-health"
+short_description: "Health check all services across environments. Checks frontend URLs, backend GraphQL endpoints, and reports response times."
+default_prompt:
+  - "Use $ops-verify-health"

package/plugins/lisa-expo/skills/owasp-zap/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "owasp-zap"
+short_description: ""
+default_prompt:
+  - "Use $owasp-zap"

package/plugins/lisa-expo/skills/playwright-ci-debugging/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "playwright-ci-debugging"
+short_description: "Debug Playwright E2E tests that pass locally but fail in CI (or vice versa) in Expo web projects. Covers local reproduction, network interception, CI environment discovery, commit SHA verification, and robust interaction patterns that eliminate flake. Use this skill when a Playwright test is failing in CI, a test is flaky, a PR is blocked by E2E checks, or you need to investigate CI-specific test behavior. Trigger on mentions of CI failure, failing Playwright test, flaky E2E test, or debugging E2E in CI."
+default_prompt:
+  - "Use $playwright-ci-debugging"

package/plugins/lisa-expo/skills/playwright-selectors/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "playwright-selectors"
+short_description: "Best practices for writing reliable Playwright E2E tests and adding testID/aria-label selectors in Expo web applications using GlueStack UI and NativeWind. Use this skill when creating, debugging, or modifying Playwright tests, adding E2E test coverage, creating components that need test selectors, reviewing code for testability, or troubleshooting testID/data-testid issues. Trigger on any mention of Playwright, E2E tests, end-to-end tests, testID, data-testid, or GlueStack testing in an Expo web context."
+default_prompt:
+  - "Use $playwright-selectors"

package/plugins/lisa-expo/skills/reduce-complexity/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "reduce-complexity"
+short_description: "This skill provides strategies and patterns for reducing cognitive complexity in React components. It should be used when ESLint reports sonarjs/cognitive-complexity violations, when refactoring complex View components, or when planning how to break down large components. The skill enforces this project's Container/View pattern requirements when extracting components."
+default_prompt:
+  - "Use $reduce-complexity"

package/plugins/lisa-expo/skills/testing-library/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "testing-library"
+short_description: "Enforces best practices for unit testing with Jest, @testing-library/react-native, and jest-expo in Expo projects. This skill should be used when writing, reviewing, or debugging unit tests to ensure tests are accessible, maintainable, and follow Testing Library guiding principles. Use this skill for test file creation, query selection, async handling, mocking patterns, and Expo Router testing."
+default_prompt:
+  - "Use $testing-library"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.36.0",
+  "version": "2.38.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.36.0",
+  "version": "2.38.0",
   "description": "Harper/Fabric-specific Lisa rules for TypeScript component apps.",
   "author": {
     "name": "Cody Swann"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $exploratory-qa"

package/plugins/lisa-harper-fabric/skills/harper-build-and-deploy/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "harper-build-and-deploy"
+short_description: "This skill should be used when building, running locally, or deploying a Harper (HarperDB/Fabric) component — running harper dev/run, producing the generated resources.js and web/** from TypeScript via the project build, packaging the harper-app component, deploying to Harper Fabric, or handling deploy-time secrets. Use it for any change that affects the deployable surface or the dev loop. Pairs with harper-component-model, harper-config-yaml, and harper-resources."
+default_prompt:
+  - "Use $harper-build-and-deploy"

package/plugins/lisa-harper-fabric/skills/harper-component-model/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "harper-component-model"
+short_description: "This skill should be used when reasoning about how a Harper (formerly HarperDB) Fabric application is structured — what a component, application, extension, or plugin is, where code and assets belong, and how the pieces depend on each other. Use it before adding a new capability, wiring an extension, deciding where a file should live, or explaining the runtime to someone. Pairs with harper-config-yaml, harper-resources, harper-schema-graphql, and harper-build-and-deploy."
+default_prompt:
+  - "Use $harper-component-model"

package/plugins/lisa-harper-fabric/skills/harper-config-yaml/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "harper-config-yaml"
+short_description: "This skill should be used when creating or editing a Harper (HarperDB/Fabric) component's config.yaml — enabling a built-in extension (graphqlSchema, jsResource, rest, static, roles, loadEnv, dataLoader, fastifyRoutes), wiring an external component, or troubleshooting why an extension is not loading. Critical: it documents the no-merge footgun where a custom config.yaml replaces Harper's default config entirely. Pairs with harper-component-model, harper-resources, and harper-schema-graphql."
+default_prompt:
+  - "Use $harper-config-yaml"

package/plugins/lisa-harper-fabric/skills/harper-resources/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "harper-resources"
+short_description: "This skill should be used when writing or editing Harper (HarperDB/Fabric) resources — the classes in resources.js (built from TypeScript under src/) that expose custom data logic over REST and GraphQL. Use it when adding an endpoint, overriding table behavior, wrapping an external API, or wiring real-time subscriptions. Covers the Resource method-to-HTTP mapping and the TS-is-source build convention. Pairs with harper-schema-graphql, harper-config-yaml, and harper-build-and-deploy."
+default_prompt:
+  - "Use $harper-resources"

package/plugins/lisa-harper-fabric/skills/harper-schema-graphql/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "harper-schema-graphql"
+short_description: "This skill should be used when editing a Harper (HarperDB/Fabric) schema.graphql — defining or changing database tables, types, fields, relationships, or indexes that the graphqlSchema extension turns into Harper tables and API surface. Use it when adding a table, changing the data model, or when a resource/verify path depends on schema shape. Pairs with harper-resources, harper-config-yaml, and harper-component-model."
+default_prompt:
+  - "Use $harper-schema-graphql"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "2.36.0",
+  "version": "2.38.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.36.0",
+  "version": "2.38.0",
   "description": "NestJS-specific skills and migration write-protection hooks.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-nestjs/skills/nestjs-graphql/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "nestjs-graphql"
+short_description: "Comprehensive guide for NestJS GraphQL development using Apollo and code-first approach. This skill should be used when writing GraphQL resolvers, mutations, queries, types, subscriptions, or implementing advanced features like field middleware, complexity limits, and custom scalars. Also covers project-specific patterns including zero-trust auth decorators and DataLoader integration."
+default_prompt:
+  - "Use $nestjs-graphql"

package/plugins/lisa-nestjs/skills/nestjs-rules/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "nestjs-rules"
+short_description: "Procedural rules and patterns for NestJS backend development. This skill should be used when creating new NestJS modules, services, resolvers, or controllers. It covers component generation with NestJS CLI, TDD patterns, module structure conventions, Lambda handler patterns, and configuration standards. Use this skill alongside nestjs-graphql for GraphQL-specific patterns."
+default_prompt:
+  - "Use $nestjs-rules"

package/plugins/lisa-nestjs/skills/typeorm-patterns/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "typeorm-patterns"
+short_description: "Enforces TypeORM implementation patterns for this NestJS backend project. This skill should be used when creating or modifying TypeORM entities, repositories, database configuration, migrations, or any database-related code. It covers configuration patterns (TypeOrmModule.forRootAsync, replication, naming strategy), entity patterns (base entity, comments, indexes), and observability (X-Ray logging)."
+default_prompt:
+  - "Use $typeorm-patterns"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.36.0",
+  "version": "2.38.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.36.0",
+  "version": "2.38.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/skills/lisa-openclaw-connect-repo-topic/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "lisa-openclaw-connect-repo-topic"
+short_description: "Bind a Telegram forum topic to an OpenClaw dispatcher+worker agent pair that runs a coding CLI against a repo, so you can drive code work from chat. Supports single-repo topics and folder-scoped topics (multiple repos with repo-confirmation). Creates/validates the agent pair, ensures the bot is a group admin, captures real group/topic ids, wires the route in ~/.openclaw/openclaw.json, validates the gateway, and runs a no-change self-test. Requires lisa-openclaw-setup first."
+default_prompt:
+  - "Use $lisa-openclaw-connect-repo-topic"

package/plugins/lisa-openclaw/skills/lisa-openclaw-connect-staff/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "lisa-openclaw-connect-staff"
+short_description: "Connect staff roles to a human chat surface (Telegram or Slack) via OpenClaw using a facilitator/specialist hub-and-spoke model. Registers bots/apps, creates or reuses the human-facing surface, wires routes in ~/.openclaw/openclaw.json, writes facilitator/specialist agent prompts, validates the gateway, resets stale sessions, and runs an end-to-end route test. Use when you want a \"chief of staff\" facilitator and its specialists reachable from chat. Requires lisa-openclaw-setup first."
+default_prompt:
+  - "Use $lisa-openclaw-connect-staff"

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

@@ -0,0 +1,4 @@
+display_name: "lisa-openclaw-setup"
+short_description: "Set up OpenClaw as the chat-surface runtime for this project's staff roles. Verifies the openclaw CLI, the ~/.openclaw/openclaw.json config, a secret provider, and the required gateway capabilities (sessions_spawn, native-reply session scoping, the NO_REPLY sentinel), then writes a lean `openclaw` section to .lisa.config.json. Prerequisite for lisa-openclaw-connect-staff and lisa-openclaw-connect-repo-topic. Use when a project wants its facilitator/specialist staff reachable from Telegram or Slack."
+default_prompt:
+  - "Use $lisa-openclaw-setup"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.36.0",
+  "version": "2.38.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.36.0",
+  "version": "2.38.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/skills/action-controller-best-practices/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "action-controller-best-practices"
+short_description: "Build or Refactor large Rails controller files into clean, maintainable code. Use when a controller action exceeds ~10 lines, a controller has custom non-RESTful actions, or when the user asks to refactor, slim down, clean up, or organize a Rails controller. Applies patterns: service objects, query objects, form objects, controller concerns, presenters/decorators, and RESTful resource extraction."
+default_prompt:
+  - "Use $action-controller-best-practices"

package/plugins/lisa-rails/skills/action-view-best-practices/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "action-view-best-practices"
+short_description: "Build or Refactor Rails views, partials, and templates into clean, maintainable code. Use when views have inline Ruby logic, deeply nested partials, jQuery or legacy JavaScript, helper methods returning HTML, or when the user asks to modernize, refactor, or clean up Rails views. Applies patterns - Turbo Frames, Turbo Streams, Stimulus controllers, ViewComponent, presenters, strict locals, and proper partial extraction."
+default_prompt:
+  - "Use $action-view-best-practices"

package/plugins/lisa-rails/skills/active-record-model-best-practices/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "active-record-model-best-practices"
+short_description: "Best practices for Ruby on Rails models, splitting code into well-organized, maintainable code. Use when a model exceeds ~100 lines, has mixed responsibilities, or when the user asks to refactor, extract, clean up, or organize a Rails model. Applies patterns: concerns, service objects, query objects, form objects, and value objects."
+default_prompt:
+  - "Use $active-record-model-best-practices"

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

@@ -0,0 +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."
+default_prompt:
+  - "Use $exploratory-qa"

package/plugins/lisa-rails/skills/fix-linter-error/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "fix-linter-error"
+short_description: "This skill should be used when fixing all violations of one or more RuboCop cops across the codebase. It runs RuboCop, groups violations by cop and file, generates a brief with fix strategies, and creates a plan with tasks to implement the fixes."
+default_prompt:
+  - "Use $fix-linter-error"

package/plugins/lisa-rails/skills/improve-code-complexity/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "improve-code-complexity"
+short_description: "This skill should be used when reducing the code complexity threshold of the codebase. It lowers the CyclomaticComplexity threshold by 2, identifies methods that exceed the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to fix all violations."
+default_prompt:
+  - "Use $improve-code-complexity"

package/plugins/lisa-rails/skills/improve-max-lines/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "improve-max-lines"
+short_description: "This skill should be used when reducing the maximum class/module lines threshold and fixing all violations. It updates the RuboCop configuration, identifies classes and modules exceeding the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to split oversized files."
+default_prompt:
+  - "Use $improve-max-lines"

package/plugins/lisa-rails/skills/improve-max-lines-per-function/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "improve-max-lines-per-function"
+short_description: "This skill should be used when reducing the maximum lines per method threshold and fixing all violations. It updates the RuboCop configuration, identifies methods exceeding the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to split oversized methods."
+default_prompt:
+  - "Use $improve-max-lines-per-function"

package/plugins/lisa-rails/skills/improve-test-coverage/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "improve-test-coverage"
+short_description: "This skill should be used when increasing test coverage to a specified threshold percentage. It runs the test suite with SimpleCov, identifies files with the lowest coverage, generates a brief with coverage gaps, and creates a plan with tasks to add the missing tests."
+default_prompt:
+  - "Use $improve-test-coverage"

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

@@ -0,0 +1,4 @@
+display_name: "jira-add-journey"
+short_description: "Add a Validation Journey section to an existing JIRA ticket by reading the ticket description, understanding the feature, and generating the journey steps and assertions."
+default_prompt:
+  - "Use $jira-add-journey"

package/plugins/lisa-rails/skills/jira-create/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "jira-create"
+short_description: "This skill should be used when creating JIRA epics, stories, and tasks from code files or descriptions. It analyzes the provided input, determines the appropriate issue hierarchy, and creates issues with comprehensive quality requirements including test-first development and documentation."
+default_prompt:
+  - "Use $jira-create"

package/plugins/lisa-rails/skills/jira-evidence/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "jira-evidence"
+short_description: "Upload evidence to GitHub pr-assets release, update PR description, upload attachments to JIRA, post comment, and move ticket to Code Review. Reusable by any skill that captures evidence and generates evidence/comment.txt + evidence/comment.md."
+default_prompt:
+  - "Use $jira-evidence"

package/plugins/lisa-rails/skills/jira-journey/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "jira-journey"
+short_description: "Parse a JIRA ticket's Validation Journey section, execute the verification steps, capture evidence, and post to JIRA + GitHub PR using the jira-evidence skill."
+default_prompt:
+  - "Use $jira-journey"

package/plugins/lisa-rails/skills/jira-verify/agents/openai.yaml

@@ -0,0 +1,4 @@
+display_name: "jira-verify"
+short_description: "This skill should be used when verifying that a JIRA ticket meets organizational standards for epic relationships and description quality. It fetches the live ticket and delegates the gate checks to jira-validate-ticket so the bar matches what jira-write-ticket enforces pre-write."
+default_prompt:
+  - "Use $jira-verify"