@codyswann/lisa 1.76.1 → 1.76.3

package/all/copy-overwrite/.claude/rules/base-rules.md

@@ -20,6 +20,7 @@ Code Quality:
 - Make atomic commits with clear conventional commit messages.
 - Create clear documentation preambles for new code. Update preambles when modifying existing code.
 - Document the "why", not the "what". Code explains what it does; documentation explains why it exists.
+- Always add new imports and their first usage in the same edit. The lint-on-edit hook runs `eslint --fix` after every Edit, which auto-removes unused imports. If you add an import in one edit and plan to use it in a second edit, the hook will strip the import before the second edit runs.
 - Add language specifiers to fenced code blocks in Markdown.
 - Use project-relative paths rather than absolute paths in documentation and Markdown.
 - Delete old code completely when replacing it. No deprecation unless specifically requested.

package/package.json

@@ -74,7 +74,7 @@
     "flatted": "^3.4.2"
   },
   "name": "@codyswann/lisa",
-  "version": "1.76.1",
+  "version": "1.76.3",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "exports": {
@@ -129,8 +129,8 @@
   "homepage": "https://github.com/CodySwannGT/lisa#readme",
   "dependencies": {
     "@ast-grep/cli": "^0.40.4",
-    "@commitlint/cli": "^20.3.1",
-    "@commitlint/config-conventional": "^20.3.1",
+    "@commitlint/cli": "^20.5.0",
+    "@commitlint/config-conventional": "^20.5.0",
     "@eslint-community/eslint-plugin-eslint-comments": "^4.5.0",
     "@eslint/eslintrc": "^3.2.0",
     "@eslint/js": "^9.39.0",
@@ -172,7 +172,7 @@
     "picocolors": "^1.0.0",
     "prettier": "^3.3.3",
     "standard-version": "^9.5.0",
-    "ts-jest": "^29.4.6",
+    "ts-jest": "^29.4.9",
     "ts-morph": "^27.0.2",
     "tsx": "^4.0.0",
     "typescript": "~5.7.0",

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

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

package/plugins/lisa/skills/nightly-lower-code-complexity/SKILL.md

@@ -17,9 +17,12 @@ The caller provides pre-computed context:
 1. Read CLAUDE.md and package.json for project conventions
 2. Update eslint.thresholds.json with the proposed new threshold values (do NOT change the maxLines threshold)
 3. Run the project's lint script with the provided package manager (e.g., `npm run lint`, `yarn lint`, or `bun run lint`) to find functions that violate the new stricter thresholds
-4. For cognitive complexity violations: use early returns, extract helper functions, replace conditionals with lookup tables
-5. For max-lines-per-function violations: split large functions, extract helper functions, separate concerns
-6. Re-run the lint script with the provided package manager to verify all violations are resolved
-7. Run the project's test script with the provided package manager (e.g., `npm run test`, `yarn test`, or `bun run test`) to verify no tests are broken by the refactoring
-8. Commit all changes (refactored code + updated eslint.thresholds.json) with conventional commit messages
-9. Create a PR with `gh pr create` with a title like "refactor: reduce code complexity: [metrics being reduced]" summarizing the changes
+4. **Before editing**, check each violating file's total line count (`wc -l`). If a file is within 20 lines of its `max-lines` ESLint limit (typically 300), extract helpers into a **separate companion file** (e.g., `fooHelpers.ts`) instead of adding them to the same file. Extracting functions into the same file adds net lines and can create new max-lines violations.
+5. Fix violations one file at a time. Read only the specific function that violates — do not pre-read all files upfront. Fix it, then move to the next.
+6. For cognitive complexity violations: use early returns, extract helper functions, replace conditionals with lookup tables
+7. For max-lines-per-function violations: split large functions, extract helper functions, separate concerns
+8. After each file edit, run the project's formatter (e.g., `bun run format` or `npx prettier --write <file>`) to ensure line counts reflect the final formatted state before moving on
+9. Re-run the lint script with the provided package manager to verify all violations are resolved (both the target metric AND max-lines)
+10. Run the project's test script with the provided package manager (e.g., `npm run test`, `yarn test`, or `bun run test`) to verify no tests are broken by the refactoring
+11. Commit all changes (refactored code + updated eslint.thresholds.json) with conventional commit messages
+12. Create a PR with `gh pr create` with a title like "refactor: reduce code complexity: [metrics being reduced]" summarizing the changes

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

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

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

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

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-nestjs",
-  "version": "1.76.1",
+  "version": "1.76.3",
   "description": "NestJS-specific skills (GraphQL, TypeORM)",
   "author": {
     "name": "Cody Swann"

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

@@ -1,6 +1,6 @@
 {
   "name": "lisa-rails",
-  "version": "1.76.1",
+  "version": "1.76.3",
   "description": "Ruby on Rails-specific hooks — RuboCop linting/formatting and ast-grep scanning on edit",
   "author": {
     "name": "Cody Swann"

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

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

package/plugins/src/base/skills/nightly-lower-code-complexity/SKILL.md

@@ -17,9 +17,12 @@ The caller provides pre-computed context:
 1. Read CLAUDE.md and package.json for project conventions
 2. Update eslint.thresholds.json with the proposed new threshold values (do NOT change the maxLines threshold)
 3. Run the project's lint script with the provided package manager (e.g., `npm run lint`, `yarn lint`, or `bun run lint`) to find functions that violate the new stricter thresholds
-4. For cognitive complexity violations: use early returns, extract helper functions, replace conditionals with lookup tables
-5. For max-lines-per-function violations: split large functions, extract helper functions, separate concerns
-6. Re-run the lint script with the provided package manager to verify all violations are resolved
-7. Run the project's test script with the provided package manager (e.g., `npm run test`, `yarn test`, or `bun run test`) to verify no tests are broken by the refactoring
-8. Commit all changes (refactored code + updated eslint.thresholds.json) with conventional commit messages
-9. Create a PR with `gh pr create` with a title like "refactor: reduce code complexity: [metrics being reduced]" summarizing the changes
+4. **Before editing**, check each violating file's total line count (`wc -l`). If a file is within 20 lines of its `max-lines` ESLint limit (typically 300), extract helpers into a **separate companion file** (e.g., `fooHelpers.ts`) instead of adding them to the same file. Extracting functions into the same file adds net lines and can create new max-lines violations.
+5. Fix violations one file at a time. Read only the specific function that violates — do not pre-read all files upfront. Fix it, then move to the next.
+6. For cognitive complexity violations: use early returns, extract helper functions, replace conditionals with lookup tables
+7. For max-lines-per-function violations: split large functions, extract helper functions, separate concerns
+8. After each file edit, run the project's formatter (e.g., `bun run format` or `npx prettier --write <file>`) to ensure line counts reflect the final formatted state before moving on
+9. Re-run the lint script with the provided package manager to verify all violations are resolved (both the target metric AND max-lines)
+10. Run the project's test script with the provided package manager (e.g., `npm run test`, `yarn test`, or `bun run test`) to verify no tests are broken by the refactoring
+11. Commit all changes (refactored code + updated eslint.thresholds.json) with conventional commit messages
+12. Create a PR with `gh pr create` with a title like "refactor: reduce code complexity: [metrics being reduced]" summarizing the changes