@codyswann/lisa 1.0.2 → 1.0.5

package/README.md

@@ -389,6 +389,8 @@ Pre-built workflows for common tasks:
 | `/project:implement` | Execute all planned tasks |
 | `/project:review` | Run code review |
 | `/project:verify` | Run all quality checks |
+| `/project:reduce-max-lines` | Reduce max file lines threshold and fix violations |
+| `/project:reduce-max-lines-per-function` | Reduce max lines per function threshold and fix violations |
 | `/git:commit` | Create conventional commit |
 | `/git:submit-pr` | Create pull request |
 | `/lisa:review-implementation` | Compare project files against Lisa templates, upstream changes |

package/all/copy-overwrite/.claude/commands/project/fix-linter-error.md

@@ -1,15 +1,15 @@
 ---
-description: Fix all violations of a specific ESLint rule across the codebase
+description: Fix all violations of one or more ESLint rules across the codebase
 allowed-tools: Read, Write, Edit, Bash, Task, TaskCreate, TaskUpdate, TaskList, TaskGet
-argument-hint: <eslint-rule-name>
+argument-hint: <rule-1> [rule-2] [rule-3] ...
 model: sonnet
 ---
 
 # Fix Linter Errors
 
-Target rule: $ARGUMENTS
+Target rules: $ARGUMENTS
 
-If no argument provided, prompt the user for a lint rule name.
+Parse the arguments as space-separated ESLint rule names. If no arguments provided, prompt the user for at least one lint rule name.
 
 ## Setup
 
@@ -17,38 +17,71 @@ Check for active project: `cat .claude-active-project 2>/dev/null`
 
 If active, include `metadata: { "project": "<project-name>" }` in TaskCreate calls.
 
-## Step 1: Enable Rule
+## Step 1: Parse Rules
 
-Find the ESLint config and temporarily set `$ARGUMENTS` to `"error"` severity if not already.
+Split `$ARGUMENTS` into individual rule names (space-separated).
 
-## Step 2: Identify Violations
+Example inputs:
+- `sonarjs/cognitive-complexity` → 1 rule
+- `sonarjs/cognitive-complexity @typescript-eslint/no-explicit-any` → 2 rules
+- `react-hooks/exhaustive-deps import/order prefer-const` → 3 rules
 
-Run `npm run lint 2>&1 | grep "$ARGUMENTS"` and collect files with violations.
+## Step 2: Enable Rules
 
-## Step 3: Create Tasks
+For each rule, find the ESLint config and set it to `"error"` severity if not already enabled. NOTE: Make sure to scan for overrides that need to be changed too. For example eslint.config.local.ts.
 
-Create a task for each file with violations, ordered by violation count (highest first).
+## Step 3: Identify Violations
 
-Each task should include:
-- File path and violation count
+Run linting and collect violations for all target rules:
+
+```bash
+bun run lint 2>&1 | grep -E "(rule-1|rule-2|...)"
+```
+
+Group violations by:
+1. **Rule name** (primary grouping)
+2. **File path** (secondary grouping)
+
+Count violations per file per rule.
+
+## Step 4: Create Tasks
+
+Create tasks organized by rule, then by file:
+
+For each rule:
+- Create a parent task: "Fix all [rule-name] violations ([N] files, [M] total)"
+- Create child tasks for each file with violations, ordered by count (highest first)
+
+Each file task should include:
+- File path and violation count for that specific rule
 - Sample error messages
 - Fix approach based on rule type:
-  - **Complexity rules**: Extract functions, use early returns, simplify conditions
-  - **Style rules**: Apply formatting fixes
-  - **Best practice rules**: Refactor to follow recommended pattern
-  - **Type rules**: Add proper types, remove `any`
+  - **Complexity rules** (`sonarjs/*`): Extract functions, use early returns, simplify conditions
+  - **Style rules** (`prettier/*`, `import/order`): Apply formatting fixes
+  - **Best practice rules** (`react-hooks/*`, `prefer-const`): Refactor to follow recommended pattern
+  - **Type rules** (`@typescript-eslint/*`): Add proper types, remove `any`
 
-## Step 4: Execute
+## Step 5: Execute
 
-Launch up to 5 sub-agents to work through tasks in parallel.
+Process rules sequentially (to avoid conflicts), but parallelize file fixes within each rule:
 
-Each fix should be verified and committed before marking complete.
+For each rule:
+1. Launch up to 5 sub-agents to fix files for that rule in parallel
+2. Wait for all files to be fixed
+3. Run `bun run lint` to verify rule is now clean
+4. Commit all fixes for that rule with message: `fix(lint): resolve [rule-name] violations`
+5. Move to next rule
 
-## Step 5: Report
+## Step 6: Report
 
 ```
 Lint rule fix complete:
-- Rule: $ARGUMENTS
-- Files fixed: [N]
-- Total violations resolved: [M]
+
+| Rule | Files Fixed | Violations Resolved |
+|------|-------------|---------------------|
+| rule-1 | N1 | M1 |
+| rule-2 | N2 | M2 |
+| ... | ... | ... |
+
+Total: [N] files fixed, [M] violations resolved
 ```

package/all/copy-overwrite/.claude/commands/project/reduce-max-lines-per-function.md

@@ -0,0 +1,76 @@
+---
+description: Reduce max lines per function threshold and fix violations
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Task, TaskCreate, TaskUpdate, TaskList, TaskGet
+argument-hint: <max-lines-per-function-value>
+model: sonnet
+---
+
+# Reduce Max Lines Per Function
+
+Target threshold: $ARGUMENTS lines per function
+
+If no argument provided, prompt the user for a target.
+
+## Process
+
+### Step 0: Check Project Context
+
+Check if there's an active project for task syncing:
+
+```bash
+cat .claude-active-project 2>/dev/null
+```
+
+If a project is active, include `metadata: { "project": "<project-name>" }` in all TaskCreate calls.
+
+### Step 1: Locate Configuration
+
+Read the eslint thresholds config (`eslint.thresholds.json` or similar).
+
+### Step 2: Update Threshold
+
+Set the `maxLinesPerFunction` threshold to $ARGUMENTS (e.g., `"maxLinesPerFunction": $ARGUMENTS`).
+
+### Step 3: Identify Violations
+
+Run lint to find all functions exceeding the new threshold. Note file path, function name, and current line count.
+
+If no violations, report success and exit.
+
+### Step 4: Create Task List
+
+Create a task for each function needing refactoring, ordered by line count (highest first).
+
+Each task should have:
+- **subject**: "Reduce lines in [function-name]" (imperative form)
+- **description**: File path and line number, function name, current line count, target threshold, refactoring strategies
+- **activeForm**: "Reducing lines in [function-name]" (present continuous)
+- **metadata**: `{ "project": "<active-project>" }` if project context exists
+
+Refactoring strategies:
+- **Extract functions**: Break function into smaller named functions
+- **Early returns**: Reduce nesting with guard clauses
+- **Extract conditions**: Move complex boolean logic into named variables
+- **Use lookup tables**: Replace complex switch/if-else chains with object maps
+- **Consolidate logic**: Merge similar code paths
+
+### Step 5: Parallel Execution
+
+Launch **up to 5 sub-agents** using the `code-simplifier` subagent to refactor in parallel.
+
+### Step 6: Iterate
+
+Check for remaining pending tasks. Re-run lint to verify.
+
+If violations remain, repeat from Step 3.
+
+Continue until all functions meet or are under $ARGUMENTS lines.
+
+### Step 7: Report
+
+```
+Max lines per function reduction complete:
+- Target threshold: $ARGUMENTS
+- Functions refactored: [count]
+- Functions reduced: [list with line counts]
+```

package/all/copy-overwrite/.claude/commands/project/reduce-max-lines.md

@@ -0,0 +1,75 @@
+---
+description: Reduce max file lines threshold and fix violations
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Task, TaskCreate, TaskUpdate, TaskList, TaskGet
+argument-hint: <max-lines-value>
+model: sonnet
+---
+
+# Reduce Max Lines
+
+Target threshold: $ARGUMENTS lines per file
+
+If no argument provided, prompt the user for a target.
+
+## Process
+
+### Step 0: Check Project Context
+
+Check if there's an active project for task syncing:
+
+```bash
+cat .claude-active-project 2>/dev/null
+```
+
+If a project is active, include `metadata: { "project": "<project-name>" }` in all TaskCreate calls.
+
+### Step 1: Locate Configuration
+
+Read the eslint thresholds config (`eslint.thresholds.json` or similar).
+
+### Step 2: Update Threshold
+
+Set the `maxLines` threshold to $ARGUMENTS (e.g., `"maxLines": $ARGUMENTS`).
+
+### Step 3: Identify Violations
+
+Run lint to find all files exceeding the new threshold. Note file path and current line count.
+
+If no violations, report success and exit.
+
+### Step 4: Create Task List
+
+Create a task for each file needing refactoring, ordered by line count (highest first).
+
+Each task should have:
+- **subject**: "Reduce lines in [file]" (imperative form)
+- **description**: File path, current line count, target threshold, refactoring strategies
+- **activeForm**: "Reducing lines in [file]" (present continuous)
+- **metadata**: `{ "project": "<active-project>" }` if project context exists
+
+Refactoring strategies:
+- **Extract modules**: Break file into smaller focused modules
+- **Remove duplication**: Consolidate repeated logic
+- **Delete dead code**: Remove unused functions/code paths
+- **Simplify logic**: Use early returns, reduce nesting
+
+### Step 5: Parallel Execution
+
+Launch **up to 5 sub-agents** using the `code-simplifier` subagent to refactor in parallel.
+
+### Step 6: Iterate
+
+Check for remaining pending tasks. Re-run lint to verify.
+
+If violations remain, repeat from Step 3.
+
+Continue until all files meet or are under $ARGUMENTS lines.
+
+### Step 7: Report
+
+```
+Max lines reduction complete:
+- Target threshold: $ARGUMENTS
+- Files refactored: [count]
+- Files reduced: [list with line counts]
+```

package/all/copy-overwrite/HUMAN.md

@@ -80,6 +80,8 @@ Commands are organized by category. Sub-commands (commands that are called by ot
 | `/project:fix-linter-error` | Fix all violations of a specific ESLint rule | `<eslint-rule-name>` (required) | - |
 | `/project:lower-code-complexity` | Reduce code complexity threshold by 2 and fix violations | none | - |
 | `/project:add-test-coverage` | Increase test coverage to a specified threshold | `<threshold-percentage>` (required) | - |
+| `/project:reduce-max-lines` | Reduce max file lines threshold and fix violations | `<max-lines-value>` (required) | - |
+| `/project:reduce-max-lines-per-function` | Reduce max lines per function threshold and fix violations | `<max-lines-per-function-value>` (required) | - |
 
 ### Git Commands
 
@@ -330,6 +332,22 @@ Updates coverage config thresholds, identifies the 20 files with lowest coverage
 
 ---
 
+### `/project:reduce-max-lines`
+
+**Arguments:** `<max-lines-value>` (required)
+
+Reduces the max file lines threshold, identifies all files exceeding the new limit, creates tasks ordered by line count, and launches up to 5 code-simplifier agents to refactor in parallel. Iterates until all files meet or are under the target.
+
+---
+
+### `/project:reduce-max-lines-per-function`
+
+**Arguments:** `<max-lines-per-function-value>` (required)
+
+Reduces the max lines per function threshold, identifies all functions exceeding the new limit, creates tasks ordered by line count, and launches up to 5 code-simplifier agents to refactor in parallel. Iterates until all functions meet or are under the target.
+
+---
+
 ### `/git:commit`
 
 **Arguments:** `[commit-message-hint]` (optional)

package/expo/copy-overwrite/.github/workflows/deploy.yml

@@ -175,6 +175,22 @@ jobs:
         with:
           source: ".env.${{ needs.determine_environment.outputs.environment == 'dev' && 'development' || needs.determine_environment.outputs.environment }}"
           target: '.env.production'
+      - name: Copy amplify file (if exists)
+        run: |
+          ENV="${{ needs.determine_environment.outputs.environment }}"
+          if [ "$ENV" == "staging" ]; then
+            SOURCE_FILE="staging.aws-exports.js"
+          elif [ "$ENV" == "dev" ]; then
+            SOURCE_FILE="dev.aws-exports.js"
+          else
+            SOURCE_FILE="prod.aws-exports.js"
+          fi
+          if [ -f "$SOURCE_FILE" ]; then
+            cp "$SOURCE_FILE" aws-exports.js
+            echo "Copied $SOURCE_FILE to aws-exports.js"
+          else
+            echo "Skipping: $SOURCE_FILE does not exist"
+          fi
       - name: Get version for deploy message
         id: get_version
         run: |

package/package.json

@@ -75,7 +75,7 @@
     "@ast-grep/cli"
   ],
   "name": "@codyswann/lisa",
-  "version": "1.0.2",
+  "version": "1.0.5",
   "description": "Claude Code governance framework that applies guardrails, guidance, and automated enforcement to projects",
   "main": "dist/index.js",
   "bin": {