@codyswann/lisa 1.19.0 → 1.19.1

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

@@ -1,53 +0,0 @@
----
-name: project-review
-description: This skill should be used when performing extensive code review and optimization on the current project. It runs Claude local code review, CodeRabbit review, implements fixes from both, and performs code simplification optimizations.
-allowed-tools: ["Read", "Write", "Edit", "Bash", "Glob", "Grep", "Task", "TaskCreate", "TaskUpdate", "TaskList", "Skill"]
-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.
-
-The current branch is a feature branch with full implementation of the project in $ARGUMENTS.
-
-**IMPORTANT**: Perform each step and move to the next without stopping.
-
-## Setup
-
-Set active project marker: `echo "$ARGUMENTS" | sed 's|.*/||' > .claude-active-project`
-
-Extract `<project-name>` from the last segment of `$ARGUMENTS`.
-
-## Create and Execute Tasks
-
-Create workflow tracking tasks with `metadata.project` set to the project name:
-
-```
-TaskCreate:
-  subject: "Perform Claude review"
-  description: "If $ARGUMENTS/claude-review.md already exists, skip this task. Otherwise, run /project-local-code-review $ARGUMENTS"
-  metadata: { project: "<project-name>" }
-
-TaskCreate:
-  subject: "Implement Claude review fixes"
-  description: "Read $ARGUMENTS/claude-review.md and fix any suggestions that score above 45."
-  metadata: { project: "<project-name>" }
-
-TaskCreate:
-  subject: "Perform CodeRabbit review"
-  description: "If $ARGUMENTS/coderabbit-review.md already exists, skip this task. Otherwise, run `/coderabbit:review` and write results to $ARGUMENTS/coderabbit-review.md"
-  metadata: { project: "<project-name>" }
-
-TaskCreate:
-  subject: "Implement CodeRabbit review fixes"
-  description: "Evaluate suggestions in $ARGUMENTS/coderabbit-review.md and implement fixes for valid findings."
-  metadata: { project: "<project-name>" }
-
-TaskCreate:
-  subject: "Perform Claude optimizations"
-  description: "Use the code simplifier agent to clean up code added to the current branch."
-  metadata: { project: "<project-name>" }
-```
-
-**Execute each task via a subagent** to preserve main context. Launch up to 6 in parallel where tasks don't have dependencies. Do not stop until all are completed.

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

@@ -1,60 +0,0 @@
----
-name: project-setup
-description: This skill should be used when initializing a new project with full requirements analysis, planning, and structure setup. It accepts a file path, JIRA issue, or text description, creates the project directory structure with brief.md and findings.md, and commits the initial setup.
-allowed-tools: ["Read", "Write", "Bash(git*)", "Glob", "Grep", "Task", "TaskCreate", "TaskUpdate", "TaskList"]
-argument-hint: "<file-path|jira-issue|text-description>"
----
-
-> **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.
-
-## Step 1: Determine Input Type
-
-Examine $ARGUMENTS to determine which type:
-- **Jira issue**: Matches pattern like `SE-123`, `PROJ-456` (letters-dash-numbers)
-- **File path**: Path exists as a file (check with Glob or Read)
-- **Text prompt**: Everything else - a description of work to be done
-
-## Step 2: Get Brief Content
-
-Based on input type:
-
-**If Jira issue:**
-1. Use the atlassian MCP server to Read the issue FULLY
-2. If MCP server not working, STOP and let human know
-
-**If file path:**
-1. Read the file FULLY (no limit/offset)
-
-**If text prompt:**
-1. The prompt IS the brief content - use $ARGUMENTS directly
-
-## Step 3: Create Project Structure
-
-1. Create project directory in `projects/` named `YYYY-MM-DD-<project-name>` where `<project-name>` is derived from:
-   - Jira: the issue key and title (e.g., `2026-01-26-se-123-add-auth`)
-   - File: the filename without extension
-   - Text prompt: a kebab-case summary of the prompt (e.g., `2026-01-26-add-user-authentication`)
-
-2. Create `brief.md` in the project directory:
-   - Jira: populate with issue number, title, and description
-   - File: copy contents of the file to `brief.md`
-   - Text prompt: create `brief.md` with the prompt text as content
-
-3. Create empty `findings.md` in the project directory
-
-4. Create `.claude-active-project` marker file:
-   ```bash
-   echo "YYYY-MM-DD-<project-name>" > .claude-active-project
-   ```
-
-## Step 4: Git and Finalize
-
-1. If Jira issue:
-   - Run /git-commit with branch name including issue number (e.g., `feature/SE-111-<branch-name>`)
-   - Use atlassian MCP server to update issue status to "In Progress"
-2. Otherwise:
-   - Run /git-commit
-
-3. Output: "Project created: `YYYY-MM-DD-<project-name>`"

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

@@ -1,46 +0,0 @@
----
-name: project-verify
-description: This skill should be used when performing comprehensive verification that a feature branch fully implements all project requirements with proper code quality, tests, and documentation. It reviews requirements, verifies implementation, runs task verification commands, and documents any drift.
-allowed-tools: ["Read", "Write", "Edit", "Bash", "Glob", "Grep", "Task", "TaskCreate", "TaskUpdate", "TaskList"]
-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.
-
-The current branch is a feature branch with full implementation of the project in $ARGUMENTS.
-
-## Setup
-
-Set active project marker: `echo "$ARGUMENTS" | sed 's|.*/||' > .claude-active-project`
-
-Extract `<project-name>` from the last segment of `$ARGUMENTS`.
-
-## Create and Execute Tasks
-
-Create workflow tracking tasks with `metadata.project` set to the project name:
-
-```
-TaskCreate:
-  subject: "Review requirements"
-  description: "Read all requirements for $ARGUMENTS (brief.md, research.md, task files)."
-  metadata: { project: "<project-name>" }
-
-TaskCreate:
-  subject: "Verify implementation"
-  description: "Verify the implementation completely and fully satisfies all requirements from the brief and research."
-  metadata: { project: "<project-name>" }
-
-TaskCreate:
-  subject: "Run task verification commands"
-  description: "Read all task files in $ARGUMENTS/tasks/. For each task with verification metadata (JSON: metadata.verification, or Markdown: ## Verification section), create a verification task with subject 'Verify: <original-subject>' and metadata including originalTaskId and verification details. Then execute each verification task: run the command, compare output to expected. If pass, mark completed. If fail, keep in_progress and document failure in $ARGUMENTS/drift.md. Report summary: total tasks, passed, failed, blocked."
-  metadata: { project: "<project-name>" }
-
-TaskCreate:
-  subject: "Document drift"
-  description: "If there is any divergence from requirements or verification failures, ensure all drift is documented in $ARGUMENTS/drift.md."
-  metadata: { project: "<project-name>" }
-```
-
-**Execute each task via a subagent** to preserve main context. Launch up to 6 in parallel where tasks don't have dependencies. Do not stop until all are completed.