@codyswann/lisa 1.53.0 → 1.53.2

package/all/merge/.claude/settings.json

@@ -19,7 +19,8 @@
     "BASH_DEFAULT_TIMEOUT_MS": "1800000",
     "BASH_MAX_TIMEOUT_MS": "7200000",
     "CLAUDE_DEBUG": "0",
-    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
+    "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1",
+    "ENABLE_LSP_TOOL": "1"
   },
   "permissions": {
     "deny": ["Read(./.entire/metadata/**)"]

package/package.json

@@ -72,7 +72,7 @@
     "axios": ">=1.13.5"
   },
   "name": "@codyswann/lisa",
-  "version": "1.53.0",
+  "version": "1.53.2",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {

package/plugins/lisa-expo/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "expo-docs": {
+      "command": "npx",
+      "args": ["expo-local-docs-mcp"]
+    }
+  }
+}

package/plugins/lisa-rails/rules/lisa.md

@@ -6,15 +6,22 @@ The following files are managed by Lisa and will be overwritten on every `lisa`
 
 | Managed File (do not edit) | Local Override (edit this instead) |
 |---|---|
-| `eslint.config.ts` | `eslint.config.local.ts` |
-| `jest.config.ts` | `jest.config.local.ts` |
-| `tsconfig.json` | `tsconfig.local.json` |
+| `.rubocop.yml` | `.rubocop.local.yml` |
 
 ## Create-only files (edit freely, Lisa won't overwrite)
 
 - `.claude/rules/PROJECT_RULES.md`
-- `eslint.thresholds.json`
-- `jest.thresholds.json`
+- `.rubocop.local.yml`
+- `.simplecov`
+- `.reek.yml`
+- `.rspec`
+- `sonar-project.properties`
+- `spec/spec_helper.rb`
+- `spec/rails_helper.rb`
+- `.github/workflows/quality.yml`
+- `.github/workflows/ci.yml`
+- `.github/workflows/release.yml`
+- `VERSION`
 
 ## Deep-merged by Lisa (Lisa wins conflicts, but project can add its own keys)
 
@@ -22,16 +29,11 @@ The following files are managed by Lisa and will be overwritten on every `lisa`
 
 ## Plugin-managed content (agents, skills, hooks, commands, rules)
 
-These resources are distributed via the stack Claude Code plugin (e.g., `typescript@lisa`). Rules — including this file — are injected into each prompt automatically. Do not add these files to your project directory.
+These resources are distributed via the stack Claude Code plugin (`rails@lisa`). Rules — including this file — are injected into each prompt automatically. Do not add these files to your project directory.
 
 ## Copy-overwrite files (do not edit — full list)
 
-- `.prettierrc.json`, `.prettierignore`, `.lintstagedrc.json`, `.versionrc`, `.nvmrc`
-- `.yamllint`, `.gitleaksignore`, `.coderabbit.yml`, `commitlint.config.cjs`, `sgconfig.yml`, `knip.json`
-- `.safety-net.json`, `audit.ignore.config.json`
-- `eslint.base.ts`, `eslint.typescript.ts` (+ `expo`/`nestjs`/`cdk` variants), `eslint.slow.config.ts`
-- `jest.base.ts`, `jest.typescript.ts` (+ variants)
-- `tsconfig.base.json`, `tsconfig.typescript.json` (+ variants), `tsconfig.eslint.json`, `tsconfig.build.json`, `tsconfig.spec.json`
-- `.github/workflows/quality.yml`, `release.yml`, `claude.yml`, and all other Claude/CI workflows
-- `.github/dependabot.yml`, `.github/GITHUB_ACTIONS.md`
-- `ast-grep/rules/`, `ast-grep/utils/`, `ast-grep/rule-tests/`
+- `.safety-net.json`
+- `.rubocop.yml`, `.versionrc`, `lefthook.yml`, `Gemfile.lisa`
+- `config/initializers/version.rb`
+- `.coderabbit.yml`, `commitlint.config.cjs`

package/plugins/src/expo/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "expo-docs": {
+      "command": "npx",
+      "args": ["expo-local-docs-mcp"]
+    }
+  }
+}

package/{rails/copy-overwrite/.claude → plugins/src/rails}/rules/lisa.md

@@ -23,22 +23,17 @@ The following files are managed by Lisa and will be overwritten on every `lisa`
 - `.github/workflows/release.yml`
 - `VERSION`
 
-## Directories with both Lisa-managed and project content
+## Deep-merged by Lisa (Lisa wins conflicts, but project can add its own keys)
 
-These directories contain files deployed by Lisa **and** files you create. Do not edit or delete Lisa-managed files — they will be overwritten. You **can** freely add your own. Check `.lisa-manifest` to see which specific files Lisa manages.
+- `.claude/settings.json`
+
+## Plugin-managed content (agents, skills, hooks, commands, rules)
 
-- `.claude/skills/` — Add your own skill directories alongside Lisa's
-- `.claude/commands/` — Add your own command namespaces alongside Lisa's
-- `.claude/hooks/` — Add your own hook scripts alongside Lisa's
-- `.claude/agents/` — Add your own agent files alongside Lisa's
+These resources are distributed via the stack Claude Code plugin (`rails@lisa`). Rules — including this file — are injected into each prompt automatically. Do not add these files to your project directory.
 
-## Files and directories with NO local override (do not edit at all)
+## Copy-overwrite files (do not edit — full list)
 
-- `.claude/rules/coding-philosophy.md`, `.claude/rules/plan.md`, `.claude/rules/verfication.md`
-- `.claude/rules/rails-conventions.md`
-- `CLAUDE.md`, `HUMAN.md`, `.safety-net.json`
+- `.safety-net.json`
 - `.rubocop.yml`, `.versionrc`, `lefthook.yml`, `Gemfile.lisa`
 - `config/initializers/version.rb`
 - `.coderabbit.yml`, `commitlint.config.cjs`
-- `.claude/settings.json`
-- `.claude/README.md`, `.claude/REFERENCE.md`

package/typescript/create-only/.github/workflows/claude-ci-auto-fix.yml

@@ -8,6 +8,13 @@ on:
     workflows: ['CI Quality Checks']
     types: [completed]
 
+permissions:
+  actions: read
+  contents: write
+  issues: write
+  pull-requests: write
+  id-token: write
+
 jobs:
   auto-fix:
     uses: CodySwannGT/lisa/.github/workflows/reusable-claude-ci-auto-fix.yml@main

package/typescript/create-only/.github/workflows/claude-code-review-response.yml

@@ -7,6 +7,14 @@ on:
   pull_request_review:
     types: [submitted]
 
+permissions:
+  actions: write
+  checks: write
+  contents: write
+  issues: write
+  pull-requests: write
+  id-token: write
+
 jobs:
   respond-to-review:
     uses: CodySwannGT/lisa/.github/workflows/reusable-claude-code-review-response.yml@main

package/typescript/create-only/.github/workflows/claude-deploy-auto-fix.yml

@@ -8,6 +8,13 @@ on:
     workflows: ['Release and Deploy', '🚀 Release and Deploy']
     types: [completed]
 
+permissions:
+  actions: read
+  contents: write
+  issues: write
+  pull-requests: write
+  id-token: write
+
 jobs:
   auto-fix:
     uses: CodySwannGT/lisa/.github/workflows/reusable-claude-deploy-auto-fix.yml@main

package/typescript/create-only/.github/workflows/claude-nightly-code-complexity.yml

@@ -8,6 +8,12 @@ on:
     - cron: '0 5 * * 1-5'
   workflow_dispatch:
 
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+  id-token: write
+
 jobs:
   reduce-complexity:
     uses: CodySwannGT/lisa/.github/workflows/reusable-claude-nightly-code-complexity.yml@main

package/typescript/create-only/.github/workflows/claude-nightly-test-coverage.yml

@@ -8,6 +8,12 @@ on:
     - cron: '0 4 * * 1-5'
   workflow_dispatch:
 
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+  id-token: write
+
 jobs:
   improve-coverage:
     uses: CodySwannGT/lisa/.github/workflows/reusable-claude-nightly-test-coverage.yml@main

package/typescript/create-only/.github/workflows/claude-nightly-test-improvement.yml

@@ -17,6 +17,12 @@ on:
           - nightly
           - general
 
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+  id-token: write
+
 jobs:
   improve-tests:
     uses: CodySwannGT/lisa/.github/workflows/reusable-claude-nightly-test-improvement.yml@main

package/typescript/create-only/.github/workflows/claude.yml

@@ -13,6 +13,13 @@ on:
   pull_request_review:
     types: [submitted]
 
+permissions:
+  actions: read
+  contents: write
+  issues: write
+  pull-requests: write
+  id-token: write
+
 jobs:
   claude:
     uses: CodySwannGT/lisa/.github/workflows/reusable-claude.yml@main

package/cdk/copy-overwrite/README.md

@@ -1,81 +0,0 @@
-# CDK
-
-Developers write specs and answer questions. Agents implement, test, verify, question, and document.
-
-## About This Project
-
-> Ask Claude: "What is the purpose of this project and how does it work?"
-
-## Step 1: Install Claude Code
-
-```bash
-brew install claude-code
-# Or: npm install -g @anthropic-ai/claude-code
-```
-
-## Step 2: Set Up This Project
-
-> Ask Claude: "I just cloned this repo. Walk me through the full setup including installing dependencies, environment variables, and any other configuration."
-
-## Step 3: Verify the Infrastructure
-
-> Ask Claude: "How do I synthesize the CDK stacks and verify the templates are valid?"
-
-## Step 4: Work on a Feature
-
-> Ask Claude: "I have Jira ticket [TICKET-ID]. Research the codebase, create a plan, and implement it."
-
-Or use utility commands:
-
-- `/plan:add-test-coverage` - Increase test coverage to a threshold
-- `/plan:fix-linter-error` - Fix ESLint rule violations
-- `/plan:local-code-review` - Review local branch changes
-- `/plan:lower-code-complexity` - Reduce cognitive complexity
-- `/plan:reduce-max-lines` - Reduce max file lines threshold
-- `/plan:reduce-max-lines-per-function` - Reduce max function lines
-
-## Lisa Commands
-
-> Ask Claude: "What Lisa commands are available and how do I use them? Read HUMAN.md and give me a summary."
-
-## Common Tasks
-
-### Code Review
-
-> Ask Claude: "Review the changes on this branch and suggest improvements."
-
-### Submit a PR
-
-> Ask Claude: "Commit my changes and open a pull request."
-
-### Fix Lint Errors
-
-> Ask Claude: "Run the linter and fix all errors."
-
-### Add Test Coverage
-
-> Ask Claude: "Increase test coverage for the files I changed."
-
-### Synthesize CloudFormation Templates
-
-> Ask Claude: "Run CDK synth and verify the CloudFormation templates are generated correctly."
-
-### Diff Against Deployed Stacks
-
-> Ask Claude: "Run CDK diff to show what changes would be deployed compared to the current stacks."
-
-### Deploy
-
-> Ask Claude: "Walk me through deploying this project."
-
-## Project Standards
-
-> Ask Claude: "What coding standards and conventions does this project follow?"
-
-## Architecture
-
-> Ask Claude: "Explain the architecture of this project, including key components and how they interact."
-
-## Troubleshooting
-
-> Ask Claude: "I'm having an issue with [describe problem]. Help me debug it."

package/expo/copy-overwrite/.mcp.json

@@ -1,25 +0,0 @@
-{
-  "mcpServers": {
-    "expo-docs": {
-      "command": "npx",
-      "args": ["expo-local-docs-mcp"]
-    },
-    "sonarqube": {
-      "command": "docker",
-      "args": [
-        "run",
-        "-i",
-        "--rm",
-        "-e",
-        "SONARQUBE_TOKEN",
-        "-e",
-        "SONARQUBE_ORG",
-        "mcp/sonarqube"
-      ],
-      "env": {
-        "SONARQUBE_TOKEN": "${SONAR_TOKEN}",
-        "SONARQUBE_ORG": "${SONAR_ORG}"
-      }
-    }
-  }
-}

package/expo/copy-overwrite/README.md

@@ -1,89 +0,0 @@
-# Expo
-
-Developers write specs and answer questions. Agents implement, test, verify, question, and document.
-
-## About This Project
-
-> Ask Claude: "What is the purpose of this project and how does it work?"
-
-## Step 1: Install Claude Code
-
-```bash
-brew install claude-code
-# Or: npm install -g @anthropic-ai/claude-code
-```
-
-## Step 2: Set Up This Project
-
-> Ask Claude: "I just cloned this repo. Walk me through the full setup including installing dependencies, environment variables, and any other configuration."
-
-## Step 3: Run the App Locally
-
-> Ask Claude: "How do I start the app locally? Walk me through the steps and verify it's running."
-
-## Step 4: Work on a Feature
-
-> Ask Claude: "I have Jira ticket [TICKET-ID]. Research the codebase, create a plan, and implement it."
-
-Or use utility commands:
-
-- `/plan:add-test-coverage` - Increase test coverage to a threshold
-- `/plan:fix-linter-error` - Fix ESLint rule violations
-- `/plan:local-code-review` - Review local branch changes
-- `/plan:lower-code-complexity` - Reduce cognitive complexity
-- `/plan:reduce-max-lines` - Reduce max file lines threshold
-- `/plan:reduce-max-lines-per-function` - Reduce max function lines
-
-## Lisa Commands
-
-> Ask Claude: "What Lisa commands are available and how do I use them? Read HUMAN.md and give me a summary."
-
-## Common Tasks
-
-### Code Review
-
-> Ask Claude: "Review the changes on this branch and suggest improvements."
-
-### Submit a PR
-
-> Ask Claude: "Commit my changes and open a pull request."
-
-### Fix Lint Errors
-
-> Ask Claude: "Run the linter and fix all errors."
-
-### Add Test Coverage
-
-> Ask Claude: "Increase test coverage for the files I changed."
-
-### Run on iOS
-
-> Ask Claude: "Start the app on the iOS simulator and verify it launches correctly."
-
-### Run on Android
-
-> Ask Claude: "Start the app on the Android emulator and verify it launches correctly."
-
-### Run on Web
-
-> Ask Claude: "Start the app in a web browser and verify it loads correctly."
-
-### Generate Types After Schema Changes
-
-> Ask Claude: "The API schema has changed. Regenerate types and fix any resulting type errors."
-
-### Deploy
-
-> Ask Claude: "Walk me through deploying this project."
-
-## Project Standards
-
-> Ask Claude: "What coding standards and conventions does this project follow?"
-
-## Architecture
-
-> Ask Claude: "Explain the architecture of this project, including key components and how they interact."
-
-## Troubleshooting
-
-> Ask Claude: "I'm having an issue with [describe problem]. Help me debug it."

package/nestjs/copy-overwrite/README.md

@@ -1,81 +0,0 @@
-# NestJS
-
-Developers write specs and answer questions. Agents implement, test, verify, question, and document.
-
-## About This Project
-
-> Ask Claude: "What is the purpose of this project and how does it work?"
-
-## Step 1: Install Claude Code
-
-```bash
-brew install claude-code
-# Or: npm install -g @anthropic-ai/claude-code
-```
-
-## Step 2: Set Up This Project
-
-> Ask Claude: "I just cloned this repo. Walk me through the full setup including installing dependencies, environment variables, and any other configuration."
-
-## Step 3: Run the App Locally
-
-> Ask Claude: "How do I start the app locally? Walk me through the steps and verify it's running."
-
-## Step 4: Work on a Feature
-
-> Ask Claude: "I have Jira ticket [TICKET-ID]. Research the codebase, create a plan, and implement it."
-
-Or use utility commands:
-
-- `/plan:add-test-coverage` - Increase test coverage to a threshold
-- `/plan:fix-linter-error` - Fix ESLint rule violations
-- `/plan:local-code-review` - Review local branch changes
-- `/plan:lower-code-complexity` - Reduce cognitive complexity
-- `/plan:reduce-max-lines` - Reduce max file lines threshold
-- `/plan:reduce-max-lines-per-function` - Reduce max function lines
-
-## Lisa Commands
-
-> Ask Claude: "What Lisa commands are available and how do I use them? Read HUMAN.md and give me a summary."
-
-## Common Tasks
-
-### Code Review
-
-> Ask Claude: "Review the changes on this branch and suggest improvements."
-
-### Submit a PR
-
-> Ask Claude: "Commit my changes and open a pull request."
-
-### Fix Lint Errors
-
-> Ask Claude: "Run the linter and fix all errors."
-
-### Add Test Coverage
-
-> Ask Claude: "Increase test coverage for the files I changed."
-
-### Run Database Migrations
-
-> Ask Claude: "Run pending database migrations and verify the schema is up to date."
-
-### Test API Endpoints
-
-> Ask Claude: "How do I test the API endpoints locally?"
-
-### Deploy
-
-> Ask Claude: "Walk me through deploying this project."
-
-## Project Standards
-
-> Ask Claude: "What coding standards and conventions does this project follow?"
-
-## Architecture
-
-> Ask Claude: "Explain the architecture of this project, including key components and how they interact."
-
-## Troubleshooting
-
-> Ask Claude: "I'm having an issue with [describe problem]. Help me debug it."

package/rails/copy-overwrite/.claude/rules/rails-conventions.md

@@ -1,176 +0,0 @@
-# Rails Coding Conventions
-
-This rule enforces Rails-specific coding standards for consistency, maintainability, and performance.
-
-## Fat Models, Skinny Controllers
-
-Controllers handle HTTP concerns only. Business logic belongs in models or service objects.
-
-```ruby
-# Correct — controller delegates to model
-class OrdersController < ApplicationController
-  def create
-    @order = Order.place(order_params, current_user)
-    redirect_to @order
-  end
-end
-
-# Wrong — business logic in controller
-class OrdersController < ApplicationController
-  def create
-    @order = Order.new(order_params)
-    @order.user = current_user
-    @order.total = @order.line_items.sum(&:price)
-    @order.apply_discount(current_user.discount_rate)
-    @order.save!
-    OrderMailer.confirmation(@order).deliver_later
-    redirect_to @order
-  end
-end
-```
-
-## Service Objects
-
-Extract complex business logic into service objects when a model method would be too large or spans multiple models.
-
-```ruby
-# app/services/order_placement_service.rb
-class OrderPlacementService
-  def initialize(user:, params:)
-    @user = user
-    @params = params
-  end
-
-  def call
-    order = Order.new(@params)
-    order.user = @user
-    order.calculate_total
-    order.save!
-    OrderMailer.confirmation(order).deliver_later
-    order
-  end
-end
-```
-
-## Concerns
-
-Use concerns to share behavior across models or controllers. Keep concerns focused on a single responsibility.
-
-```ruby
-# app/models/concerns/searchable.rb
-module Searchable
-  extend ActiveSupport::Concern
-
-  included do
-    scope :search, ->(query) { where("name ILIKE ?", "%#{query}%") }
-  end
-end
-```
-
-## ActiveRecord Patterns
-
-### Scopes over class methods for chainable queries
-
-```ruby
-# Correct — scope
-scope :active, -> { where(active: true) }
-scope :recent, -> { order(created_at: :desc) }
-
-# Wrong — class method for simple query
-def self.active
-  where(active: true)
-end
-```
-
-### Validations
-
-```ruby
-# Use built-in validators
-validates :email, presence: true, uniqueness: true, format: { with: URI::MailTo::EMAIL_REGEXP }
-validates :age, numericality: { greater_than: 0 }
-```
-
-### Callbacks — use sparingly
-
-Prefer explicit service objects over callbacks for complex side effects. Callbacks are acceptable for simple data normalization.
-
-```ruby
-# Acceptable — simple normalization
-before_validation :normalize_email
-
-private
-
-def normalize_email
-  self.email = email&.downcase&.strip
-end
-```
-
-## N+1 Query Prevention
-
-Always use `includes`, `preload`, or `eager_load` to prevent N+1 queries. The Bullet gem is included to detect these in development.
-
-```ruby
-# Correct — eager loading
-@posts = Post.includes(:author, :comments).where(published: true)
-
-# Wrong — N+1 query
-@posts = Post.where(published: true)
-@posts.each { |post| post.author.name } # N+1!
-```
-
-## Strong Parameters
-
-Always use strong parameters in controllers. Never use `permit!`.
-
-```ruby
-# Correct
-def order_params
-  params.require(:order).permit(:product_id, :quantity, :notes)
-end
-
-# Wrong — permits everything
-def order_params
-  params.require(:order).permit!
-end
-```
-
-## Database Migrations
-
-- Use `strong_migrations` gem constraints (included via Gemfile.lisa)
-- Never modify `db/schema.rb` directly
-- Always add indexes for foreign keys and commonly queried columns
-- Use `change` method when the migration is reversible; use `up`/`down` when it is not
-
-```ruby
-class AddIndexToOrdersUserId < ActiveRecord::Migration[7.2]
-  def change
-    add_index :orders, :user_id
-  end
-end
-```
-
-## Testing with RSpec
-
-- Use `let` and `let!` for test setup
-- Use `described_class` instead of repeating the class name
-- Use `factory_bot` for test data, not fixtures
-- Use `shoulda-matchers` for model validation tests
-- Keep tests focused — one assertion concept per example
-
-```ruby
-RSpec.describe Order, type: :model do
-  describe "validations" do
-    it { is_expected.to validate_presence_of(:user) }
-    it { is_expected.to validate_numericality_of(:total).is_greater_than(0) }
-  end
-
-  describe ".recent" do
-    it "returns orders in descending creation order" do
-      old_order = create(:order, created_at: 1.day.ago)
-      new_order = create(:order, created_at: 1.hour.ago)
-
-      expect(described_class.recent).to eq([new_order, old_order])
-    end
-  end
-end
-```