@codyswann/lisa 1.56.0 → 1.56.2

package/plugins/lisa-typescript/skills/tasks-sync/SKILL.md

@@ -1,108 +0,0 @@
----
-name: tasks-sync
-description: This skill should be used when syncing current session tasks to a project directory. It exports all tasks from the current Claude Code session to JSON files in the project's tasks directory, enabling persistence across sessions.
-allowed-tools: ["Read", "Write", "Bash", "TaskList", "TaskGet"]
----
-
-# Sync Tasks to Project
-
-Sync all tasks from the current session to `projects/$ARGUMENTS/tasks/{session-id}/`.
-
-This skill is for manual syncing when work started without setting an active project. Once synced, the automatic hook handles future task updates.
-
-## Process
-
-### Step 1: Validate Project
-
-Check if the project directory exists:
-
-```bash
-ls -d projects/$ARGUMENTS 2>/dev/null
-```
-
-If the project doesn't exist, ask: "Project '$ARGUMENTS' doesn't exist. Create it?"
-
-If yes, create the project structure:
-
-```bash
-mkdir -p projects/$ARGUMENTS/tasks
-```
-
-### Step 2: Determine Session ID
-
-Find the current session by looking for the most recently modified task directory:
-
-```bash
-ls -dt ~/.claude/tasks/*/ 2>/dev/null | head -1 | xargs basename
-```
-
-If no session found, use a timestamp-based identifier:
-
-```bash
-echo "manual-$(date +%Y%m%d-%H%M%S)"
-```
-
-Store the session ID for use in subsequent steps.
-
-### Step 3: Set Active Project
-
-Create/update the active project marker:
-
-```bash
-echo "$ARGUMENTS" > .claude-active-project
-```
-
-### Step 4: Get Current Tasks
-
-Use TaskList to get all tasks in the current session.
-
-### Step 5: Sync Each Task
-
-For each task from TaskList:
-
-1. Use TaskGet to get full task details
-2. Create the session directory:
-
-```bash
-mkdir -p projects/$ARGUMENTS/tasks/{session-id}
-```
-
-3. Create a JSON file with the task data:
-
-```json
-{
-  "id": "<task-id>",
-  "subject": "<subject>",
-  "description": "<description>",
-  "activeForm": "<activeForm>",
-  "status": "<status>",
-  "blocks": [],
-  "blockedBy": []
-}
-```
-
-4. Write to `projects/$ARGUMENTS/tasks/{session-id}/<id>.json`
-
-### Step 6: Stage for Git
-
-```bash
-git add projects/$ARGUMENTS/tasks/{session-id}/*.json
-```
-
-### Step 7: Report
-
-```
-Synced X tasks to projects/$ARGUMENTS/tasks/{session-id}/
-- Pending: Y
-- In Progress: Z
-- Completed: W
-
-Files staged for commit. Run /git-commit when ready.
-```
-
-## Notes
-
-- This skill manually syncs all current tasks to a project
-- Use this when work started without a project context
-- After syncing, the active project is set so future tasks auto-sync via the hook
-- Each sync creates a new session directory to preserve history

package/plugins/src/base/hooks/format-on-edit.sh

@@ -1,76 +0,0 @@
-#!/bin/bash
-# This file is managed by Lisa.
-# Do not edit directly — changes will be overwritten on the next `lisa` run.
-
-# Hook script to format files with Prettier after Claude edits them
-# This script receives JSON input via stdin with tool information
-# Reference: https://docs.claude.com/en/docs/claude-code/hooks
-
-# Read the JSON input from stdin
-JSON_INPUT=$(cat)
-
-# Extract the file path from the tool_input
-# The Edit tool input contains a "file_path" field in the tool_input object
-FILE_PATH=$(echo "$JSON_INPUT" | grep -o '"tool_input":{[^}]*"file_path":"[^"]*"' | grep -o '"file_path":"[^"]*"' | cut -d'"' -f4)
-
-# Check if we successfully extracted a file path
-if [ -z "$FILE_PATH" ]; then
-    echo "⚠ Skipping Prettier: Could not extract file path from Edit tool input" >&2
-    exit 0  # Exit gracefully to not interrupt Claude's workflow
-fi
-
-# Check if the file exists
-if [ ! -f "$FILE_PATH" ]; then
-    echo "⚠ Skipping Prettier: File does not exist: $FILE_PATH" >&2
-    exit 0  # Exit gracefully
-fi
-
-# Get the file extension
-FILE_EXT="${FILE_PATH##*.}"
-
-# Check if this is a TypeScript or JavaScript file that should be formatted
-# Based on package.json format command: "prettier --write \"src/**/*.ts\" \"test/**/*.ts\""
-case "$FILE_EXT" in
-    ts|tsx|js|jsx|json)
-        # File type is supported for formatting
-        ;;
-    *)
-        echo "ℹ Skipping Prettier: File type .$FILE_EXT is not configured for auto-formatting"
-        exit 0
-        ;;
-esac
-
-# Change to the project directory to ensure package manager commands work
-cd "$CLAUDE_PROJECT_DIR" || exit 0
-
-# Detect package manager based on lock file presence
-detect_package_manager() {
-    if [ -f "bun.lockb" ] || [ -f "bun.lock" ]; then
-        echo "bun"
-    elif [ -f "pnpm-lock.yaml" ]; then
-        echo "pnpm"
-    elif [ -f "yarn.lock" ]; then
-        echo "yarn"
-    elif [ -f "package-lock.json" ]; then
-        echo "npm"
-    else
-        echo "npm"  # Default fallback
-    fi
-}
-
-PKG_MANAGER=$(detect_package_manager)
-
-# Run Prettier on the specific file
-echo "🎨 Running Prettier on: $FILE_PATH"
-$PKG_MANAGER prettier --write "$FILE_PATH" 2>&1 | grep -v "run v" | grep -v "Done in"
-
-# Check the exit status
-if [ ${PIPESTATUS[0]} -eq 0 ]; then
-    echo "✓ Successfully formatted: $(basename "$FILE_PATH")"
-else
-    echo "⚠ Prettier formatting failed for: $FILE_PATH" >&2
-    echo "  You may need to run '$PKG_MANAGER run format' manually to fix formatting issues." >&2
-fi
-
-# Always exit successfully to not interrupt Claude's workflow
-exit 0

package/plugins/src/base/hooks/lint-on-edit.sh

@@ -1,81 +0,0 @@
-#!/bin/bash
-# This file is managed by Lisa.
-# Do not edit directly — changes will be overwritten on the next `lisa` run.
-# =============================================================================
-# ESLint Lint-on-Edit Hook (PostToolUse - Write|Edit)
-# =============================================================================
-# Runs ESLint --fix with --quiet --cache on each edited TypeScript file.
-# Part of the inline self-correction pipeline: prettier → ast-grep → eslint.
-#
-# Behavior:
-#   - Exit 0: lint passes or auto-fix resolved all errors
-#   - Exit 2: unfixable errors remain — blocks Claude so it fixes them immediately
-#
-# @see .claude/rules/verfication.md "Self-Correction Loop" section
-# =============================================================================
-
-# Extract file path from JSON input
-FILE_PATH=$(cat | grep -o '"file_path":"[^"]*"' | head -1 | cut -d'"' -f4)
-
-if [ -z "$FILE_PATH" ] || [ ! -f "$FILE_PATH" ]; then
-    exit 0
-fi
-
-# Check if file type is supported (TypeScript only)
-case "${FILE_PATH##*.}" in
-    ts|tsx) ;;
-    *) exit 0 ;;
-esac
-
-# Validate project directory
-if [ -z "${CLAUDE_PROJECT_DIR:-}" ]; then
-    exit 0
-fi
-
-# Check if file is in a source directory
-RELATIVE_PATH="${FILE_PATH#$CLAUDE_PROJECT_DIR/}"
-case "$RELATIVE_PATH" in
-    src/*|apps/*|libs/*|test/*|tests/*|features/*|components/*|hooks/*|screens/*|app/*|constants/*|utils/*|providers/*|stores/*) ;;
-    *) exit 0 ;;
-esac
-
-cd "$CLAUDE_PROJECT_DIR" || exit 0
-
-# Detect package manager
-if [ -f "bun.lockb" ] || [ -f "bun.lock" ]; then
-    PKG_MANAGER="bun"
-elif [ -f "pnpm-lock.yaml" ]; then
-    PKG_MANAGER="pnpm"
-elif [ -f "yarn.lock" ]; then
-    PKG_MANAGER="yarn"
-else
-    PKG_MANAGER="npm"
-fi
-
-# Run ESLint with --fix --quiet --cache on the specific file
-# --quiet: suppress warnings, only show errors
-# --cache: use ESLint cache for performance
-echo "Running ESLint --fix on: $FILE_PATH"
-
-# First pass: attempt auto-fix
-OUTPUT=$($PKG_MANAGER eslint --fix --quiet --cache "$FILE_PATH" 2>&1)
-FIX_EXIT=$?
-
-if [ $FIX_EXIT -eq 0 ]; then
-    echo "ESLint: No errors in $(basename "$FILE_PATH")"
-    exit 0
-fi
-
-# Auto-fix resolved some issues but errors remain — re-run to get remaining errors
-OUTPUT=$($PKG_MANAGER eslint --quiet --cache "$FILE_PATH" 2>&1)
-LINT_EXIT=$?
-
-if [ $LINT_EXIT -eq 0 ]; then
-    echo "ESLint: Auto-fixed all errors in $(basename "$FILE_PATH")"
-    exit 0
-fi
-
-# Unfixable errors remain — block with feedback
-echo "ESLint found unfixable errors in: $FILE_PATH" >&2
-echo "$OUTPUT" >&2
-exit 2

package/plugins/src/base/hooks/sg-scan-on-edit.sh

@@ -1,68 +0,0 @@
-#!/bin/bash
-# This file is managed by Lisa.
-# Do not edit directly — changes will be overwritten on the next `lisa` run.
-
-# Hook script to run ast-grep scan after Claude edits files
-# This script receives JSON input via stdin with tool information
-# Reference: https://docs.claude.com/en/docs/claude-code/hooks
-# Note: This hook is BLOCKING - it returns non-zero exit codes so Claude must fix issues
-
-# Extract file path from JSON input
-FILE_PATH=$(cat | grep -o '"file_path":"[^"]*"' | head -1 | cut -d'"' -f4)
-
-if [ -z "$FILE_PATH" ] || [ ! -f "$FILE_PATH" ]; then
-    exit 0
-fi
-
-# Check if file type is supported (TypeScript, JavaScript)
-case "${FILE_PATH##*.}" in
-    ts|tsx|js|jsx|mjs|cjs) ;;
-    *) exit 0 ;;
-esac
-
-# Validate project directory
-if [ -z "${CLAUDE_PROJECT_DIR:-}" ]; then
-    exit 0
-fi
-
-# Check if file is in a source directory
-RELATIVE_PATH="${FILE_PATH#$CLAUDE_PROJECT_DIR/}"
-case "$RELATIVE_PATH" in
-    src/*|apps/*|libs/*|test/*|tests/*|features/*|components/*|hooks/*|screens/*|app/*|constants/*|utils/*|providers/*|stores/*) ;;
-    *) exit 0 ;;
-esac
-
-cd "$CLAUDE_PROJECT_DIR" || exit 0
-
-# Verify ast-grep configuration exists
-if [ ! -f "sgconfig.yml" ]; then
-    exit 0
-fi
-
-# Verify rules are defined
-RULE_COUNT=$(find ast-grep/rules -name "*.yml" -o -name "*.yaml" 2>/dev/null | grep -v ".gitkeep" | wc -l | tr -d ' ')
-if [ "$RULE_COUNT" -eq 0 ]; then
-    exit 0
-fi
-
-# Detect package manager
-if [ -f "bun.lockb" ] || [ -f "bun.lock" ]; then
-    PKG_MANAGER="bun"
-elif [ -f "pnpm-lock.yaml" ]; then
-    PKG_MANAGER="pnpm"
-elif [ -f "yarn.lock" ]; then
-    PKG_MANAGER="yarn"
-else
-    PKG_MANAGER="npm"
-fi
-
-# Run ast-grep scan
-echo "Running ast-grep scan on: $FILE_PATH"
-if OUTPUT=$($PKG_MANAGER run sg:scan "$FILE_PATH" 2>&1); then
-    echo "ast-grep: No issues found in $(basename "$FILE_PATH")"
-    exit 0
-else
-    echo "ast-grep found issues in: $FILE_PATH" >&2
-    echo "$OUTPUT" >&2
-    exit 1
-fi

package/plugins/src/base/rules/lisa.md

@@ -1,37 +0,0 @@
-# Lisa-Managed Files
-
-The following files are managed by Lisa and will be overwritten on every `lisa` run. Never edit them directly. Where a local override exists, edit that instead.
-
-## Files with local overrides (edit the override, not the managed file)
-
-| 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` |
-
-## Create-only files (edit freely, Lisa won't overwrite)
-
-- `.claude/rules/PROJECT_RULES.md`
-- `eslint.thresholds.json`
-- `jest.thresholds.json`
-
-## Deep-merged by Lisa (Lisa wins conflicts, but project can add its own keys)
-
-- `.claude/settings.json`
-
-## 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.
-
-## 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/`