@codyswann/lisa 4.72.1 → 4.72.2

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

@@ -3,6 +3,8 @@ name: lisa-verify-prd
 description: "Initiative-level PRD acceptance…"
 allowed-tools: ["Skill", "Bash", "Read"]
 ---
+Initiative-level PRD acceptance gate. Given a PRD ref/URL (GitHub, Linear, Notion, Confluence, or JIRA), resolves the source vendor, reads the PRD and its generated top-level child work via the prd-lifecycle-rollup contract, and confirms every required child is terminal before any verification runs — if any is non-terminal it reports the incomplete set and STOPS. When the guard passes it runs spec-conformance against the original PRD requirements plus empirical verification via verification-lifecycle. On CONFORMS with all checks passing: transitions the PRD shipped → verified and posts evidence. On PARTIAL/DIVERGES or any failing check: re-opens the PRD shipped → ticketed (NEVER blocked), creates build-ready fix tickets for each divergence, and posts a product-readable failure report — the fix tickets auto-build, rollup re-ships the PRD, and a later intake cycle re-verifies, so the loop closes itself. Idempotent re-runs: comments regenerate in place via sentinel markers; fix tickets dedupe by stable ref.
+
 
 # PRD-level Verification: $ARGUMENTS
 

package/plugins/lisa/.codex-plugin/skills/lisa-verify-workflow-change/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-verify-workflow-change
 description: "a GitHub Actions workflow file…"
 allowed-tools: ["Bash", "Read"]
 ---
+Use when a GitHub Actions workflow file changed and you need pre-merge runtime proof. Classifies default-branch-only triggers, dispatches a safe workflow_dispatch sibling on the branch ref when possible, observes the exact step under test, cancels before side effects, and proves cleanup.
+
 
 # Verify Workflow Change
 

package/plugins/lisa/.codex-plugin/skills/lisa-wiki-install/SKILL.md

@@ -3,6 +3,8 @@ name: lisa-wiki-install
 description: "Bootstrap the LLM Wiki kernel…"
 allowed-tools: ["Bash", "Read", "Write", "Edit"]
 ---
+Bootstrap the LLM Wiki kernel (lisa-wiki plugin) in a host project. Solves the chicken-and-egg gap: the base lisa plugin can install the wiki plugin so its setup skill becomes discoverable. Edits .claude/settings.json to enable lisa-wiki@lisa and confirm the CodySwannGT/lisa marketplace, then for Codex verifies whether the .codex/skills/lisa overlay already carries lisa-wiki-* skills (printed by Lisa's apply) and nudges the user to refresh the overlay if missing. Idempotent. Never auto-runs `lisa apply`. After this skill, reload the runtime and run /setup:wiki (Claude) or $lisa-wiki-setup (Codex) to scaffold the wiki itself.
+
 
 # Install the LLM Wiki kernel
 

package/plugins/lisa/rules/reference/design-source-of-truth.md

@@ -1,7 +1,7 @@
 # Design Source of Truth
 
 > Demoted from the always-on eager tier by CodySwannGT/lisa#3992. The
-> section below is the former eager head, maintained with the full
+> section below is the former eager head, preserved verbatim; the full
 > contract follows it. Reachable on demand via [the rule index](../eager/00-rule-index.md).
 
 ## Design Source of Truth (load-bearing)

package/plugins/lisa/rules/reference/rejection-detection.md

@@ -272,7 +272,7 @@ The state-only reading is what fails today, so a backward move is **not** suffic
 - **JIRA** — `lisa-atlassian-access operation: changelog key:<K>`; each changelog entry carries an `author` alongside its `from`/`to` status items.
 - **Linear** — `lisa-linear-access operation: history id:<ID>`; each history node carries an `actor` alongside `fromState` / `toState`.
 
-An actor is **this flow** when it is the configured automation identity, or when the flow's own marker note (`[lisa-repair-intake]`) sits at that transition's timestamp. Any other actor is a human. Where the surface does not expose an actor at all, the result is `unknown` — never an assumed human.
+An actor is **this flow** when it is the configured automation identity, or when the flow's own marker note (`[lisa-repair-intake]`) sits at that transition's timestamp. A different actor counts as human only when the provider positively identifies a person, rather than a bot, integration, or another automation identity. Missing or ambiguous actor information yields `unknown` — never an assumed human.
 
 **A marker and a transition on the same item say nothing until you know their order.** A hold label, a comment and a lane move routinely coexist on a reversed item, and co-occurrence reads equally well in both directions — a label applied *before* a transition guards it, the same label applied *after* records that the transition was undone. Sourcing the facts, attributing them correctly and reading the artifact all pass cleanly on an invented sequence; only ordering disconfirms it. Compare timestamps explicitly and treat an unorderable pair as `unknown`.
 

package/plugins/lisa-agy/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "4.72.1",
+  "version": "4.72.2",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

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

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

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

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

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

@@ -1,7 +1,9 @@
 ---
 name: lisa-setup-aws
-description: "Provision the dev/staging/produc…"
+description: "Provision the…"
 ---
+Provision the dev/staging/production/shared AWS accounts this CDK project deploys into via the @codyswann/aws-soc2-setup CLI (Organizations, Control Tower, IAM Identity Center, SOC 2 controls), then wire them in end-to-end: SSO profiles, cdk bootstrap with pipeline trust, PLACEHOLDER account IDs in config/environments.ts, AWS_ACCOUNT_ID_* GitHub secrets, and the .lisa.config.json account map. Idempotent; console-only prerequisites (root MFA, Identity Center, landing zone) surface as a human checklist instead of being automated.
+
 ## Lisa Command Compatibility
 
 - Original Claude command: `/lisa:setup:aws`

package/plugins/lisa-cdk/.codex-plugin/skills/lisa-setup-aws/agents/openai.yaml

@@ -1,4 +1,4 @@
 display_name: "Setup AWS"
-short_description: "Provision the dev/staging/produc…"
+short_description: "Provision the…"
 default_prompt:
-  - "Use $lisa-setup-aws: Provision the dev/staging/produc…."
+  - "Use $lisa-setup-aws: Provision the…."

package/plugins/lisa-cdk/.codex-plugin/skills/setup-aws-accounts/SKILL.md

@@ -3,6 +3,8 @@ name: setup-aws-accounts
 description: "Provision the multi-account AWS…"
 allowed-tools: ["Bash", "Read", "Edit", "Write", "AskUserQuestion"]
 ---
+Provision the multi-account AWS environment a Lisa CDK project deploys into, using the @codyswann/aws-soc2-setup CLI (AWS Organizations, Control Tower, IAM Identity Center, SOC 2 controls). Use when a CDK project still has PLACEHOLDER account IDs in config/environments.ts, when asked to create the dev/staging/production/shared AWS accounts, or when CDK deploys fail because accounts, SSO profiles, or bootstrap are missing. Drives the CLI for the org + OU + security foundation and Account Factory account vending, writes the AWS SSO profiles the project's scripts expect, runs cdk bootstrap with cross-account pipeline trust, replaces PLACEHOLDER account IDs, sets the AWS_ACCOUNT_ID_* GitHub secrets when CI uses them, and records the account map in .lisa.config.json. Idempotent — safe to re-run. Console-only prerequisites (root MFA, enabling Identity Center, creating the Control Tower landing zone) are surfaced as an explicit human checklist, never automated.
+
 
 # Setup AWS Accounts (SOC 2 Landing Zone)
 

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

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

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

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "4.72.1",
+  "version": "4.72.2",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-copilot/rules/reference/design-source-of-truth.md

@@ -1,7 +1,7 @@
 # Design Source of Truth
 
 > Demoted from the always-on eager tier by CodySwannGT/lisa#3992. The
-> section below is the former eager head, maintained with the full
+> section below is the former eager head, preserved verbatim; the full
 > contract follows it. Reachable on demand via [the rule index](../eager/00-rule-index.md).
 
 ## Design Source of Truth (load-bearing)

package/plugins/lisa-copilot/rules/reference/rejection-detection.md

@@ -272,7 +272,7 @@ The state-only reading is what fails today, so a backward move is **not** suffic
 - **JIRA** — `lisa-atlassian-access operation: changelog key:<K>`; each changelog entry carries an `author` alongside its `from`/`to` status items.
 - **Linear** — `lisa-linear-access operation: history id:<ID>`; each history node carries an `actor` alongside `fromState` / `toState`.
 
-An actor is **this flow** when it is the configured automation identity, or when the flow's own marker note (`[lisa-repair-intake]`) sits at that transition's timestamp. Any other actor is a human. Where the surface does not expose an actor at all, the result is `unknown` — never an assumed human.
+An actor is **this flow** when it is the configured automation identity, or when the flow's own marker note (`[lisa-repair-intake]`) sits at that transition's timestamp. A different actor counts as human only when the provider positively identifies a person, rather than a bot, integration, or another automation identity. Missing or ambiguous actor information yields `unknown` — never an assumed human.
 
 **A marker and a transition on the same item say nothing until you know their order.** A hold label, a comment and a lane move routinely coexist on a reversed item, and co-occurrence reads equally well in both directions — a label applied *before* a transition guards it, the same label applied *after* records that the transition was undone. Sourcing the facts, attributing them correctly and reading the artifact all pass cleanly on an invented sequence; only ordering disconfirms it. Compare timestamps explicitly and treat an unorderable pair as `unknown`.
 

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa",
-  "version": "4.72.1",
+  "version": "4.72.2",
   "description": "Universal governance — agents, skills, commands, hooks, and rules for all projects",
   "author": {
     "name": "Cody Swann"

package/plugins/lisa-cursor/rules/design-source-of-truth-reference.mdc

@@ -6,7 +6,7 @@ alwaysApply: false
 # Design Source of Truth
 
 > Demoted from the always-on eager tier by CodySwannGT/lisa#3992. The
-> section below is the former eager head, maintained with the full
+> section below is the former eager head, preserved verbatim; the full
 > contract follows it. Reachable on demand via [the rule index](00-rule-index.mdc).
 
 ## Design Source of Truth (load-bearing)

package/plugins/lisa-cursor/rules/rejection-detection-reference.mdc

@@ -277,7 +277,7 @@ The state-only reading is what fails today, so a backward move is **not** suffic
 - **JIRA** — `lisa-atlassian-access operation: changelog key:<K>`; each changelog entry carries an `author` alongside its `from`/`to` status items.
 - **Linear** — `lisa-linear-access operation: history id:<ID>`; each history node carries an `actor` alongside `fromState` / `toState`.
 
-An actor is **this flow** when it is the configured automation identity, or when the flow's own marker note (`[lisa-repair-intake]`) sits at that transition's timestamp. Any other actor is a human. Where the surface does not expose an actor at all, the result is `unknown` — never an assumed human.
+An actor is **this flow** when it is the configured automation identity, or when the flow's own marker note (`[lisa-repair-intake]`) sits at that transition's timestamp. A different actor counts as human only when the provider positively identifies a person, rather than a bot, integration, or another automation identity. Missing or ambiguous actor information yields `unknown` — never an assumed human.
 
 **A marker and a transition on the same item say nothing until you know their order.** A hold label, a comment and a lane move routinely coexist on a reversed item, and co-occurrence reads equally well in both directions — a label applied *before* a transition guards it, the same label applied *after* records that the transition was undone. Sourcing the facts, attributing them correctly and reading the artifact all pass cleanly on an invented sequence; only ordering disconfirms it. Compare timestamps explicitly and treat an unorderable pair as `unknown`.
 

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

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

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

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

package/plugins/lisa-expo/.codex-plugin/skills/add-app-clip/SKILL.md

@@ -2,6 +2,8 @@
 name: add-app-clip
 description: "Add an iOS App Clip target to…"
 ---
+Add an iOS App Clip target to an Expo app. Use when the user mentions App Clip, AASA, apple-app-site-association, appclips, smart app banner, or wants to ship a lightweight iOS Clip invoked from a URL alongside their parent app.
+
 
 # Add an App Clip to an Expo App
 

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

@@ -2,6 +2,8 @@
 name: apollo-client
 description: "writing or modifying GraphQL…"
 ---
+This skill should be used when writing or modifying GraphQL operations, hooks, or mutations using Apollo Client 3.10. It enforces best practices for optimistic responses, cache updates, and TypeScript type generation. Use this skill when creating new queries/mutations, reviewing Apollo code, or troubleshooting cache issues.
+
 
 # Apollo Client 3.10
 

package/plugins/lisa-expo/.codex-plugin/skills/atomic-design-gluestack/SKILL.md

@@ -2,6 +2,8 @@
 name: atomic-design-gluestack
 description: "Enforces atomic design…"
 ---
+Enforces atomic design methodology (atoms, molecules, organisms, templates, pages) for React Native/Expo projects using Gluestack UI. This skill should be used when creating new components, validating existing component organization, reviewing component placement decisions, or planning component architecture. Use this skill to ensure components are properly categorized, placed in correct directories, and follow composition patterns appropriate to their atomic level.
+
 
 # Atomic Design with Gluestack UI
 

package/plugins/lisa-expo/.codex-plugin/skills/building-native-ui/SKILL.md

@@ -4,6 +4,8 @@ description: "Complete guide for building…"
 version: 1.0.1
 license: MIT
 ---
+Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
+
 
 # Expo UI Guidelines
 

package/plugins/lisa-expo/.codex-plugin/skills/container-view-pattern/SKILL.md

@@ -2,6 +2,8 @@
 name: container-view-pattern
 description: "This skill enforces the…"
 ---
+This skill enforces the Container/View pattern for React components. It should be used when creating new components, validating existing components, or refactoring components to follow the separation of concerns pattern where Container handles logic and View handles presentation.
+
 
 # Container/View Pattern
 

package/plugins/lisa-expo/.codex-plugin/skills/cross-platform-compatibility/SKILL.md

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

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

@@ -2,6 +2,8 @@
 name: directory-structure
 description: "This skill enforces the…"
 ---
+This skill enforces the project's directory structure standards when creating or moving files. Use this skill when creating new components, screens, features, hooks, utilities, or any other code files to ensure they are placed in the correct location with proper naming conventions. Also use when reviewing file placement or restructuring code.
+
 
 # Directory Structure Enforcement
 

package/plugins/lisa-expo/.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-expo/.codex-plugin/skills/eas-update-insights/SKILL.md

@@ -5,6 +5,8 @@ version: 1.0.0
 license: MIT
 allowed-tools: "Bash(eas *)"
 ---
+Check the health of published EAS Updates: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel. Use when the user asks how an update is performing, whether a rollout is healthy, how many users are on the embedded build vs OTA, or wants to gate CI on update health.
+
 
 # EAS Update Insights
 

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

@@ -4,6 +4,8 @@ description: "Guidelines for creating API…"
 version: 1.0.0
 license: MIT
 ---
+Guidelines for creating API routes in Expo Router with EAS Hosting
+
 
 ## When to Use API Routes
 

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

@@ -2,6 +2,8 @@
 name: expo-brownfield
 description: "Integrate Expo and React Native…"
 ---
+Integrate Expo and React Native into an existing native iOS or Android app. Use when the user mentions brownfield, embedding React Native in a native app, AAR/XCFramework, or adding Expo to an existing Kotlin/Swift project. Covers both the isolated approach and the integrated approach.
+
 
 # Expo Brownfield
 

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

@@ -5,6 +5,8 @@ allowed-tools: "Read,Write,Bash(node:*)"
 version: 1.0.0
 license: MIT License
 ---
+Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation.
+
 
 # EAS Workflows Skill
 

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

@@ -4,6 +4,8 @@ description: "Deploying Expo apps to iOS App…"
 version: 1.0.0
 license: MIT
 ---
+Deploying Expo apps to iOS App Store, Android Play Store, web hosting, and API routes
+
 
 # Deployment
 

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

@@ -4,6 +4,8 @@ description: "Build and distribute Expo…"
 version: 1.0.0
 license: MIT
 ---
+Build and distribute Expo development clients locally or via TestFlight
+
 
 Use EAS Build to create development clients for testing native code changes on physical devices. Use this for creating custom Expo Go clients for testing branches of your app.
 

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

@@ -2,6 +2,8 @@
 name: expo-env-config
 description: "creating, modifying, or…"
 ---
+This skill should be used when creating, modifying, or accessing environment variables in this Expo/React Native codebase. It enforces type-safe, validated environment configuration using Zod schemas. Use this skill when adding new environment variables, setting up env validation, or writing code that reads from process.env.
+
 
 # Expo Environment Configuration
 

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

@@ -4,6 +4,8 @@ description: "Guide for creating and writing…"
 version: 1.0.0
 license: MIT
 ---
+Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript). Covers module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system. Use when building or modifying native modules for Expo.
+
 
 # Writing Expo Modules
 

package/plugins/lisa-expo/.codex-plugin/skills/expo-router-best-practices/SKILL.md

@@ -2,6 +2,8 @@
 name: expo-router-best-practices
 description: "creating new routes…"
 ---
+This skill should be used when creating new routes, configuring navigation layouts, implementing deep linking, or organizing the app/ directory structure in Expo Router projects. It provides best practices for file-based routing patterns.
+
 
 # Expo Router Best Practices
 

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

@@ -4,6 +4,8 @@ description: "Set up Tailwind CSS v4 in Expo…"
 version: 1.0.0
 license: MIT
 ---
+Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling
+
 
 # Tailwind CSS Setup for Expo with react-native-css
 

package/plugins/lisa-expo/.codex-plugin/skills/expo-ui-jetpack-compose/SKILL.md

@@ -2,6 +2,8 @@
 name: Expo UI Jetpack Compose
 description: "`@expo/ui/jetpack-compose`…"
 ---
+`@expo/ui/jetpack-compose` package lets you use Jetpack Compose Views and modifiers in your app.
+
 
 > The instructions in this skill apply to SDK 55 only. For other SDK versions, refer to the Expo UI Jetpack Compose docs for that version for the most accurate information.
 

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

@@ -2,6 +2,8 @@
 name: Expo UI SwiftUI
 description: "`@expo/ui/swift-ui` package…"
 ---
+`@expo/ui/swift-ui` package lets you use SwiftUI Views and modifiers in your app.
+
 
 > The instructions in this skill apply to SDK 55 only. For other SDK versions, refer to the Expo UI SwiftUI docs for that version for the most accurate information.
 

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

@@ -2,6 +2,8 @@
 name: gluestack-nativewind
 description: "This skill enforces Gluestack…"
 ---
+This skill enforces Gluestack UI v3 and NativeWind v4 design patterns for consistent, performant, and maintainable styling. It should be used when creating or reviewing components, fixing styling issues, or refactoring styles to follow the constrained design system.
+
 
 # Gluestack NativeWind Design Patterns
 

package/plugins/lisa-expo/.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, viewports, and assertions.
+
 
 # Add Validation Journey to Existing JIRA Ticket
 

package/plugins/lisa-expo/.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-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