@codyswann/lisa 1.47.1 → 1.48.0

package/rails/copy-overwrite/.claude/skills/active-record-model-best-practices/SKILL.md

@@ -1,166 +0,0 @@
----
-name: active-record-model-best-practices
-description: Best practices for Ruby on Rails models, splitting code into well-organized, maintainable code. Use when a model exceeds ~100 lines, has mixed responsibilities, or when the user asks to refactor, extract, clean up, or organize a Rails model. Applies patterns: concerns, service objects, query objects, form objects, and value objects.
----
-
-# Rails Model Refactoring
-
-When refactoring a Rails model, analyze the file and extract code into the appropriate pattern based on what the code does. The model itself should only contain associations, enums, basic validations, and concern includes.
-
-## Decision Framework
-
-Read the model file and classify each block of code:
-
-| Code type | Extract to | Location |
-|---|---|---|
-| Related scopes + simple methods sharing a theme | Concern | `app/models/concerns/` |
-| Business logic, multi-step operations, callbacks with side effects | Service object | `app/services/` |
-| Complex queries, multi-join scopes, reporting queries | Query object | `app/queries/` |
-| Context-specific validations (e.g. registration vs admin update) | Form object | `app/forms/` |
-| Domain concepts beyond a primitive (money, coordinates, scores) | Value object | `app/models/` |
-| Associations, enums, core validations, simple scopes | Keep on model | — |
-
-## Patterns
-
-### Concerns
-
-Use for grouping related scopes, validations, callbacks, and simple instance methods that share a single theme. Name the concern after the capability it provides.
-
-```ruby
-# app/models/concerns/searchable.rb
-module Searchable
-  extend ActiveSupport::Concern
-
-  included do
-    scope :search, ->(query) { where("name ILIKE ?", "%#{query}%") }
-  end
-
-  def matching_terms(query)
-    name.scan(/#{Regexp.escape(query)}/i)
-  end
-end
-```
-
-### Service Objects
-
-Use for business logic, orchestration of multiple models, and anything triggered by a user action that involves more than a simple CRUD operation. Follow the single-responsibility principle — one service, one operation.
-
-```ruby
-# app/services/players/calculate_stats.rb
-module Players
-  class CalculateStats
-    def initialize(player)
-      @player = player
-    end
-
-    def call
-      # complex logic here
-    end
-  end
-end
-```
-
-Conventions:
-- Namespace under the model name: `Players::CalculateStats`
-- Single public method: `call`
-- Accept dependencies via `initialize`
-- Return a result or raise a domain-specific error
-
-### Query Objects
-
-Use for complex database queries that involve joins, subqueries, CTEs, or multi-condition filtering that would clutter a model with scopes.
-
-```ruby
-# app/queries/players/free_agent_query.rb
-module Players
-  class FreeAgentQuery
-    def initialize(relation = Player.all)
-      @relation = relation
-    end
-
-    def call(filters = {})
-      @relation
-        .where(contract_status: :expired)
-        .where("age < ?", filters[:max_age])
-        .joins(:stats)
-        .order(war: :desc)
-    end
-  end
-end
-```
-
-Conventions:
-- Accept a base relation in `initialize` (default to `Model.all`)
-- Return an ActiveRecord relation so it remains chainable
-- Single public method: `call`
-
-### Form Objects
-
-Use when validations only apply in specific contexts, or when a form spans multiple models.
-
-```ruby
-# app/forms/player_registration_form.rb
-class PlayerRegistrationForm
-  include ActiveModel::Model
-  include ActiveModel::Attributes
-
-  attribute :name, :string
-  attribute :email, :string
-  attribute :team_id, :integer
-  attribute :position, :string
-
-  validates :name, :email, :position, presence: true
-  validates :email, format: { with: URI::MailTo::EMAIL_REGEXP }
-
-  def save
-    return false unless valid?
-    Player.create!(attributes)
-  end
-end
-```
-
-### Value Objects
-
-Use for domain concepts that deserve their own identity beyond a raw primitive.
-
-```ruby
-# app/models/batting_average.rb
-class BattingAverage
-  include Comparable
-
-  def initialize(hits, at_bats)
-    @hits = hits
-    @at_bats = at_bats
-  end
-
-  def value
-    return 0.0 if @at_bats.zero?
-    (@hits.to_f / @at_bats).round(3)
-  end
-
-  def elite?
-    value >= 0.300
-  end
-
-  def <=>(other)
-    value <=> other.value
-  end
-end
-```
-
-## Refactoring Process
-
-1. **Read the entire model** and identify every method, scope, callback, and validation.
-2. **Classify each block** using the decision framework table above.
-3. **Extract in order**: value objects first, then query objects, then service objects, then concerns. Do concerns last because some may become unnecessary after other extractions.
-4. **Update the model** to include concerns and delegate to new objects.
-5. **Verify** that the slimmed-down model only contains: associations, enums, core validations, and concern includes.
-6. **Create or update tests** for each extracted class. Each new class gets its own spec file mirroring the source path.
-
-## What NOT to Do
-
-- Don't extract everything — simple one-line scopes and basic validations belong on the model.
-- Don't create a class for trivial logic just to hit a line count target.
-- Don't use concerns as junk drawers — each concern should have a clear, single theme.
-- Don't break ActiveRecord conventions (e.g. don't move associations into concerns).
-- Don't introduce callback-heavy service objects — prefer explicit invocation over implicit hooks.

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

@@ -1,45 +0,0 @@
----
-name: plan-add-test-coverage
-description: This skill should be used when increasing test coverage to a specified threshold percentage. It runs the test suite with SimpleCov, 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"]
-
----
-
-# Increase Test Coverage
-
-Target threshold: $ARGUMENTS%
-
-If no argument provided, prompt the user for a target.
-
-## Step 1: Gather Requirements
-
-1. **Find coverage config** (`.simplecov` or `spec/spec_helper.rb`)
-2. **Run test suite with coverage** to get current state:
-   ```bash
-   bundle exec rspec 2>&1 | tail -50
-   ```
-3. **Check SimpleCov output** in `coverage/index.html` or console output
-4. **Identify the 20 files with lowest coverage**, noting:
-   - File path
-   - Current coverage % (lines, branches)
-   - Which lines/branches are uncovered
-
-## Step 2: Compile Brief and Delegate
-
-Compile the gathered information into a structured brief:
-
-```
-Increase test coverage from [current]% to $ARGUMENTS%.
-
-Files needing coverage (ordered by coverage gap):
-1. [file] - [current]% coverage (target: $ARGUMENTS%)
-   - Uncovered: [lines]
-   - Missing branch coverage: [lines]
-2. ...
-
-Configuration: .simplecov, update minimum_coverage to $ARGUMENTS%
-
-Verification: `bundle exec rspec` -> Expected: SimpleCov reports >= $ARGUMENTS% coverage
-```
-
-Invoke `/plan-execute` with this brief to create the implementation plan.

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

@@ -1,45 +0,0 @@
----
-name: plan-fix-linter-error
-description: This skill should be used when fixing all violations of one or more RuboCop cops across the codebase. It runs RuboCop, groups violations by cop and file, generates a brief with fix strategies, and creates a plan with tasks to implement the fixes.
-allowed-tools: ["Read", "Bash", "Glob", "Grep"]
-
----
-
-# Fix Linter Errors
-
-Target cops: $ARGUMENTS
-
-If no arguments provided, prompt the user for at least one RuboCop cop name.
-
-## Step 1: Gather Requirements
-
-1. **Parse cops** from $ARGUMENTS (space-separated)
-2. **Run RuboCop** to collect all violations:
-   ```bash
-   bundle exec rubocop --format json 2>&1
-   ```
-3. **Group violations** by cop, then by file, noting:
-   - File path and line numbers
-   - Violation count per file
-   - Sample offense messages
-
-## Step 2: Compile Brief and Delegate
-
-Compile the gathered information into a structured brief:
-
-```
-Fix RuboCop violations for cops: $ARGUMENTS
-
-Violations by cop:
-- [CopName1]: X total violations across Y files
-  - [file]: N violations (lines: ...)
-  - ...
-- [CopName2]: X total violations across Y files
-  - ...
-
-Fix strategies: extract methods, reduce complexity, apply auto-correct where safe
-
-Verification: `bundle exec rubocop --format simple 2>&1 | grep -E "($ARGUMENTS)" | wc -l` -> Expected: 0
-```
-
-Invoke `/plan-execute` with this brief to create the implementation plan.

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

@@ -1,48 +0,0 @@
----
-name: plan-lower-code-complexity
-description: This skill should be used when reducing the code complexity threshold of the codebase. It lowers the CyclomaticComplexity threshold by 2, identifies methods 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 CyclomaticComplexity threshold by 2 and fixes all violations.
-
-## Step 1: Gather Requirements
-
-1. **Read current threshold** from `.rubocop.yml` (`Metrics/CyclomaticComplexity` Max)
-2. **Calculate new threshold**: current - 2 (e.g., 10 -> 8)
-3. **Run RuboCop and flog** to find violations:
-   ```bash
-   bundle exec rubocop --only Metrics/CyclomaticComplexity,Metrics/PerceivedComplexity --format json 2>&1
-   ```
-   ```bash
-   bundle exec flog --all --group app/ 2>&1 | head -50
-   ```
-4. **Note for each violation**:
-   - File path and line number
-   - Method name
-   - Current complexity score (RuboCop and/or flog)
-
-If no violations at new threshold, report success and exit.
-
-## Step 2: Compile Brief and Delegate
-
-Compile the gathered information into a structured brief:
-
-```
-Reduce CyclomaticComplexity threshold from [current] to [new].
-
-Methods exceeding threshold (ordered by complexity):
-1. [file:method_name] (complexity: X, target: [new]) - Line Y
-   - flog score: Z
-2. ...
-
-Configuration change: .rubocop.local.yml, Metrics/CyclomaticComplexity Max from [current] to [new]
-
-Refactoring strategies: extract methods, early returns, extract conditions, use lookup hashes, replace conditionals with polymorphism
-
-Verification: `bundle exec rubocop --only Metrics/CyclomaticComplexity --format simple 2>&1 | grep "offense" | wc -l` -> Expected: 0
-```
-
-Invoke `/plan-execute` with this brief to create the implementation plan.

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

@@ -1,46 +0,0 @@
----
-name: plan-reduce-max-lines
-description: This skill should be used when reducing the maximum class/module lines threshold and fixing all violations. It updates the RuboCop configuration, identifies classes and modules 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"]
-
----
-
-# Reduce Max Lines
-
-Target threshold: $ARGUMENTS lines per class/module
-
-If no argument provided, prompt the user for a target.
-
-## Step 1: Gather Requirements
-
-1. **Read current config** from `.rubocop.yml` or `.rubocop.local.yml` (`Metrics/ClassLength` and `Metrics/ModuleLength`)
-2. **Run RuboCop** with the target threshold to find violations:
-   ```bash
-   bundle exec rubocop --only Metrics/ClassLength,Metrics/ModuleLength --format json 2>&1
-   ```
-3. **Note for each violation**:
-   - File path
-   - Class/module name
-   - Current line count
-
-If no violations at $ARGUMENTS, report success and exit.
-
-## Step 2: Compile Brief and Delegate
-
-Compile the gathered information into a structured brief:
-
-```
-Reduce max class/module lines threshold to $ARGUMENTS.
-
-Classes/modules exceeding threshold (ordered by line count):
-1. [file:ClassName] - [current] lines (target: $ARGUMENTS)
-2. ...
-
-Configuration change: .rubocop.local.yml, Metrics/ClassLength Max to $ARGUMENTS, Metrics/ModuleLength Max to $ARGUMENTS
-
-Refactoring strategies: extract concerns, extract service objects, remove duplication, delete dead code, simplify logic
-
-Verification: `bundle exec rubocop --only Metrics/ClassLength,Metrics/ModuleLength --format simple 2>&1 | grep "offense" | wc -l` -> Expected: 0
-```
-
-Invoke `/plan-execute` with this brief to create the implementation plan.

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

@@ -1,46 +0,0 @@
----
-name: plan-reduce-max-lines-per-function
-description: This skill should be used when reducing the maximum lines per method threshold and fixing all violations. It updates the RuboCop configuration, identifies methods exceeding the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to split oversized methods.
-allowed-tools: ["Read", "Bash", "Glob", "Grep"]
-
----
-
-# Reduce Max Lines Per Method
-
-Target threshold: $ARGUMENTS lines per method
-
-If no argument provided, prompt the user for a target.
-
-## Step 1: Gather Requirements
-
-1. **Read current config** from `.rubocop.yml` or `.rubocop.local.yml` (`Metrics/MethodLength`)
-2. **Run RuboCop** with the target threshold to find violations:
-   ```bash
-   bundle exec rubocop --only Metrics/MethodLength --format json 2>&1
-   ```
-3. **Note for each violation**:
-   - File path and line number
-   - Method name
-   - Current line count
-
-If no violations at $ARGUMENTS, report success and exit.
-
-## Step 2: Compile Brief and Delegate
-
-Compile the gathered information into a structured brief:
-
-```
-Reduce max lines per method threshold to $ARGUMENTS.
-
-Methods exceeding threshold (ordered by line count):
-1. [file:method_name] (lines: X, target: $ARGUMENTS) - Line Y
-2. ...
-
-Configuration change: .rubocop.local.yml, Metrics/MethodLength Max to $ARGUMENTS
-
-Refactoring strategies: extract methods, early returns, extract conditions, use lookup hashes, consolidate logic
-
-Verification: `bundle exec rubocop --only Metrics/MethodLength --format simple 2>&1 | grep "offense" | wc -l` -> Expected: 0
-```
-
-Invoke `/plan-execute` with this brief to create the implementation plan.

package/typescript/copy-overwrite/.claude/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/typescript/copy-overwrite/.claude/hooks/install-pkgs.sh

@@ -1,64 +0,0 @@
-#!/bin/bash
-# This file is managed by Lisa.
-# Do not edit directly — changes will be overwritten on the next `lisa` run.
-
-# Only run package installation in remote (Claude Code web) environment
-# node_modules are gitignored, so they need to be installed remotely
-if [ "$CLAUDE_CODE_REMOTE" != "true" ]; then
-  exit 0
-fi
-
-# Detect package manager based on lock file presence
-if [ -f "bun.lockb" ] || [ -f "bun.lock" ]; then
-  bun install
-elif [ -f "pnpm-lock.yaml" ]; then
-  pnpm install
-elif [ -f "yarn.lock" ]; then
-  yarn install
-elif [ -f "package-lock.json" ]; then
-  npm install
-else
-  npm install
-fi
-
-# Install Gitleaks for secret detection (pre-commit hook)
-echo "Installing Gitleaks for secret detection..."
-GITLEAKS_VERSION="8.18.4"
-curl -sSfL "https://github.com/gitleaks/gitleaks/releases/download/v${GITLEAKS_VERSION}/gitleaks_${GITLEAKS_VERSION}_linux_x64.tar.gz" | tar -xz -C /usr/local/bin gitleaks
-echo "Gitleaks installed: $(gitleaks version)"
-
-# Install jira-cli for JIRA integration
-# The tarball nests the binary at jira_VERSION_linux_x86_64/bin/jira,
-# so we extract to a temp dir and copy the binary out.
-echo "Installing jira-cli for JIRA integration..."
-JIRA_CLI_VERSION="1.7.0"
-JIRA_TMPDIR=$(mktemp -d)
-curl -sSfL "https://github.com/ankitpokhrel/jira-cli/releases/download/v${JIRA_CLI_VERSION}/jira_${JIRA_CLI_VERSION}_linux_x86_64.tar.gz" \
-  | tar -xz -C "${JIRA_TMPDIR}"
-cp "${JIRA_TMPDIR}/jira_${JIRA_CLI_VERSION}_linux_x86_64/bin/jira" /usr/local/bin/jira
-chmod +x /usr/local/bin/jira
-rm -rf "${JIRA_TMPDIR}"
-echo "jira-cli installed: $(jira version)"
-
-# Install Chromium for Lighthouse CI (pre-push hook)
-# Playwright's bundled Chromium works with @lhci/cli
-echo "Installing Chromium for Lighthouse CI..."
-npx playwright install chromium
-
-# Find and export CHROME_PATH for Lighthouse CI
-# Use sort to ensure deterministic selection of the latest version
-CHROME_PATH=$(find ~/.cache/ms-playwright -name "chrome" -type f 2>/dev/null | grep "chrome-linux" | sort | tail -n 1)
-if [ -n "$CHROME_PATH" ]; then
-  # Append to ~/.bashrc for shell sessions (idempotent)
-  if ! grep -q "export CHROME_PATH=" ~/.bashrc 2>/dev/null; then
-    echo "export CHROME_PATH=\"$CHROME_PATH\"" >> ~/.bashrc
-  else
-    # Update existing CHROME_PATH in bashrc
-    sed -i "s|^export CHROME_PATH=.*|export CHROME_PATH=\"$CHROME_PATH\"|" ~/.bashrc
-  fi
-
-  export CHROME_PATH="$CHROME_PATH"
-  echo "Chromium installed at: $CHROME_PATH"
-fi
-
-exit 0

package/typescript/copy-overwrite/.claude/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/typescript/copy-overwrite/.claude/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