@codyswann/lisa 4.72.1 → 4.72.3

package/plugins/lisa-expo/.codex-plugin/skills/jira-evidence/SKILL.md

@@ -2,6 +2,8 @@
 name: jira-evidence
 description: "Upload screenshots to GitHub…"
 ---
+Upload screenshots to GitHub pr-assets release, update PR description with evidence, upload attachments to JIRA, post wiki markup comment, and move ticket to the configured review status only when `jira.workflow.review` is set (otherwise leave it in `claimed`). Reusable by any skill that captures screenshots and generates evidence/comment.txt + evidence/comment.md.
+
 
 # JIRA Evidence Posting
 

package/plugins/lisa-expo/.codex-plugin/skills/jira-journey/SKILL.md

@@ -2,6 +2,8 @@
 name: jira-journey
 description: "Read a JIRA ticket's Validation…"
 ---
+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.
+
 
 # JIRA Validation Journey
 

package/plugins/lisa-expo/.codex-plugin/skills/jira-verify/SKILL.md

@@ -3,6 +3,8 @@ name: jira-verify
 description: "verifying that a JIRA ticket…"
 allowed-tools: ["Skill", "mcp__atlassian__getJiraIssue", "mcp__atlassian__getAccessibleAtlassianResources"]
 ---
+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.
+
 
 # Verify JIRA Ticket: $ARGUMENTS
 

package/plugins/lisa-expo/.codex-plugin/skills/lisa-e2e-coverage-gaps/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-e2e-coverage-gaps
 description: "Explore gaps in the automated…"
 ---
+Explore gaps in the automated Playwright/e2e suite: inventory the app's routes and existing tests, find routes with no coverage or flows tested only on the happy path (missing error, permission, empty, loading, and edge cases), confirm each in the running app, and file bounded build-ready work for worthwhile test gaps via lisa:tracker-write. The optional ready flag (default true) controls build-ready vs backlog. For human usability issues, use exploratory-qa instead.
+
 ## Lisa Command Compatibility
 
 - Original Claude command: `/lisa:e2e-coverage-gaps`

package/plugins/lisa-expo/.codex-plugin/skills/lisa-maestro-mcp-setup/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-maestro-mcp-setup
 description: "Enable the Maestro CLI's MCP…"
 ---
+Enable the Maestro CLI's MCP server (maestro mcp, STDIO) for this machine, robustly. Detects the Maestro CLI + a usable Java runtime (honoring mise/asdf/sdkman), installs or guides what is missing, and registers the server at LOCAL/per-machine scope with an absolute command path and injected JAVA_HOME/PATH so the spawn never dies on a non-login PATH. Never registers at committed/project scope, which would reintroduce the fleet-wide -32000 failure.
+
 ## Lisa Command Compatibility
 
 - Original Claude command: `/lisa:maestro-mcp-setup`

package/plugins/lisa-expo/.codex-plugin/skills/local-state/SKILL.md

@@ -2,6 +2,8 @@
 name: local-state
 description: "implementing local state…"
 ---
+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.
+
 
 # Local State Management
 

package/plugins/lisa-expo/.codex-plugin/skills/maestro-mcp-setup/SKILL.md

@@ -5,6 +5,8 @@ allowed-tools:
   - Bash
   - Read
 ---
+Enable the Maestro CLI's built-in MCP server (`maestro mcp`, STDIO) for this machine, robustly. Detects the Maestro CLI and a usable Java runtime, installs/guides what is missing, and registers the MCP server at LOCAL (per-machine, uncommitted) scope with an absolute command path and injected JAVA_HOME/PATH so the spawn never dies on a non-login PATH. Use when an Expo project needs Maestro device-automation tools (list_devices, inspect_screen, take_screenshot, run flows). Never registers at project/committed scope — that reintroduces the fleet-wide "-32000" failure.
+
 
 # Maestro MCP Setup
 

package/plugins/lisa-expo/.codex-plugin/skills/native-data-fetching/SKILL.md

@@ -4,6 +4,8 @@ description: "implementing or debugging ANY…"
 version: 1.0.0
 license: MIT
 ---
+Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router data loaders (`useLoaderData`).
+
 
 # Expo Networking
 

package/plugins/lisa-expo/.codex-plugin/skills/ops-browser-uat/SKILL.md

@@ -5,6 +5,8 @@ allowed-tools:
   - Bash
   - Read
 ---
+Browser-based user acceptance testing via Playwright MCP tools. Logs into the application, navigates through features, and captures visual proof with screenshots.
+
 
 # Ops: Browser UAT
 

package/plugins/lisa-expo/.codex-plugin/skills/ops-check-logs/SKILL.md

@@ -5,6 +5,8 @@ allowed-tools:
   - Bash
   - Read
 ---
+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.
+
 
 # Ops: Check Logs
 

package/plugins/lisa-expo/.codex-plugin/skills/ops-db-ops/SKILL.md

@@ -5,6 +5,8 @@ allowed-tools:
   - Bash
   - Read
 ---
+Database migrations, reverts, schema generation, GraphQL codegen, and the reset/seed/verify state operations for Expo + serverless backend projects. Operates on the backend (TypeORM) and frontend (GraphQL code generation).
+
 
 # Ops: Database Operations
 

package/plugins/lisa-expo/.codex-plugin/skills/ops-deploy/SKILL.md

@@ -5,6 +5,8 @@ allowed-tools:
   - Bash
   - Read
 ---
+Deploy Expo frontend (EAS Update/Build) or serverless backend (Serverless Framework) to dev, staging, or production environments.
+
 
 # Ops: Deploy
 

package/plugins/lisa-expo/.codex-plugin/skills/ops-monitor-errors/SKILL.md

@@ -5,6 +5,8 @@ allowed-tools:
   - Bash
   - Read
 ---
+Monitor Sentry for unresolved errors in frontend and backend projects. Supports filtering by project, environment, and time range.
+
 
 # Ops: Monitor Errors
 

package/plugins/lisa-expo/.codex-plugin/skills/ops-performance/SKILL.md

@@ -5,6 +5,8 @@ allowed-tools:
   - Bash
   - Read
 ---
+Performance analysis for Expo + serverless backend projects. Runs Lighthouse audits, bundle size analysis, and k6 load tests.
+
 
 # Ops: Performance
 

package/plugins/lisa-expo/.codex-plugin/skills/ops-run-local/SKILL.md

@@ -5,6 +5,8 @@ allowed-tools:
   - Bash
   - Read
 ---
+Manage the local development environment for Expo + serverless backend projects. Supports start, stop, restart, and status for the full stack or individual services.
+
 
 # Ops: Run Local
 

package/plugins/lisa-expo/.codex-plugin/skills/ops-verify-health/SKILL.md

@@ -5,6 +5,8 @@ allowed-tools:
   - Bash
   - Read
 ---
+Health check all services across environments. Checks frontend URLs, backend GraphQL endpoints, and reports response times.
+
 
 # Ops: Verify Health
 

package/plugins/lisa-expo/.codex-plugin/skills/owasp-zap/SKILL.md

@@ -2,6 +2,8 @@
 name: owasp-zap
 description: "running or interpreting an…"
 ---
+This skill should be used when running or interpreting an OWASP ZAP baseline DAST scan of the Expo web export — after changes to HTTP headers, authentication, or security middleware, before deploying to staging or production, or when triaging ZAP findings from CI or pull request checks. Covers running scripts/zap-baseline.sh locally, risk-level triage, common findings and fixes, and .zap/baseline.conf rule configuration.
+
 
 # OWASP ZAP Baseline Scanning
 

package/plugins/lisa-expo/.codex-plugin/skills/play-store-access/SKILL.md

@@ -7,6 +7,8 @@ allowed-tools:
   - Bash
   - Read
 ---
+Read-only Google Play Console access layer for Expo projects. Use when an operator or agent needs to set up Play Developer API credentials, resolve the Android package name, or check the production track release state without using the Play Console UI. Reads the androidpublisher v3 API only; track promotion, rollout changes, and submissions are out of scope.
+
 
 # Play Store Access: $ARGUMENTS
 

package/plugins/lisa-expo/.codex-plugin/skills/playwright-ci-debugging/SKILL.md

@@ -2,6 +2,8 @@
 name: playwright-ci-debugging
 description: "Debug Playwright E2E tests that…"
 ---
+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.
+
 
 # Debugging Playwright E2E Failures in CI
 

package/plugins/lisa-expo/.codex-plugin/skills/playwright-selectors/SKILL.md

@@ -2,6 +2,8 @@
 name: playwright-selectors
 description: "Best practices for writing…"
 ---
+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.
+
 
 # Playwright E2E Testing for Expo + GlueStack UI
 

package/plugins/lisa-expo/.codex-plugin/skills/reduce-complexity/SKILL.md

@@ -2,6 +2,8 @@
 name: reduce-complexity
 description: "This skill provides strategies…"
 ---
+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.
+
 
 # Reduce Complexity
 

package/plugins/lisa-expo/.codex-plugin/skills/testing-library/SKILL.md

@@ -2,6 +2,8 @@
 name: testing-library
 description: "Enforces best practices for…"
 ---
+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.
+
 
 # Testing Library Best Practices
 

package/plugins/lisa-expo/.codex-plugin/skills/upgrading-expo/SKILL.md

@@ -4,6 +4,8 @@ description: "Guidelines for upgrading Expo…"
 version: 1.0.0
 license: MIT
 ---
+Guidelines for upgrading Expo SDK versions and fixing dependency issues
+
 
 ## References
 

package/plugins/lisa-expo/.codex-plugin/skills/use-dom/SKILL.md

@@ -4,6 +4,8 @@ description: "Use Expo DOM components to run…"
 version: 1.0.0
 license: MIT
 ---
+Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
+
 
 ## What are DOM Components?
 

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

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

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

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

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

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

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

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

package/plugins/lisa-harper-fabric/.codex-plugin/skills/e2e-coverage-gaps/SKILL.md

@@ -2,6 +2,8 @@
 name: e2e-coverage-gaps
 description: "Playwright/e2e coverage-gap…"
 ---
+Playwright/e2e coverage-gap explorer that FEEDS THE LIFECYCLE. Use when asked to find paths the automated end-to-end suite does NOT cover — routes with no test at all, or flows that are only happy-path tested (missing error, validation, permission, empty, loading, and edge states). It inventories the app's routes and the existing Playwright tests, explores the running app to confirm each uncovered or under-covered path is real and reachable, and files bounded build-ready work for worthwhile test gaps via lisa-tracker-write. For human usability/experience issues (confusing, cramped, or broken UI), use the lisa-exploratory-qa skill instead.
+
 
 # E2E Coverage Gaps
 

package/plugins/lisa-harper-fabric/.codex-plugin/skills/harper-auth/SKILL.md

@@ -2,6 +2,8 @@
 name: harper-auth
 description: "adding or debugging Harper…"
 ---
+This skill should be used when adding or debugging Harper (HarperDB/Fabric) authentication and authorization - roles.yaml, user and role Operations API calls, Basic auth, JWT operation tokens, exported-resource permissions, and Resource context.user checks. Pairs with harper-config-yaml, harper-resources, harper-rest-queries, and harper-operations.
+
 
 # Harper Auth
 

package/plugins/lisa-harper-fabric/.codex-plugin/skills/harper-build-and-deploy/SKILL.md

@@ -2,6 +2,8 @@
 name: harper-build-and-deploy
 description: "building, running locally, or…"
 ---
+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.
+
 
 # Harper Build and Deploy
 

package/plugins/lisa-harper-fabric/.codex-plugin/skills/harper-caching/SKILL.md

@@ -2,6 +2,8 @@
 name: harper-caching
 description: "implementing Harper…"
 ---
+This skill should be used when implementing Harper (HarperDB/Fabric) caching tables, external-source caches, TTL expiration, stale revalidation, invalidation, and cache verification. Use it when caching an upstream API, database, or expensive computation in Harper instead of hand-rolling in-memory maps. Pairs with harper-resources, harper-schema-graphql, harper-rest-queries, and harper-operations.
+
 
 # Harper Caching
 

package/plugins/lisa-harper-fabric/.codex-plugin/skills/harper-component-model/SKILL.md

@@ -2,6 +2,8 @@
 name: harper-component-model
 description: "reasoning about how a Harper…"
 ---
+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.
+
 
 # Harper Component Model
 

package/plugins/lisa-harper-fabric/.codex-plugin/skills/harper-config-yaml/SKILL.md

@@ -2,6 +2,8 @@
 name: harper-config-yaml
 description: "creating or editing a Harper…"
 ---
+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.
+
 
 # Harper config.yaml
 

package/plugins/lisa-harper-fabric/.codex-plugin/skills/harper-operations/SKILL.md

@@ -2,6 +2,8 @@
 name: harper-operations
 description: "operating, monitoring, or…"
 ---
+This skill should be used when operating, monitoring, or debugging a Harper (HarperDB/Fabric) component after it builds or deploys - Operations API calls, component inventory, log retrieval, health checks, job lookup, local 500 debugging, and escalation boundaries. Pairs with harper-build-and-deploy, harper-config-yaml, harper-resources, and harper-rest-queries.
+
 
 # Harper Operations
 

package/plugins/lisa-harper-fabric/.codex-plugin/skills/harper-realtime/SKILL.md

@@ -2,6 +2,8 @@
 name: harper-realtime
 description: "adding or troubleshooting…"
 ---
+This skill should be used when adding or troubleshooting Harper (HarperDB/Fabric) real-time behavior: MQTT topics, WebSocket resource subscriptions, resource publish/subscribe handlers, SSE-style streaming routes, and local subscriber verification. Pairs with harper-resources, harper-config-yaml, harper-schema-graphql, and harper-build-and-deploy.
+
 
 # Harper Realtime
 

package/plugins/lisa-harper-fabric/.codex-plugin/skills/harper-resources/SKILL.md

@@ -2,6 +2,8 @@
 name: harper-resources
 description: "writing or editing Harper…"
 ---
+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.
+
 
 # Harper Resources
 

package/plugins/lisa-harper-fabric/.codex-plugin/skills/harper-rest-queries/SKILL.md

@@ -2,6 +2,8 @@
 name: harper-rest-queries
 description: "building or debugging Harper…"
 ---
+This skill should be used when building or debugging Harper (HarperDB/Fabric) REST collection queries and Resource search methods - filters, FIQL comparison operators, OR/grouping, select, sort, limit/offset pagination, relationship traversal, request context, and transaction boundaries. Use it when adding list endpoints, admin filters, query builders, or multi-write resource methods. Pairs with harper-resources and harper-schema-graphql.
+
 
 # Harper REST Queries
 

package/plugins/lisa-harper-fabric/.codex-plugin/skills/harper-schema-graphql/SKILL.md

@@ -1,7 +1,9 @@
 ---
 name: harper-schema-graphql
-description: "editing a Harper (HarperDB/Fabri…"
+description: "editing a Harper…"
 ---
+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.
+
 
 # Harper schema.graphql
 

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

@@ -1,4 +1,4 @@
 display_name: "Harper Schema Graphql"
-short_description: "editing a Harper (HarperDB/Fabri…"
+short_description: "editing a Harper…"
 default_prompt:
-  - "Use $harper-schema-graphql: editing a Harper (HarperDB/Fabri…."
+  - "Use $harper-schema-graphql: editing a Harper…."

package/plugins/lisa-harper-fabric/.codex-plugin/skills/harper-testing/SKILL.md

@@ -2,6 +2,8 @@
 name: harper-testing
 description: "adding, repairing, or designing…"
 ---
+This skill should be used when adding, repairing, or designing tests for a Harper (HarperDB/Fabric) component app — Vitest unit tests for pure functions and Resource methods, local Harper integration tests that boot/symlink/seed/assert real endpoints, Playwright e2e tests against REST/GraphQL routes, and schema/verify-script coupling. Use it when a Harper app needs its first test suite, endpoint coverage, seed isolation, or a local smoke/verify path. Pairs with harper-build-and-deploy, harper-schema-graphql, and e2e-coverage-gaps.
+
 
 # Harper Testing
 

package/plugins/lisa-harper-fabric/.codex-plugin/skills/lisa-e2e-coverage-gaps/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-e2e-coverage-gaps
 description: "Explore gaps in the automated…"
 ---
+Explore gaps in the automated Playwright/e2e suite: inventory the app's routes and existing tests, find routes with no coverage or flows tested only on the happy path (missing error, permission, empty, loading, and edge cases), confirm each in the running app, and file bounded build-ready work for worthwhile test gaps via lisa:tracker-write. The optional ready flag (default true) controls build-ready vs backlog. For human usability issues, use exploratory-qa instead.
+
 ## Lisa Command Compatibility
 
 - Original Claude command: `/lisa:e2e-coverage-gaps`

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

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

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

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

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

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

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

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

package/plugins/lisa-nestjs/.codex-plugin/skills/nestjs-graphql/SKILL.md

@@ -2,6 +2,8 @@
 name: nestjs-graphql
 description: "Comprehensive guide for NestJS…"
 ---
+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.
+
 
 # NestJS GraphQL Development Guide
 

package/plugins/lisa-nestjs/.codex-plugin/skills/nestjs-rules/SKILL.md

@@ -2,6 +2,8 @@
 name: nestjs-rules
 description: "Procedural rules and patterns…"
 ---
+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.
+
 
 # NestJS Development Rules
 

package/plugins/lisa-nestjs/.codex-plugin/skills/typeorm-patterns/SKILL.md

@@ -2,6 +2,8 @@
 name: typeorm-patterns
 description: "Enforces TypeORM implementation…"
 ---
+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).
+
 
 # TypeORM Patterns
 

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

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

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

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-openclaw",
-  "version": "4.72.1",
+  "version": "4.72.3",
   "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": "4.72.1",
+  "version": "4.72.3",
   "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/.codex-plugin/skills/lisa-connect-repo-topic/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-connect-repo-topic
 description: "Bind a Telegram forum topic to…"
 ---
+Bind a Telegram forum topic to an OpenClaw dispatcher+worker pair that runs a coding CLI against a repo (single-repo or folder-scoped), so you can drive code work from chat. Requires /lisa:setup-openclaw first.
+
 ## Lisa Command Compatibility
 
 - Original Claude command: `/lisa:connect-repo-topic`

package/plugins/lisa-openclaw/.codex-plugin/skills/lisa-connect-staff-slack/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-connect-staff-slack
 description: "Connect staff roles to Slack…"
 ---
+Connect staff roles to Slack via OpenClaw using a facilitator/specialist hub-and-spoke model — register the app, create/reuse the facilitator channel, wire routes, validate, and run an end-to-end route test. Requires /lisa:setup-openclaw first.
+
 ## Lisa Command Compatibility
 
 - Original Claude command: `/lisa:connect-staff-slack`

package/plugins/lisa-openclaw/.codex-plugin/skills/lisa-connect-staff-telegram/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-connect-staff-telegram
 description: "Connect staff roles to Telegram…"
 ---
+Connect staff roles to Telegram via OpenClaw using a facilitator/specialist hub-and-spoke model — register bots, create/reuse the facilitator topic, wire routes, validate, and run an end-to-end route test. Requires /lisa:setup-openclaw first.
+
 ## Lisa Command Compatibility
 
 - Original Claude command: `/lisa:connect-staff-telegram`

package/plugins/lisa-openclaw/.codex-plugin/skills/lisa-openclaw-connect-repo-topic/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-openclaw-connect-repo-topic
 description: "Bind a Telegram forum topic to…"
 ---
+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.
+
 
 # lisa-openclaw-connect-repo-topic
 

package/plugins/lisa-openclaw/.codex-plugin/skills/lisa-openclaw-connect-staff/SKILL.md

@@ -2,6 +2,8 @@
 name: lisa-openclaw-connect-staff
 description: "Connect staff roles to a human…"
 ---
+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.
+
 
 # lisa-openclaw-connect-staff