@codyswann/lisa 1.18.0 → 1.19.0

package/all/copy-overwrite/.claude/commands/plan/add-test-coverage.md

@@ -0,0 +1,8 @@
+---
+description: "Increase test coverage to a specified threshold percentage"
+allowed-tools: ["Skill"]
+argument-hint: "<threshold-percentage>"
+
+---
+
+Use the /plan-add-test-coverage skill to increase test coverage. $ARGUMENTS

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

@@ -0,0 +1,8 @@
+---
+description: "Fix all violations of one or more ESLint rules across the codebase"
+allowed-tools: ["Skill"]
+argument-hint: "<rule-1> [rule-2] [rule-3] ..."
+
+---
+
+Use the /plan-fix-linter-error skill to fix linter errors. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/plan/local-code-review.md

@@ -0,0 +1,6 @@
+---
+description: "Review local branch changes compared to main"
+allowed-tools: ["Skill"]
+---
+
+Use the /plan-local-code-review skill to review local changes.

package/all/copy-overwrite/.claude/commands/plan/lower-code-complexity.md

@@ -0,0 +1,6 @@
+---
+description: "Reduce the cognitive complexity threshold by 2 and fix all violations"
+allowed-tools: ["Skill"]
+---
+
+Use the /plan-lower-code-complexity skill to lower code complexity.

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

@@ -0,0 +1,8 @@
+---
+description: "Reduce max lines per function threshold and fix violations"
+allowed-tools: ["Skill"]
+argument-hint: "<max-lines-per-function-value>"
+
+---
+
+Use the /plan-reduce-max-lines-per-function skill to reduce max function lines. $ARGUMENTS

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

@@ -0,0 +1,8 @@
+---
+description: "Reduce max file lines threshold and fix violations"
+allowed-tools: ["Skill"]
+argument-hint: "<max-lines-value>"
+
+---
+
+Use the /plan-reduce-max-lines skill to reduce max lines. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/add-test-coverage.md

@@ -2,7 +2,10 @@
 description: "Increase test coverage to a specified threshold percentage"
 allowed-tools: ["Skill"]
 argument-hint: "<threshold-percentage>"
-model: sonnet
+
 ---
 
+> **DEPRECATED**: This command is deprecated. Use `/plan:add-test-coverage` instead.
+> This command will be removed in a future release.
+
 Use the /project-add-test-coverage skill to increase test coverage. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/archive.md

@@ -4,4 +4,8 @@ allowed-tools: ["Skill"]
 argument-hint: "<project-directory>"
 ---
 
+> **DEPRECATED**: This command is deprecated. Use Claude's native plan mode instead.
+> Enter plan mode with `/plan`, describe your requirements, and Claude will create a plan with tasks automatically.
+> This command will be removed in a future release.
+
 Use the /project-archive skill to archive the completed project. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/bootstrap.md

@@ -4,4 +4,8 @@ allowed-tools: ["Skill"]
 argument-hint: "<file-path|jira-issue|\"text description\">"
 ---
 
+> **DEPRECATED**: This command is deprecated. Use Claude's native plan mode instead.
+> Enter plan mode with `/plan`, describe your requirements, and Claude will create a plan with tasks automatically.
+> This command will be removed in a future release.
+
 Use the /project-bootstrap skill to set up, research, and execute a project. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/debrief.md

@@ -4,4 +4,8 @@ allowed-tools: ["Skill"]
 argument-hint: "<project-directory>"
 ---
 
+> **DEPRECATED**: This command is deprecated. Use Claude's native plan mode instead.
+> Enter plan mode with `/plan`, describe your requirements, and Claude will create a plan with tasks automatically.
+> This command will be removed in a future release.
+
 Use the /project-debrief skill to aggregate and apply project learnings. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/document.md

@@ -4,4 +4,8 @@ allowed-tools: ["Skill"]
 argument-hint: "<project-directory>"
 ---
 
+> **DEPRECATED**: This command is deprecated. Use Claude's native plan mode instead.
+> Enter plan mode with `/plan`, describe your requirements, and Claude will create a plan with tasks automatically.
+> This command will be removed in a future release.
+
 Use the /project-document skill to update all project documentation. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/execute.md

@@ -4,4 +4,8 @@ allowed-tools: ["Skill"]
 argument-hint: "<project-directory>"
 ---
 
+> **DEPRECATED**: This command is deprecated. Use Claude's native plan mode instead.
+> Enter plan mode with `/plan`, describe your requirements, and Claude will create a plan with tasks automatically.
+> This command will be removed in a future release.
+
 Use the /project-execute skill to run the complete project workflow. $ARGUMENTS

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

@@ -2,7 +2,10 @@
 description: "Fix all violations of one or more ESLint rules across the codebase"
 allowed-tools: ["Skill"]
 argument-hint: "<rule-1> [rule-2] [rule-3] ..."
-model: sonnet
+
 ---
 
+> **DEPRECATED**: This command is deprecated. Use `/plan:fix-linter-error` instead.
+> This command will be removed in a future release.
+
 Use the /project-fix-linter-error skill to fix ESLint rule violations. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/implement.md

@@ -4,4 +4,8 @@ allowed-tools: ["Skill"]
 argument-hint: "<project-directory>"
 ---
 
+> **DEPRECATED**: This command is deprecated. Use Claude's native plan mode instead.
+> Enter plan mode with `/plan`, describe your requirements, and Claude will create a plan with tasks automatically.
+> This command will be removed in a future release.
+
 Use the /project-implement skill to implement all planned tasks. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/local-code-review.md

@@ -4,4 +4,7 @@ allowed-tools: ["Skill"]
 argument-hint: "<project-directory>"
 ---
 
+> **DEPRECATED**: This command is deprecated. Use `/plan:local-code-review` instead.
+> This command will be removed in a future release.
+
 Use the /project-local-code-review skill to review local changes on the current branch. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/lower-code-complexity.md

@@ -3,4 +3,7 @@ description: "Reduces the code complexity of the codebase by 2 on each run"
 allowed-tools: ["Skill"]
 ---
 
+> **DEPRECATED**: This command is deprecated. Use `/plan:lower-code-complexity` instead.
+> This command will be removed in a future release.
+
 Use the /project-lower-code-complexity skill to reduce cognitive complexity. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/plan.md

@@ -4,4 +4,8 @@ allowed-tools: ["Skill"]
 argument-hint: "<project-directory>"
 ---
 
+> **DEPRECATED**: This command is deprecated. Use Claude's native plan mode instead.
+> Enter plan mode with `/plan`, describe your requirements, and Claude will create a plan with tasks automatically.
+> This command will be removed in a future release.
+
 Use the /project-plan skill to create implementation tasks from research and brief. $ARGUMENTS

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

@@ -2,7 +2,10 @@
 description: "Reduce max lines per function threshold and fix violations"
 allowed-tools: ["Skill"]
 argument-hint: "<max-lines-per-function-value>"
-model: sonnet
+
 ---
 
+> **DEPRECATED**: This command is deprecated. Use `/plan:reduce-max-lines-per-function` instead.
+> This command will be removed in a future release.
+
 Use the /project-reduce-max-lines-per-function skill to reduce function line limits. $ARGUMENTS

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

@@ -2,7 +2,10 @@
 description: "Reduce max file lines threshold and fix violations"
 allowed-tools: ["Skill"]
 argument-hint: "<max-lines-value>"
-model: sonnet
+
 ---
 
+> **DEPRECATED**: This command is deprecated. Use `/plan:reduce-max-lines` instead.
+> This command will be removed in a future release.
+
 Use the /project-reduce-max-lines skill to reduce file line limits. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/research.md

@@ -4,4 +4,8 @@ allowed-tools: ["Skill"]
 argument-hint: "<project-directory>"
 ---
 
+> **DEPRECATED**: This command is deprecated. Use Claude's native plan mode instead.
+> Enter plan mode with `/plan`, describe your requirements, and Claude will create a plan with tasks automatically.
+> This command will be removed in a future release.
+
 Use the /project-research skill to conduct comprehensive research for the project. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/review.md

@@ -4,4 +4,8 @@ allowed-tools: ["Skill"]
 argument-hint: "<project-directory>"
 ---
 
+> **DEPRECATED**: This command is deprecated. Use Claude's native plan mode instead.
+> Enter plan mode with `/plan`, describe your requirements, and Claude will create a plan with tasks automatically.
+> This command will be removed in a future release.
+
 Use the /project-review skill to perform code review and optimization. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/setup.md

@@ -4,4 +4,8 @@ allowed-tools: ["Skill"]
 argument-hint: "<file-path|jira-issue|text-description>"
 ---
 
+> **DEPRECATED**: This command is deprecated. Use Claude's native plan mode instead.
+> Enter plan mode with `/plan`, describe your requirements, and Claude will create a plan with tasks automatically.
+> This command will be removed in a future release.
+
 Use the /project-setup skill to initialize a new project. $ARGUMENTS

package/all/copy-overwrite/.claude/commands/project/verify.md

@@ -4,4 +4,8 @@ allowed-tools: ["Skill"]
 argument-hint: "<project-directory>"
 ---
 
+> **DEPRECATED**: This command is deprecated. Use Claude's native plan mode instead.
+> Enter plan mode with `/plan`, describe your requirements, and Claude will create a plan with tasks automatically.
+> This command will be removed in a future release.
+
 Use the /project-verify skill to verify the project implementation. $ARGUMENTS

package/all/copy-overwrite/.claude/skills/plan-add-test-coverage/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: plan-add-test-coverage
+description: This skill should be used when increasing test coverage to a specified threshold percentage. It runs the coverage report, identifies files with the lowest coverage, generates a brief with coverage gaps, and creates a plan with tasks to add the missing tests.
+allowed-tools: ["Read", "Bash", "Glob", "Grep"]
+argument-hint: "<threshold-percentage>"
+
+---
+
+# Increase Test Coverage
+
+Target threshold: $ARGUMENTS%
+
+If no argument provided, prompt the user for a target.
+
+## Step 1: Gather Requirements
+
+1. **Find coverage config** (jest.config.js, vitest.config.ts, .nycrc, etc.)
+2. **Run coverage report** to get current state:
+   ```bash
+   bun run test:cov 2>&1 | head -100
+   ```
+3. **Identify the 20 files with lowest coverage**, noting:
+   - File path
+   - Current coverage % (lines, branches, functions)
+   - Which lines/branches are uncovered
+
+## Step 2: Create Plan
+
+In plan mode, create a plan that includes the following details:
+
+```markdown
+Increase test coverage from [current]% to $ARGUMENTS%.
+
+## Files Needing Coverage (ordered by coverage gap)
+
+1. src/services/user.ts - 23% coverage (target: $ARGUMENTS%)
+   - Uncovered: lines 45-67, 89-102
+   - Missing branch coverage: lines 34, 56
+2. src/utils/helpers.ts - 34% coverage (target: $ARGUMENTS%)
+   - Uncovered: lines 12-45
+...
+
+## Configuration
+- Config file: [path to coverage config]
+- Update thresholds to $ARGUMENTS% for: lines, branches, functions, statements
+
+## Acceptance Criteria
+- All files meet $ARGUMENTS% coverage threshold
+- `bun run test:cov` passes with no threshold violations
+
+## Verification
+Command: `bun run test:cov`
+Expected: All thresholds pass at $ARGUMENTS%
+```

package/all/copy-overwrite/.claude/skills/plan-fix-linter-error/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: plan-fix-linter-error
+description: This skill should be used when fixing all violations of one or more ESLint rules across the codebase. It runs the linter, groups violations by rule and file, generates a brief with fix strategies, and creates a plan with tasks to implement the fixes.
+allowed-tools: ["Read", "Bash", "Glob", "Grep"]
+argument-hint: "<rule-1> [rule-2] [rule-3] ..."
+
+---
+
+# Fix Linter Errors
+
+Target rules: $ARGUMENTS
+
+If no arguments provided, prompt the user for at least one lint rule name.
+
+## Step 1: Gather Requirements
+
+1. **Parse rules** from $ARGUMENTS (space-separated)
+2. **Run linter** to collect all violations:
+   ```bash
+   bun run lint 2>&1
+   ```
+3. **Group violations** by rule, then by file, noting:
+   - File path and line numbers
+   - Violation count per file
+   - Sample error messages
+
+## Step 2: Create Plan
+
+In plan mode, create a plan that includes the following details:
+
+```markdown
+Fix ESLint violations for rules: $ARGUMENTS
+
+## Violations by Rule
+
+### [rule-name-1] (X total violations across Y files)
+
+1. src/services/user.ts (5 violations)
+   - Line 23: [error message]
+   - Line 45: [error message]
+   - Line 67: [error message]
+   ...
+2. src/utils/helpers.ts (3 violations)
+   - Line 12: [error message]
+   ...
+
+### [rule-name-2] (X total violations across Y files)
+...
+
+## Fix Strategies
+- **Complexity rules** (sonarjs/*): Extract functions, early returns, simplify conditions
+- **Style rules** (prettier/*, import/order): Apply formatting fixes
+- **Best practice rules** (react-hooks/*, prefer-const): Refactor to recommended pattern
+- **Type rules** (@typescript-eslint/*): Add proper types, remove `any`
+
+## Acceptance Criteria
+- `bun run lint` passes with zero violations for: $ARGUMENTS
+- Each rule's fixes committed separately: `fix(lint): resolve [rule-name] violations`
+
+## Verification
+Command: `bun run lint 2>&1 | grep -E "($ARGUMENTS)" | wc -l`
+Expected: 0
+```

package/all/copy-overwrite/.claude/skills/plan-local-code-review/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: plan-local-code-review
+description: This skill should be used when performing a code review on local changes on the current branch compared to the main branch. It uses multiple parallel agents to check for bugs, CLAUDE.md compliance, git history context, previous PR comments, and code comment adherence, then scores and filters findings by confidence level.
+disable-model-invocation: false
+---
+
+Provide a code review for the local changes on the current branch compared to the main branch.
+
+To do this, follow these steps precisely:
+
+1. Use a Haiku agent to check the current git state:
+   - Run `git branch --show-current` to get the current branch name
+   - Run `git log main..HEAD --oneline` to see commits on this branch
+   - Run `git diff main...HEAD --stat` to see changed files
+   - If the current branch IS main, or there are no commits/changes compared to main, do not proceed.
+2. Use another Haiku agent to give you a list of file paths to (but not the contents of) any relevant CLAUDE.md files from the codebase: the root CLAUDE.md file (if one exists), as well as any CLAUDE.md files in the directories whose files were modified on this branch
+3. Use a Haiku agent to analyze the branch changes:
+   - Run `git log main..HEAD --format="%s%n%b"` to get commit messages
+   - Run `git diff main...HEAD` to get the full diff
+   - Return a summary of the changes
+4. Then, launch 5 parallel Sonnet agents to independently code review the change. The agents should do the following, then return a list of issues and the reason each issue was flagged (eg. CLAUDE.md adherence, bug, historical git context, etc.):
+   a. Agent #1: Audit the changes to make sure they comply with the CLAUDE.md. Note that CLAUDE.md is guidance for Claude as it writes code, so not all instructions will be applicable during code review.
+   b. Agent #2: Read the file changes (via `git diff main...HEAD`), then do a shallow scan for obvious bugs. Avoid reading extra context beyond the changes, focusing just on the changes themselves. Focus on large bugs, and avoid small issues and nitpicks. Ignore likely false positives.
+   c. Agent #3: Read the git blame and history of the code modified, to identify any bugs in light of that historical context
+   d. Agent #4: Read previous pull requests that touched these files, and check for any comments on those pull requests that may also apply to the current changes.
+   e. Agent #5: Read code comments in the modified files, and make sure the changes comply with any guidance in the comments.
+5. For each issue found in #4, launch a parallel Haiku agent that takes the diff, issue description, and list of CLAUDE.md files (from step 2), and returns a score to indicate the agent's level of confidence for whether the issue is real or false positive. To do that, the agent should score each issue on a scale from 0-100, indicating its level of confidence. For issues that were flagged due to CLAUDE.md instructions, the agent should double check that the CLAUDE.md actually calls out that issue specifically. The scale is (give this rubric to the agent verbatim):
+   a. 0: Not confident at all. This is a false positive that doesn't stand up to light scrutiny, or is a pre-existing issue.
+   b. 25: Somewhat confident. This might be a real issue, but may also be a false positive. The agent wasn't able to verify that it's a real issue. If the issue is stylistic, it is one that was not explicitly called out in the relevant CLAUDE.md.
+   c. 50: Moderately confident. The agent was able to verify this is a real issue, but it might be a nitpick or not happen very often in practice. Relative to the rest of the changes, it's not very important.
+   d. 75: Highly confident. The agent double checked the issue, and verified that it is very likely it is a real issue that will be hit in practice. The existing approach is insufficient. The issue is very important and will directly impact the code's functionality, or it is an issue that is directly mentioned in the relevant CLAUDE.md.
+   e. 100: Absolutely certain. The agent double checked the issue, and confirmed that it is definitely a real issue, that will happen frequently in practice. The evidence directly confirms this.
+6. Filter out any issues with a score less than 80.
+7. Write the review to claude-review.md. When writing your review, keep in mind to:
+   a. Keep your output brief
+   b. Avoid emojis
+   c. Reference relevant files and line numbers
+8. Briefly summarize claude-review.md as direct output to the user
+
+Examples of false positives, for steps 4 and 5:
+
+- Pre-existing issues
+- Something that looks like a bug but is not actually a bug
+- Pedantic nitpicks that a senior engineer wouldn't call out
+- Issues that a linter, typechecker, or compiler would catch (eg. missing or incorrect imports, type errors, broken tests, formatting issues, pedantic style issues like newlines). No need to run these build steps yourself -- it is safe to assume that they will be run separately as part of CI.
+- General code quality issues (eg. lack of test coverage, general security issues, poor documentation), unless explicitly required in CLAUDE.md
+- Issues that are called out in CLAUDE.md, but explicitly silenced in the code (eg. due to a lint ignore comment)
+- Changes in functionality that are likely intentional or are directly related to the broader change
+- Real issues, but on lines that were not modified in the current branch
+
+Notes:
+
+- Do not check build signal or attempt to build or typecheck the app. These will run separately, and are not relevant to your code review.
+- Use git commands to analyze local changes (not `gh` commands for remote PRs)
+- Make a todo list first
+- You must cite each bug with file path and line number (eg. if referring to a CLAUDE.md, you must reference it)
+- For your final output, follow the following format precisely (assuming for this example that you found 3 issues):
+
+---
+
+### Code review for branch `<branch-name>`
+
+Reviewed X commits with changes to Y files.
+
+Found 3 issues:
+
+1. **<brief description of bug>** (CLAUDE.md says "<...>")
+   - File: `path/to/file.ts:L10-L15`
+
+2. **<brief description of bug>** (some/other/CLAUDE.md says "<...>")
+   - File: `path/to/other-file.ts:L25-L30`
+
+3. **<brief description of bug>** (bug due to <reasoning>)
+   - File: `path/to/another-file.ts:L5-L8`
+
+---
+
+- Or, if you found no issues:
+
+---
+
+### Code review for branch `<branch-name>`
+
+Reviewed X commits with changes to Y files.
+
+No issues found. Checked for bugs and CLAUDE.md compliance.
+
+---

package/all/copy-overwrite/.claude/skills/plan-lower-code-complexity/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: plan-lower-code-complexity
+description: This skill should be used when reducing the cognitive complexity threshold of the codebase. It lowers the threshold by 2, identifies functions that exceed the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to fix all violations.
+allowed-tools: ["Read", "Bash", "Glob", "Grep"]
+---
+
+# Lower Code Complexity
+
+Reduces the cognitive complexity threshold by 2 and fixes all violations.
+
+## Step 1: Gather Requirements
+
+1. **Read current threshold** from eslint config (cognitive-complexity rule)
+2. **Calculate new threshold**: current - 2 (e.g., 15 -> 13)
+3. **Run lint** with the new threshold to find violations:
+   ```bash
+   bun run lint 2>&1 | grep "cognitive-complexity"
+   ```
+4. **Note for each violation**:
+   - File path and line number
+   - Function name
+   - Current complexity score
+
+If no violations at new threshold, report success and exit.
+
+## Step 2: Create Plan
+
+In plan mode, create a plan that includes the following details:
+
+```markdown
+Reduce cognitive complexity threshold from [current] to [new].
+
+## Functions Exceeding Threshold (ordered by complexity)
+
+1. src/services/user.ts:processUser (complexity: 18, target: [new])
+   - Line 45, function spans lines 45-120
+2. src/utils/helpers.ts:validateInput (complexity: 15, target: [new])
+   - Line 23, function spans lines 23-67
+...
+
+## Configuration Change
+- File: [eslint config path]
+- Change: cognitive-complexity threshold from [current] to [new]
+
+## Refactoring Strategies
+- **Extract functions**: Break complex logic 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
+
+## Acceptance Criteria
+- All functions at or below complexity [new]
+- `bun run lint` passes with no cognitive-complexity violations
+
+## Verification
+Command: `bun run lint 2>&1 | grep "cognitive-complexity" | wc -l`
+Expected: 0
+```

package/all/copy-overwrite/.claude/skills/plan-reduce-max-lines/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: plan-reduce-max-lines
+description: This skill should be used when reducing the maximum file lines threshold and fixing all violations. It updates the eslint threshold configuration, identifies files exceeding the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to split oversized files.
+allowed-tools: ["Read", "Bash", "Glob", "Grep"]
+argument-hint: "<max-lines-value>"
+
+---
+
+# Reduce Max Lines
+
+Target threshold: $ARGUMENTS lines per file
+
+If no argument provided, prompt the user for a target.
+
+## Step 1: Gather Requirements
+
+1. **Read current config** from eslint thresholds (eslint.thresholds.json or similar)
+2. **Run lint** with the new threshold to find violations:
+   ```bash
+   bun run lint 2>&1 | grep "max-lines"
+   ```
+3. **Note for each violation**:
+   - File path
+   - Current line count
+
+If no violations at $ARGUMENTS, report success and exit.
+
+## Step 2: Create Plan
+
+In plan mode, create a plan that includes the following details:
+
+```markdown
+Reduce max file lines threshold to $ARGUMENTS.
+
+## Files Exceeding Threshold (ordered by line count)
+
+1. src/services/user.ts (450 lines, target: $ARGUMENTS)
+2. src/utils/helpers.ts (380 lines, target: $ARGUMENTS)
+3. src/components/Dashboard.tsx (320 lines, target: $ARGUMENTS)
+...
+
+## Configuration Change
+- File: eslint.thresholds.json
+- Change: maxLines to $ARGUMENTS
+
+## 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
+
+## Acceptance Criteria
+- All files at or below $ARGUMENTS lines
+- `bun run lint` passes with no max-lines violations
+
+## Verification
+Command: `bun run lint 2>&1 | grep "max-lines" | wc -l`
+Expected: 0
+```

package/all/copy-overwrite/.claude/skills/plan-reduce-max-lines-per-function/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: plan-reduce-max-lines-per-function
+description: This skill should be used when reducing the maximum lines per function threshold and fixing all violations. It updates the eslint threshold configuration, identifies functions exceeding the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to split oversized functions.
+allowed-tools: ["Read", "Bash", "Glob", "Grep"]
+argument-hint: "<max-lines-per-function-value>"
+
+---
+
+# Reduce Max Lines Per Function
+
+Target threshold: $ARGUMENTS lines per function
+
+If no argument provided, prompt the user for a target.
+
+## Step 1: Gather Requirements
+
+1. **Read current config** from eslint thresholds (eslint.thresholds.json or similar)
+2. **Run lint** with the new threshold to find violations:
+   ```bash
+   bun run lint 2>&1 | grep "max-lines-per-function"
+   ```
+3. **Note for each violation**:
+   - File path and line number
+   - Function name
+   - Current line count
+
+If no violations at $ARGUMENTS, report success and exit.
+
+## Step 2: Create Plan
+
+In plan mode, create a plan that includes the following details:
+
+```markdown
+Reduce max lines per function threshold to $ARGUMENTS.
+
+## Functions Exceeding Threshold (ordered by line count)
+
+1. src/services/user.ts:processUser (95 lines, target: $ARGUMENTS)
+   - Line 45, function spans lines 45-140
+2. src/utils/helpers.ts:validateInput (82 lines, target: $ARGUMENTS)
+   - Line 23, function spans lines 23-105
+...
+
+## Configuration Change
+- File: eslint.thresholds.json
+- Change: maxLinesPerFunction to $ARGUMENTS
+
+## 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
+
+## Acceptance Criteria
+- All functions at or below $ARGUMENTS lines
+- `bun run lint` passes with no max-lines-per-function violations
+
+## Verification
+Command: `bun run lint 2>&1 | grep "max-lines-per-function" | wc -l`
+Expected: 0
+```

package/all/copy-overwrite/.claude/skills/project-add-test-coverage/SKILL.md

@@ -3,9 +3,12 @@ name: project-add-test-coverage
 description: This skill should be used when increasing test coverage to a specified threshold percentage. It runs the coverage report, identifies files with the lowest coverage, generates a brief with coverage gaps, and bootstraps a project to add the missing tests.
 allowed-tools: ["Read", "Bash", "Glob", "Grep"]
 argument-hint: "<threshold-percentage>"
-model: sonnet
+
 ---
 
+> **DEPRECATED**: This skill is deprecated. Use `/plan-add-test-coverage` instead, which integrates with Claude's native plan mode.
+> This skill will be removed in a future release.
+
 # Increase Test Coverage
 
 Target threshold: $ARGUMENTS%

package/all/copy-overwrite/.claude/skills/project-archive/SKILL.md

@@ -5,6 +5,10 @@ allowed-tools: ["Read", "Write", "Bash(git*)", "Glob", "Grep", "Task", "TaskCrea
 argument-hint: "<project-directory>"
 ---
 
+> **DEPRECATED**: This skill is deprecated. Use Claude's native plan mode instead.
+> Enter plan mode with `/plan`, describe your requirements, and Claude will create a plan with tasks automatically.
+> This skill will be removed in a future release.
+
 1. Move $ARGUMENTS to `projects/archive`
 2. Clear the active project marker: `rm -f .claude-active-project`
 3. Run /git-commit-and-submit-pr