@codyswann/lisa 4.72.0 → 4.72.2

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.0",
+  "version": "4.72.2",
   "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.0",
+  "version": "4.72.2",
   "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.0",
+  "version": "4.72.2",
   "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.0",
+  "version": "4.72.2",
   "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.0",
+  "version": "4.72.2",
   "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.0",
+  "version": "4.72.2",
   "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.0",
+  "version": "4.72.2",
   "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.0",
+  "version": "4.72.2",
   "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.0",
+  "version": "4.72.2",
   "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.0",
+  "version": "4.72.2",
   "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
 

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

@@ -2,6 +2,8 @@
 name: lisa-openclaw-setup
 description: "Set up OpenClaw as the…"
 ---
+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.
+
 
 # lisa-openclaw-setup
 

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

@@ -2,6 +2,8 @@
 name: lisa-setup-openclaw
 description: "Set up OpenClaw as the…"
 ---
+Set up OpenClaw as the chat-surface runtime for this project's staff. Verifies the openclaw CLI, ~/.openclaw/openclaw.json, a secret provider, and required gateway capabilities, then writes a lean `openclaw` section to .lisa.config.json. Run before connect-staff / connect-repo-topic.
+
 ## Lisa Command Compatibility
 
 - Original Claude command: `/lisa:setup-openclaw`

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

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

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

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

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

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

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

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

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

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

package/plugins/lisa-phaser/.codex-plugin/skills/phaser-accessibility/SKILL.md

@@ -2,6 +2,8 @@
 name: phaser-accessibility
 description: "making a Phaser 4 game…"
 ---
+This skill should be used when making a Phaser 4 game accessible — honoring prefers-reduced-motion, pausing on window/tab blur, keyboard navigation and visible focus for menus, colorblind-safe palettes, and a screen-reader live region that announces game state through the DOM. Use it when building menus, settings, HUD, or any player-facing UI, or when an accessibility requirement comes up. Pairs with phaser-services, phaser-i18n, and the official scenes skill.
+
 
 # Phaser 4 Accessibility
 

package/plugins/lisa-phaser/.codex-plugin/skills/phaser-asset-pipeline/SKILL.md

@@ -2,6 +2,8 @@
 name: phaser-asset-pipeline
 description: "setting up or changing the…"
 ---
+This skill should be used when setting up or changing the build-time asset pipeline of a Phaser 4 game — packing raw art in assets/src into public/assets (free-tex-packer-core texture atlases, audiosprite audio sprites, BMFont bitmap fonts) and the codegen step that emits typed keys to src/assets.ts so a missing or renamed key is a compile error. Use it when adding source art, wiring packing into the build, regenerating typed keys, or eliminating raw string asset keys. Assumes the raw art already exists — get it first via phaser-asset-sourcing (CC0 sourcing + license gate). Pairs with phaser-asset-sourcing, the official loading-assets skill, phaser-build-deploy, and phaser-services.
+
 
 # Phaser 4 Asset Pipeline
 

package/plugins/lisa-phaser/.codex-plugin/skills/phaser-asset-sourcing/SKILL.md

@@ -2,6 +2,8 @@
 name: phaser-asset-sourcing
 description: "a Phaser 4 game needs actual…"
 ---
+This skill should be used when a Phaser 4 game needs actual art or audio and none exists yet — deciding WHERE game art comes from before it can be packed. Covers the priority order (curated CC0 packs → deriving/editing CC0 art → asking the human for bespoke/paid work), the strict license gate (CC0-or-equivalent only, recorded with an exact license quote + evidence URL in assets/LICENSES.md), the provenance requirement (a committed ingest script or committed raw sources), why procedural generateTexture placeholders are tracked art debt and never a best practice, and the expectation that characters ship real idle+walk animation. Use it BEFORE phaser-asset-pipeline (which only packs art that already exists). Pairs with phaser-asset-pipeline, the official animations skill, and the art-director / audio-director personas.
+
 
 # Phaser 4 Asset Sourcing
 

package/plugins/lisa-phaser/.codex-plugin/skills/phaser-build-deploy/SKILL.md

@@ -2,6 +2,8 @@
 name: phaser-build-deploy
 description: "configuring the production…"
 ---
+This skill should be used when configuring the production build or deploying a Phaser 4 game — the Vite prod config (manualChunks to split the phaser vendor chunk, terser two-pass minification), content-hashed assets with immutable caching, the base path per host, vite-plugin-pwa (autoUpdate + globPatterns covering game assets), a bundle-size budget, and static hosting. Use it when setting up the build, fixing caching/base-path issues, adding the PWA, or enforcing bundle size. Pairs with phaser-asset-pipeline, phaser-project-structure, and phaser-testing.
+
 
 # Phaser 4 Build and Deploy
 

package/plugins/lisa-phaser/.codex-plugin/skills/phaser-i18n/SKILL.md

@@ -2,6 +2,8 @@
 name: phaser-i18n
 description: "localizing a Phaser 4 game — a…"
 ---
+This skill should be used when localizing a Phaser 4 game — a typed string catalog so no user-facing text is hardcoded, runtime locale switching that re-renders open text, interpolation/pluralization, and the BitmapText vs Text trade-offs (glyph coverage, RTL, CJK) localization forces. Use it when adding any player-facing string, building a language selector, or fixing missing-glyph/hardcoded-text issues. Pairs with phaser-services, phaser-accessibility, and phaser-asset-pipeline.
+
 
 # Phaser 4 Internationalization
 

package/plugins/lisa-phaser/.codex-plugin/skills/phaser-project-structure/SKILL.md

@@ -2,6 +2,8 @@
 name: phaser-project-structure
 description: "creating, restructuring, or…"
 ---
+This skill should be used when creating, restructuring, or reasoning about a Phaser 4 game project — the game config, the Vite + TypeScript layout, the Boot → Preloader → MainMenu → Game scene flow, scale/resolution setup for desktop and mobile, and where code and assets belong. Use it before scaffolding a project, adding a major subsystem, or deciding where a file should live. Pairs with the official scenes skill, the official loading-assets skill, the official filters-and-postfx skill, and phaser-testing.
+
 
 # Phaser 4 Project Structure
 

package/plugins/lisa-phaser/.codex-plugin/skills/phaser-services/SKILL.md

@@ -2,6 +2,8 @@
 name: phaser-services
 description: "wiring cross-cutting services…"
 ---
+This skill should be used when wiring cross-cutting services and shared state in a Phaser 4 game — the typed registry wrapper for global state, a single dedicated EventsCenter bus (never game.events), the .on()/.off() listener discipline enforced in scene shutdown, SoundService (mobile audio unlock on first gesture), InputService (semantic actions instead of raw keys), and SaveService (versioned localStorage with a migration chain). Use it when adding global state, an event bus, audio/input/save plumbing, or fixing listener leaks and lost saves. Pairs with the official scenes skill, phaser-testing, and phaser-i18n.
+
 
 # Phaser 4 Services and Shared State
 

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

@@ -2,6 +2,8 @@
 name: phaser-testing
 description: "writing or designing tests for…"
 ---
+This skill should be used when writing or designing tests for a Phaser 4 game — unit-testing pure game logic with Vitest, keeping logic Phaser-free so it tests without a browser, the Phaser.HEADLESS renderer for logic-only boots, asset-manifest coverage tests, and the CI runtime gates (boot smoke, allocation/perf budget, leak gate, determinism gate, deterministic Playwright visual regression, bundle-size budget) that verify scenes and entities that are excluded from unit coverage. Use it when adding tests, setting up CI verification, or deciding what is testable at which level. Pairs with phaser-project-structure, the official loading-assets skill, and phaser-services.
+
 
 # Phaser 4 Testing
 

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

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

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

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "4.72.0",
+  "version": "4.72.2",
   "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": "4.72.0",
+  "version": "4.72.2",
   "description": "Ruby on Rails-specific skills and hooks for RuboCop and ast-grep scanning on edit.",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-rails/.codex-plugin/skills/action-controller-best-practices/SKILL.md

@@ -2,6 +2,8 @@
 name: action-controller-best-practices
 description: "Build or Refactor large Rails…"
 ---
+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.
+
 
 # Rails Controller Refactoring
 

package/plugins/lisa-rails/.codex-plugin/skills/action-view-best-practices/SKILL.md

@@ -2,6 +2,8 @@
 name: action-view-best-practices
 description: "Build or Refactor Rails views…"
 ---
+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.
+
 
 # Rails View Refactoring
 

package/plugins/lisa-rails/.codex-plugin/skills/active-record-model-best-practices/SKILL.md

@@ -2,6 +2,8 @@
 name: active-record-model-best-practices
 description: "Best practices for Ruby on…"
 ---
+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.
+
 
 # Rails Model Refactoring
 

package/plugins/lisa-rails/.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-rails/.codex-plugin/skills/fix-linter-error/SKILL.md

@@ -4,6 +4,8 @@ description: "fixing all violations of one or…"
 allowed-tools: ["Read", "Bash", "Glob", "Grep"]
 
 ---
+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.
+
 
 # Fix Linter Errors
 

package/plugins/lisa-rails/.codex-plugin/skills/improve-code-complexity/SKILL.md

@@ -3,6 +3,8 @@ name: improve-code-complexity
 description: "reducing the code complexity…"
 allowed-tools: ["Read", "Bash", "Glob", "Grep"]
 ---
+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.
+
 
 # Lower Code Complexity
 

package/plugins/lisa-rails/.codex-plugin/skills/improve-max-lines/SKILL.md

@@ -4,6 +4,8 @@ description: "reducing the maximum…"
 allowed-tools: ["Read", "Bash", "Glob", "Grep"]
 
 ---
+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.
+
 
 # Reduce Max Lines
 

package/plugins/lisa-rails/.codex-plugin/skills/improve-max-lines-per-function/SKILL.md

@@ -4,6 +4,8 @@ description: "reducing the maximum lines per…"
 allowed-tools: ["Read", "Bash", "Glob", "Grep"]
 
 ---
+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.
+
 
 # Reduce Max Lines Per Method
 

package/plugins/lisa-rails/.codex-plugin/skills/improve-test-coverage/SKILL.md

@@ -4,6 +4,8 @@ description: "increasing test coverage to a…"
 allowed-tools: ["Read", "Bash", "Glob", "Grep"]
 
 ---
+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.
+
 
 # Increase Test Coverage
 

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

@@ -2,6 +2,8 @@
 name: jira-add-journey
 description: "Add a Validation Journey…"
 ---
+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.
+
 
 # Add Validation Journey to Existing JIRA Ticket
 

package/plugins/lisa-rails/.codex-plugin/skills/jira-create/SKILL.md

@@ -3,6 +3,8 @@ name: jira-create
 description: "creating JIRA epics, stories…"
 allowed-tools: ["Read", "Glob", "LS", "Skill", "mcp__atlassian__getVisibleJiraProjects", "mcp__atlassian__getJiraProjectIssueTypesMetadata", "mcp__atlassian__getAccessibleAtlassianResources"]
 ---
+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.
+
 
 # Create JIRA Issues from $ARGUMENTS
 

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

@@ -2,6 +2,8 @@
 name: jira-evidence
 description: "Upload evidence to GitHub…"
 ---
+Upload evidence to GitHub pr-assets release, update PR description, upload attachments to JIRA, post 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 evidence and generates evidence/comment.txt + evidence/comment.md.
+
 
 # JIRA Evidence Posting
 

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

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

package/plugins/lisa-rails/.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 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.
+
 
 # Verify JIRA Ticket: $ARGUMENTS