@codyswann/lisa 2.38.0 → 2.39.1

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

@@ -1,4 +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."
+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…"
 default_prompt:
-  - "Use $jira-add-journey"
+  - "Use $jira-add-journey: Add a Validation Journey section to an existing JIRA ticket by reading the ticket description, understanding the feature, and generating…."

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

@@ -1,4 +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."
+display_name: "Jira Create"
+short_description: "creating JIRA epics, stories, and tasks from code files or descriptions"
 default_prompt:
-  - "Use $jira-create"
+  - "Use $jira-create: creating JIRA epics, stories, and tasks from code files or descriptions."

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

@@ -1,4 +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."
+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…"
 default_prompt:
-  - "Use $jira-evidence"
+  - "Use $jira-evidence: Upload screenshots to GitHub pr-assets release, update PR description with evidence, upload attachments to JIRA, post wiki markup comment…."

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

@@ -1,4 +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."
+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…"
 default_prompt:
-  - "Use $jira-journey"
+  - "Use $jira-journey: Read a JIRA ticket's Validation Journey section, execute the steps using Playwright MCP browser tools across all defined viewports, capture…."

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

@@ -1,4 +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."
+display_name: "Jira Verify"
+short_description: "verifying that a JIRA ticket meets organizational standards for epic relationships, description quality, and (for UI tickets) Validation…"
 default_prompt:
-  - "Use $jira-verify"
+  - "Use $jira-verify: verifying that a JIRA ticket meets organizational standards for epic relationships, description quality, and (for UI tickets) Validation…."

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

@@ -1,4 +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."
+display_name: "Local State"
+short_description: "implementing local state management in this React Native/Expo codebase"
 default_prompt:
-  - "Use $local-state"
+  - "Use $local-state: implementing local state management in this React Native/Expo codebase."

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

@@ -1,4 +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."
+display_name: "Ops Browser Uat"
+short_description: "Browser-based user acceptance testing via Playwright MCP tools"
 default_prompt:
-  - "Use $ops-browser-uat"
+  - "Use $ops-browser-uat: Browser-based user acceptance testing via Playwright MCP tools."

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

@@ -1,4 +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."
+display_name: "Ops Check Logs"
+short_description: "Check application logs from local processes, browser console, React Native device logs, or remote AWS CloudWatch"
 default_prompt:
-  - "Use $ops-check-logs"
+  - "Use $ops-check-logs: Check application logs from local processes, browser console, React Native device logs, or remote AWS CloudWatch."

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

@@ -1,4 +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)."
+display_name: "Ops Db Ops"
+short_description: "Database migrations, reverts, schema generation, and GraphQL codegen for Expo + serverless backend projects"
 default_prompt:
-  - "Use $ops-db-ops"
+  - "Use $ops-db-ops: Database migrations, reverts, schema generation, and GraphQL codegen for Expo + serverless backend projects."

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

@@ -1,4 +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."
+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"
+  - "Use $ops-deploy: Deploy Expo frontend (EAS Update/Build) or serverless backend (Serverless Framework) to dev, staging, or production environments."

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

@@ -1,4 +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."
+display_name: "Ops Monitor Errors"
+short_description: "Monitor Sentry for unresolved errors in frontend and backend projects"
 default_prompt:
-  - "Use $ops-monitor-errors"
+  - "Use $ops-monitor-errors: Monitor Sentry for unresolved errors in frontend and backend projects."

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

@@ -1,4 +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."
+display_name: "Ops Performance"
+short_description: "Performance analysis for Expo + serverless backend projects"
 default_prompt:
-  - "Use $ops-performance"
+  - "Use $ops-performance: Performance analysis for Expo + serverless backend projects."

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

@@ -1,4 +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."
+display_name: "Ops Run Local"
+short_description: "Manage the local development environment for Expo + serverless backend projects"
 default_prompt:
-  - "Use $ops-run-local"
+  - "Use $ops-run-local: Manage the local development environment for Expo + serverless backend projects."

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

@@ -1,4 +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."
+display_name: "Ops Verify Health"
+short_description: "Health check all services across environments"
 default_prompt:
-  - "Use $ops-verify-health"
+  - "Use $ops-verify-health: Health check all services across environments."

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

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

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

@@ -1,4 +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."
+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"
 default_prompt:
-  - "Use $playwright-ci-debugging"
+  - "Use $playwright-ci-debugging: Debug Playwright E2E tests that pass locally but fail in CI (or vice versa) in Expo web projects."

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

@@ -1,4 +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."
+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…"
 default_prompt:
-  - "Use $playwright-selectors"
+  - "Use $playwright-selectors: Best practices for writing reliable Playwright E2E tests and adding testID/aria-label selectors in Expo web applications using GlueStack UI…."

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

@@ -1,4 +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."
+display_name: "Reduce Complexity"
+short_description: "This skill provides strategies and patterns for reducing cognitive complexity in React components"
 default_prompt:
-  - "Use $reduce-complexity"
+  - "Use $reduce-complexity: This skill provides strategies and patterns for reducing cognitive complexity in React components."

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

@@ -1,4 +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."
+display_name: "Testing Library"
+short_description: "Enforces best practices for unit testing with Jest, @testing-library/react-native, and jest-expo in Expo projects"
 default_prompt:
-  - "Use $testing-library"
+  - "Use $testing-library: Enforces best practices for unit testing with Jest, @testing-library/react-native, and jest-expo in Expo projects."

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-harper-fabric",
-  "version": "2.38.0",
+  "version": "2.39.1",
   "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.38.0",
+  "version": "2.39.1",
   "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

@@ -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-harper-fabric/skills/harper-build-and-deploy/agents/openai.yaml

@@ -1,4 +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."
+display_name: "Harper Build And Deploy"
+short_description: "building, running locally, or deploying a Harper (HarperDB/Fabric) component — running harper dev/run, producing the generated resources.js…"
 default_prompt:
-  - "Use $harper-build-and-deploy"
+  - "Use $harper-build-and-deploy: building, running locally, or deploying a Harper (HarperDB/Fabric) component — running harper dev/run, producing the generated resources.js…."

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

@@ -1,4 +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."
+display_name: "Harper Component Model"
+short_description: "reasoning about how a Harper (formerly HarperDB) Fabric application is structured — what a component, application, extension, or plugin is…"
 default_prompt:
-  - "Use $harper-component-model"
+  - "Use $harper-component-model: reasoning about how a Harper (formerly HarperDB) Fabric application is structured — what a component, application, extension, or plugin is…."

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

@@ -1,4 +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."
+display_name: "Harper Config Yaml"
+short_description: "creating or editing a Harper (HarperDB/Fabric) component's config.yaml — enabling a built-in extension (graphqlSchema, jsResource, rest…"
 default_prompt:
-  - "Use $harper-config-yaml"
+  - "Use $harper-config-yaml: creating or editing a Harper (HarperDB/Fabric) component's config.yaml — enabling a built-in extension (graphqlSchema, jsResource, rest…."

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

@@ -1,4 +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."
+display_name: "Harper Resources"
+short_description: "writing or editing Harper (HarperDB/Fabric) resources — the classes in resources.js (built from TypeScript under src/) that expose custom…"
 default_prompt:
-  - "Use $harper-resources"
+  - "Use $harper-resources: writing or editing Harper (HarperDB/Fabric) resources — the classes in resources.js (built from TypeScript under src/) that expose custom…."

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

@@ -1,4 +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."
+display_name: "Harper Schema Graphql"
+short_description: "editing a Harper (HarperDB/Fabric) schema.graphql — defining or changing database tables, types, fields, relationships, or indexes that the…"
 default_prompt:
-  - "Use $harper-schema-graphql"
+  - "Use $harper-schema-graphql: editing a Harper (HarperDB/Fabric) schema.graphql — defining or changing database tables, types, fields, relationships, or indexes that the…."

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

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

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

@@ -1,4 +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."
+display_name: "Nestjs Graphql"
+short_description: "Comprehensive guide for NestJS GraphQL development using Apollo and code-first approach"
 default_prompt:
-  - "Use $nestjs-graphql"
+  - "Use $nestjs-graphql: Comprehensive guide for NestJS GraphQL development using Apollo and code-first approach."

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

@@ -1,4 +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."
+display_name: "Nestjs Rules"
+short_description: "Procedural rules and patterns for NestJS backend development"
 default_prompt:
-  - "Use $nestjs-rules"
+  - "Use $nestjs-rules: Procedural rules and patterns for NestJS backend development."

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

@@ -1,4 +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)."
+display_name: "Typeorm Patterns"
+short_description: "Enforces TypeORM implementation patterns for this NestJS backend project"
 default_prompt:
-  - "Use $typeorm-patterns"
+  - "Use $typeorm-patterns: Enforces TypeORM implementation patterns for this NestJS backend project."

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "2.38.0",
+  "version": "2.39.1",
   "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.38.0",
+  "version": "2.39.1",
   "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

@@ -1,4 +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."
+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…"
 default_prompt:
-  - "Use $lisa-openclaw-connect-repo-topic"
+  - "Use $lisa-openclaw-connect-repo-topic: 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…."

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

@@ -1,4 +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."
+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"
 default_prompt:
-  - "Use $lisa-openclaw-connect-staff"
+  - "Use $lisa-openclaw-connect-staff: Connect staff roles to a human chat surface (Telegram or Slack) via OpenClaw using a facilitator/specialist hub-and-spoke model."

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

@@ -1,4 +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."
+display_name: "Lisa Openclaw Setup"
+short_description: "Set up OpenClaw as the chat-surface runtime for this project's staff roles"
 default_prompt:
-  - "Use $lisa-openclaw-setup"
+  - "Use $lisa-openclaw-setup: Set up OpenClaw as the chat-surface runtime for this project's staff roles."

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "2.38.0",
+  "version": "2.39.1",
   "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.38.0",
+  "version": "2.39.1",
   "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

@@ -1,4 +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."
+display_name: "Action Controller Best Practices"
+short_description: "Build or Refactor large Rails controller files into clean, maintainable code"
 default_prompt:
-  - "Use $action-controller-best-practices"
+  - "Use $action-controller-best-practices: Build or Refactor large Rails controller files into clean, maintainable code."

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

@@ -1,4 +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."
+display_name: "Action View Best Practices"
+short_description: "Build or Refactor Rails views, partials, and templates into clean, maintainable code"
 default_prompt:
-  - "Use $action-view-best-practices"
+  - "Use $action-view-best-practices: Build or Refactor Rails views, partials, and templates into clean, maintainable code."

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

@@ -1,4 +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."
+display_name: "Active Record Model Best Practices"
+short_description: "Best practices for Ruby on Rails models, splitting code into well-organized, maintainable code"
 default_prompt:
-  - "Use $active-record-model-best-practices"
+  - "Use $active-record-model-best-practices: Best practices for Ruby on Rails models, splitting code into well-organized, maintainable code."

package/plugins/lisa-rails/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-rails/skills/fix-linter-error/agents/openai.yaml

@@ -1,4 +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."
+display_name: "Fix Linter Error"
+short_description: "fixing all violations of one or more RuboCop cops across the codebase"
 default_prompt:
-  - "Use $fix-linter-error"
+  - "Use $fix-linter-error: fixing all violations of one or more RuboCop cops across the codebase."

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

@@ -1,4 +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."
+display_name: "Improve Code Complexity"
+short_description: "reducing the code complexity threshold of the codebase"
 default_prompt:
-  - "Use $improve-code-complexity"
+  - "Use $improve-code-complexity: reducing the code complexity threshold of the codebase."

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

@@ -1,4 +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."
+display_name: "Improve Max Lines"
+short_description: "reducing the maximum class/module lines threshold and fixing all violations"
 default_prompt:
-  - "Use $improve-max-lines"
+  - "Use $improve-max-lines: reducing the maximum class/module lines threshold and fixing all violations."

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

@@ -1,4 +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."
+display_name: "Improve Max Lines Per Function"
+short_description: "reducing the maximum lines per method threshold and fixing all violations"
 default_prompt:
-  - "Use $improve-max-lines-per-function"
+  - "Use $improve-max-lines-per-function: reducing the maximum lines per method threshold and fixing all violations."

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

@@ -1,4 +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."
+display_name: "Improve Test Coverage"
+short_description: "increasing test coverage to a specified threshold percentage"
 default_prompt:
-  - "Use $improve-test-coverage"
+  - "Use $improve-test-coverage: increasing test coverage to a specified threshold percentage."

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

@@ -1,4 +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."
+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…"
 default_prompt:
-  - "Use $jira-add-journey"
+  - "Use $jira-add-journey: Add a Validation Journey section to an existing JIRA ticket by reading the ticket description, understanding the feature, and generating…."

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

@@ -1,4 +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."
+display_name: "Jira Create"
+short_description: "creating JIRA epics, stories, and tasks from code files or descriptions"
 default_prompt:
-  - "Use $jira-create"
+  - "Use $jira-create: creating JIRA epics, stories, and tasks from code files or descriptions."

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

@@ -1,4 +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."
+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"
 default_prompt:
-  - "Use $jira-evidence"
+  - "Use $jira-evidence: Upload evidence to GitHub pr-assets release, update PR description, upload attachments to JIRA, post comment, and move ticket to Code Review."

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

@@ -1,4 +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."
+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…"
 default_prompt:
-  - "Use $jira-journey"
+  - "Use $jira-journey: Parse a JIRA ticket's Validation Journey section, execute the verification steps, capture evidence, and post to JIRA + GitHub PR using the…."

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

@@ -1,4 +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."
+display_name: "Jira Verify"
+short_description: "verifying that a JIRA ticket meets organizational standards for epic relationships and description quality"
 default_prompt:
-  - "Use $jira-verify"
+  - "Use $jira-verify: verifying that a JIRA ticket meets organizational standards for epic relationships and description quality."

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

@@ -1,4 +1,4 @@
-display_name: "ops-check-logs"
-short_description: "Check application logs from local Docker Compose or remote AWS CloudWatch for Rails applications. Supports log tailing, filtering, and error searching."
+display_name: "Ops Check Logs"
+short_description: "Check application logs from local Docker Compose or remote AWS CloudWatch for Rails applications"
 default_prompt:
-  - "Use $ops-check-logs"
+  - "Use $ops-check-logs: Check application logs from local Docker Compose or remote AWS CloudWatch for Rails applications."

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

@@ -1,4 +1,4 @@
-display_name: "ops-deploy"
-short_description: "Deploy Rails applications via Kamal or CI/CD branch push to staging or production environments."
+display_name: "Ops Deploy"
+short_description: "Deploy Rails applications via Kamal or CI/CD branch push to staging or production environments"
 default_prompt:
-  - "Use $ops-deploy"
+  - "Use $ops-deploy: Deploy Rails applications via Kamal or CI/CD branch push to staging or production environments."

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

@@ -1,4 +1,4 @@
-display_name: "ops-run-local"
-short_description: "Manage the local Docker Compose development environment for Rails applications. Supports start, stop, restart, and status for the full stack or individual services."
+display_name: "Ops Run Local"
+short_description: "Manage the local Docker Compose development environment for Rails applications"
 default_prompt:
-  - "Use $ops-run-local"
+  - "Use $ops-run-local: Manage the local Docker Compose development environment for Rails applications."

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

@@ -1,4 +1,4 @@
-display_name: "ops-verify-jobs"
-short_description: "Verify Solid Queue background jobs are running in Rails applications. Check worker health, queue depth, failed jobs, recurring job execution, and retry stuck jobs."
+display_name: "Ops Verify Jobs"
+short_description: "Verify Solid Queue background jobs are running in Rails applications"
 default_prompt:
-  - "Use $ops-verify-jobs"
+  - "Use $ops-verify-jobs: Verify Solid Queue background jobs are running in Rails applications."

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

@@ -1,4 +1,4 @@
-display_name: "ops-verify-telemetry"
-short_description: "Verify OpenTelemetry traces are being collected and exported to AWS X-Ray for Rails applications. Check collector health, trace export, and CloudWatch metrics."
+display_name: "Ops Verify Telemetry"
+short_description: "Verify OpenTelemetry traces are being collected and exported to AWS X-Ray for Rails applications"
 default_prompt:
-  - "Use $ops-verify-telemetry"
+  - "Use $ops-verify-telemetry: Verify OpenTelemetry traces are being collected and exported to AWS X-Ray for Rails applications."

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

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

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

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