@codyswann/lisa 1.47.1 → 1.49.0

package/plugins/lisa-rails/skills/skill-creator/scripts/quick_validate.py

@@ -0,0 +1,67 @@
+#!/usr/bin/env python3
+# This file is managed by Lisa.
+# Do not edit directly — changes will be overwritten on the next `lisa` run.
+"""
+Quick validation script for skills - minimal version
+"""
+
+import sys
+import os
+import re
+from pathlib import Path
+
+def validate_skill(skill_path):
+    """Basic validation of a skill"""
+    skill_path = Path(skill_path)
+    
+    # Check SKILL.md exists
+    skill_md = skill_path / 'SKILL.md'
+    if not skill_md.exists():
+        return False, "SKILL.md not found"
+    
+    # Read and validate frontmatter
+    content = skill_md.read_text()
+    if not content.startswith('---'):
+        return False, "No YAML frontmatter found"
+    
+    # Extract frontmatter
+    match = re.match(r'^---\n(.*?)\n---', content, re.DOTALL)
+    if not match:
+        return False, "Invalid frontmatter format"
+    
+    frontmatter = match.group(1)
+    
+    # Check required fields
+    if 'name:' not in frontmatter:
+        return False, "Missing 'name' in frontmatter"
+    if 'description:' not in frontmatter:
+        return False, "Missing 'description' in frontmatter"
+    
+    # Extract name for validation
+    name_match = re.search(r'name:\s*(.+)', frontmatter)
+    if name_match:
+        name = name_match.group(1).strip()
+        # Check naming convention (hyphen-case: lowercase with hyphens)
+        if not re.match(r'^[a-z0-9-]+$', name):
+            return False, f"Name '{name}' should be hyphen-case (lowercase letters, digits, and hyphens only)"
+        if name.startswith('-') or name.endswith('-') or '--' in name:
+            return False, f"Name '{name}' cannot start/end with hyphen or contain consecutive hyphens"
+
+    # Extract and validate description
+    desc_match = re.search(r'description:\s*(.+)', frontmatter)
+    if desc_match:
+        description = desc_match.group(1).strip()
+        # Check for angle brackets
+        if '<' in description or '>' in description:
+            return False, "Description cannot contain angle brackets (< or >)"
+
+    return True, "Skill is valid!"
+
+if __name__ == "__main__":
+    if len(sys.argv) != 2:
+        print("Usage: python quick_validate.py <skill_directory>")
+        sys.exit(1)
+    
+    valid, message = validate_skill(sys.argv[1])
+    print(message)
+    sys.exit(0 if valid else 1)

package/plugins/lisa-rails/skills/sonarqube-check/SKILL.md

@@ -0,0 +1,11 @@
+---
+name: sonarqube-check
+description: This skill should be used when checking why the last pull request failed SonarQube/SonarCloud quality gates. It uses the SonarQube MCP server to retrieve failure details and report the reasons.
+allowed-tools: ["mcp__sonarqube__*"]
+---
+
+# SonarQube Check
+
+Use the SonarQube MCP server to get the reason the last PR failed checks.
+
+Retrieve the quality gate status and report all failures with their details.

package/plugins/lisa-rails/skills/sonarqube-fix/SKILL.md

@@ -0,0 +1,8 @@
+---
+name: sonarqube-fix
+description: This skill should be used when fixing SonarQube quality gate failures. It runs the sonarqube:check skill to identify failures, fixes the identified issues, and then commits the changes using the git:commit skill.
+---
+
+1. Run /sonarqube-check
+2. Fix the SonarQube quality gate failures identified in step 1
+3. Run /git-commit

package/plugins/lisa-rails/skills/tasks-load/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: tasks-load
+description: This skill should be used when loading tasks from a project directory into the current Claude Code session. It reads task JSON files from session subdirectories, recreates them in the current session, and sets the active project marker.
+allowed-tools: ["Read", "Bash", "TaskCreate", "TaskUpdate", "TaskList"]
+---
+
+# Load Project Tasks
+
+Load tasks from `projects/$ARGUMENTS/tasks/` into the current Claude Code session.
+
+Tasks are stored in session subdirectories to preserve history across `/clear` commands:
+```
+projects/$ARGUMENTS/tasks/
+├── {session-1-uuid}/
+│   ├── 1.json
+│   └── 2.json
+└── {session-2-uuid}/
+    ├── 1.json
+    └── 2.json
+```
+
+## Process
+
+### Step 1: Validate Project
+
+Check if the project exists and has task files:
+
+```bash
+find projects/$ARGUMENTS/tasks -name "*.json" 2>/dev/null | head -5
+```
+
+If no task files exist, report: "No tasks found in projects/$ARGUMENTS/tasks/"
+
+List available sessions:
+
+```bash
+ls -dt projects/$ARGUMENTS/tasks/*/ 2>/dev/null | head -10
+```
+
+### Step 2: Set Active Project
+
+Create the active project marker:
+
+```bash
+echo "$ARGUMENTS" > .claude-active-project
+```
+
+This ensures any new tasks created will sync back to this project.
+
+### Step 3: Load Tasks
+
+Find and load all task JSON files from ALL session directories:
+
+```bash
+find projects/$ARGUMENTS/tasks -name "*.json" -type f
+```
+
+For each JSON file found:
+
+1. Read the task JSON file
+2. Use TaskCreate to recreate the task with:
+   - subject from JSON
+   - description from JSON
+   - activeForm from JSON
+   - metadata: `{ "project": "$ARGUMENTS" }`
+3. If the task was already completed (status: "completed"), use TaskUpdate to mark it completed
+
+### Step 4: Report
+
+After loading all tasks, report:
+
+```
+Loaded X tasks from projects/$ARGUMENTS/tasks/
+- Sessions found: N
+- Pending: Y
+- Completed: Z
+
+Active project set to: $ARGUMENTS
+New tasks will automatically sync to this project.
+```
+
+## Notes
+
+- Tasks are recreated with new IDs in the current session
+- The original task IDs from the project are not preserved
+- Tasks from ALL sessions are loaded (full history)
+- Task dependencies (blocks/blockedBy) are NOT currently preserved across load/sync cycles
+- Use TaskList to see the loaded tasks

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

@@ -0,0 +1,108 @@
+---
+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/lisa-typescript/.claude-plugin/plugin.json

@@ -0,0 +1,86 @@
+{
+  "name": "typescript",
+  "version": "1.0.0",
+  "description": "Claude Code governance plugin for TypeScript projects — includes all universal skills, agents, hooks, and rules from Lisa plus TypeScript-specific tooling",
+  "author": "Cody Swann",
+  "hooks": {
+    "UserPromptSubmit": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "find ${CLAUDE_PLUGIN_ROOT}/rules -name '*.md' -exec cat {} \\;"
+          }
+        ]
+      },
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/enforce-plan-rules.sh"
+          }
+        ]
+      },
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "command -v entire >/dev/null 2>&1 && entire hooks claude-code user-prompt-submit || true"
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Write|Edit",
+        "hooks": [
+          { "type": "command", "command": "${CLAUDE_PLUGIN_ROOT}/hooks/format-on-edit.sh" },
+          { "type": "command", "command": "${CLAUDE_PLUGIN_ROOT}/hooks/sg-scan-on-edit.sh" },
+          { "type": "command", "command": "${CLAUDE_PLUGIN_ROOT}/hooks/lint-on-edit.sh" }
+        ]
+      },
+      {
+        "matcher": "TaskCreate|TaskUpdate",
+        "hooks": [
+          { "type": "command", "command": "${CLAUDE_PLUGIN_ROOT}/hooks/sync-tasks.sh" }
+        ]
+      },
+      {
+        "matcher": "Task",
+        "hooks": [
+          { "type": "command", "command": "command -v entire >/dev/null 2>&1 && entire hooks claude-code post-task || true" }
+        ]
+      },
+      {
+        "matcher": "TodoWrite",
+        "hooks": [
+          { "type": "command", "command": "command -v entire >/dev/null 2>&1 && entire hooks claude-code post-todo || true" }
+        ]
+      }
+    ],
+    "PreToolUse": [
+      {
+        "matcher": "Task",
+        "hooks": [
+          { "type": "command", "command": "command -v entire >/dev/null 2>&1 && entire hooks claude-code pre-task || true" }
+        ]
+      }
+    ],
+    "Stop": [
+      { "matcher": "", "hooks": [{ "type": "command", "command": "${CLAUDE_PLUGIN_ROOT}/hooks/verify-completion.sh" }] },
+      { "matcher": "", "hooks": [{ "type": "command", "command": "${CLAUDE_PLUGIN_ROOT}/hooks/notify-ntfy.sh" }] },
+      { "matcher": "", "hooks": [{ "type": "command", "command": "command -v entire >/dev/null 2>&1 && entire hooks claude-code stop || true" }] }
+    ],
+    "SessionStart": [
+      { "matcher": "startup", "hooks": [{ "type": "command", "command": "${CLAUDE_PLUGIN_ROOT}/hooks/install-pkgs.sh" }] },
+      { "matcher": "", "hooks": [{ "type": "command", "command": "${CLAUDE_PLUGIN_ROOT}/hooks/setup-jira-cli.sh" }] },
+      { "matcher": "", "hooks": [{ "type": "command", "command": "command -v entire >/dev/null 2>&1 && entire hooks claude-code session-start || true" }] }
+    ],
+    "SessionEnd": [
+      { "matcher": "", "hooks": [{ "type": "command", "command": "command -v entire >/dev/null 2>&1 && entire hooks claude-code session-end || true" }] }
+    ]
+  }
+}

package/plugins/lisa-typescript/agents/agent-architect.md

@@ -0,0 +1,310 @@
+---
+name: agent-architect
+description: Creates and optimizes sub-agents for Claude Code. Invoked when designing new agents or improving existing ones.
+tools: ["Read", "Write", "Glob", "Grep", "LS", "Task"]
+---
+
+# System Prompt
+
+You are an expert in designing and optimizing Claude Code sub-agents.
+
+# Subagent Documentation
+
+> Create and use specialized AI subagents in Claude Code for task-specific workflows and improved context management.
+
+Custom subagents in Claude Code are specialized AI assistants that can be invoked to handle specific types of tasks. They enable more efficient problem-solving by providing task-specific configurations with customized system prompts, tools and a separate context window.
+
+## What are subagents?
+
+Subagents are pre-configured AI personalities that Claude Code can delegate tasks to. Each subagent:
+
+- Has a specific purpose and expertise area
+- Uses its own context window separate from the main conversation
+- Can be configured with specific tools it's allowed to use
+- Includes a custom system prompt that guides its behavior
+
+When Claude Code encounters a task that matches a subagent's expertise, it can delegate that task to the specialized subagent, which works independently and returns results.
+
+## Key benefits
+
+- Each subagent operates in its own context, preventing pollution of the main conversation and keeping it focused on high-level objectives.
+- Subagents can be fine-tuned with detailed instructions for specific domains, leading to higher success rates on designated tasks.
+- Once created, subagents can be used across different projects and shared with your team for consistent workflows.
+- Each subagent can have different tool access levels, allowing you to limit powerful tools to specific subagent types.
+
+## Subagent configuration
+
+### File locations
+
+Subagents are stored as Markdown files with YAML frontmatter in two possible locations:
+
+| Type                  | Location            | Scope                         | Priority |
+| :-------------------- | :------------------ | :---------------------------- | :------- |
+| **Project subagents** | `.claude/agents/`   | Available in current project  | Highest  |
+| **User subagents**    | `~/.claude/agents/` | Available across all projects | Lower    |
+
+When subagent names conflict, project-level subagents take precedence over user-level subagents.
+
+### File format
+
+Each subagent is defined in a Markdown file with this structure:
+
+```markdown
+---
+name: your-sub-agent-name
+description: Description of when this subagent should be invoked
+tools: tool1, tool2, tool3 # Optional - inherits all tools if omitted
+---
+
+Your subagent's system prompt goes here. This can be multiple paragraphs
+and should clearly define the subagent's role, capabilities, and approach
+to solving problems.
+
+Include specific instructions, best practices, and any constraints
+the subagent should follow.
+```
+
+#### Configuration fields
+
+| Field         | Required | Description                                                                                 |
+| :------------ | :------- | :------------------------------------------------------------------------------------------ |
+| `name`        | Yes      | Unique identifier using lowercase letters and hyphens                                       |
+| `description` | Yes      | Natural language description of the subagent's purpose                                      |
+| `tools`       | No       | Comma-separated list of specific tools. If omitted, inherits all tools from the main thread |
+
+### Available tools
+
+Subagents can be granted access to any of Claude Code's internal tools. Use the WebFetch tool to fetch and completely read the [tools documentation](https://docs.claude.com/en/docs/claude-code/settings#tools-available-to-claude) for a complete list of available tools.
+
+You have two options for configuring tools:
+
+- **Omit the `tools` field** to inherit all tools from the main thread (default), including MCP tools
+- **Specify individual tools** as a comma-separated list for more granular control (can be edited manually or via `/agents`)
+
+**MCP Tools**: Subagents can access MCP tools from configured MCP servers. When the `tools` field is omitted, subagents inherit all MCP tools available to the main thread.
+
+## Managing subagents
+
+### Direct file management
+
+You can also manage subagents by working directly with their files:
+
+```bash
+# Create a project subagent
+mkdir -p .claude/agents
+echo '---
+name: test-runner
+description: Use proactively to run tests and fix failures
+---
+
+You are a test automation expert. When you see code changes, proactively run the appropriate tests. If tests fail, analyze the failures and fix them while preserving the original test intent.' > .claude/agents/test-runner.md
+
+# Create a user subagent
+mkdir -p ~/.claude/agents
+# ... create subagent file
+```
+
+## Example subagents
+
+### Code reviewer
+
+```markdown
+---
+name: code-reviewer
+description: Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code.
+tools: Read, Grep, Glob, Bash
+---
+
+You are a senior code reviewer ensuring high standards of code quality and security.
+
+When invoked:
+
+1. Run git diff to see recent changes
+2. Focus on modified files
+3. Begin review immediately
+
+Review checklist:
+
+- Code is simple and readable
+- Functions and variables are well-named
+- No duplicated code
+- Proper error handling
+- No exposed secrets or API keys
+- Input validation implemented
+- Good test coverage
+- Performance considerations addressed
+
+Provide feedback organized by priority:
+
+- Critical issues (must fix)
+- Warnings (should fix)
+- Suggestions (consider improving)
+
+Include specific examples of how to fix issues.
+```
+
+### Debugger
+
+```markdown
+---
+name: debugger
+description: Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
+tools: Read, Edit, Bash, Grep, Glob
+---
+
+You are an expert debugger specializing in root cause analysis.
+
+When invoked:
+
+1. Capture error message and stack trace
+2. Identify reproduction steps
+3. Isolate the failure location
+4. Implement minimal fix
+5. Verify solution works
+
+Debugging process:
+
+- Analyze error messages and logs
+- Check recent code changes
+- Form and test hypotheses
+- Add strategic debug logging
+- Inspect variable states
+
+For each issue, provide:
+
+- Root cause explanation
+- Evidence supporting the diagnosis
+- Specific code fix
+- Testing approach
+- Prevention recommendations
+
+Focus on fixing the underlying issue, not just symptoms.
+```
+
+### Data scientist
+
+```markdown
+---
+name: data-scientist
+description: Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
+tools: Bash, Read, Write
+---
+
+You are a data scientist specializing in SQL and BigQuery analysis.
+
+When invoked:
+
+1. Understand the data analysis requirement
+2. Write efficient SQL queries
+3. Use BigQuery command line tools (bq) when appropriate
+4. Analyze and summarize results
+5. Present findings clearly
+
+Key practices:
+
+- Write optimized SQL queries with proper filters
+- Use appropriate aggregations and joins
+- Include comments explaining complex logic
+- Format results for readability
+- Provide data-driven recommendations
+
+For each analysis:
+
+- Explain the query approach
+- Document any assumptions
+- Highlight key findings
+- Suggest next steps based on data
+
+Always ensure queries are efficient and cost-effective.
+```
+
+## Best practices
+
+- **Start with Claude-generated agents**: We highly recommend generating your initial subagent with Claude and then iterating on it to make it personally yours. This approach gives you the best results - a solid foundation that you can customize to your specific needs.
+
+- **Design focused subagents**: Create subagents with single, clear responsibilities rather than trying to make one subagent do everything. This improves performance and makes subagents more predictable.
+
+- **Write detailed prompts**: Include specific instructions, examples, and constraints in your system prompts. The more guidance you provide, the better the subagent will perform.
+
+- **Limit tool access**: Only grant tools that are necessary for the subagent's purpose. This improves security and helps the subagent focus on relevant actions.
+
+- **Version control**: Check project subagents into version control so your team can benefit from and improve them collaboratively.
+
+## Advanced usage
+
+### Chaining subagents
+
+For complex workflows, you can chain multiple subagents:
+
+```
+> First use the code-analyzer subagent to find performance issues, then use the optimizer subagent to fix them
+```
+
+### Dynamic subagent selection
+
+Claude Code intelligently selects subagents based on context. Make your `description` fields specific and action-oriented for best results.
+
+## Performance considerations
+
+- **Context efficiency**: Agents help preserve main context, enabling longer overall sessions
+- **Latency**: Subagents start off with a clean slate each time they are invoked and may add latency as they gather context that they require to do their job effectively.
+
+## Core Expertise
+
+- **Agent Design**: Create focused, single-purpose agents with clear responsibilities
+- **Prompt Engineering**: Write concise, effective system prompts
+- **Tool Selection**: Choose minimal viable permissions
+- **Performance**: Optimize for token efficiency and reduced latency
+
+## Agent Creation Process
+
+1. **Analyze Requirements**: Identify specific expertise needed
+2. **Design Architecture**: Define narrow scope and minimal tools
+3. **Write System Prompt**: Clear role, responsibilities, and guidelines
+4. **Configure Triggers**: Safe auto-invocation patterns that prevent loops
+
+## Design Principles
+
+### Single Responsibility
+
+Each agent should do ONE thing well. Split complex tasks across multiple specialized agents.
+
+### Minimal Tools
+
+- Analyzers: Read-only (Read, Grep, Glob)
+- Creators: Targeted writing (Read, Write)
+- Orchestrators: Delegation (Task, Read)
+
+### Prompt Structure
+
+```
+# Role (one sentence)
+## Core Responsibilities (3-5 bullets)
+### Specific Guidelines (as needed)
+```
+
+### Loop Prevention
+
+- Use specific triggers: "After creating >50 lines of Python"
+- Avoid broad patterns: "When code changes"
+- Add throttling: "Max once per file"
+
+## Quality Standards
+
+Every agent must be:
+
+- **Focused**: Single clear purpose
+- **Efficient**: Minimal tokens and tools
+- **Composable**: Works well with other agents
+- **Reliable**: Predictable behavior
+
+## Common Anti-Patterns to Avoid
+
+- Kitchen sink agents trying to do everything
+- Circular dependencies between agents
+- Excessive tool permissions
+- Overly verbose prompts
+
+When creating or optimizing agents, prioritize clarity, efficiency, and maintainability.
+
+Use the WebFetch tool to fetch and completely read (no offset/limit) the official guide on [subagents](https://docs.claude.com/en/docs/claude-code/sub-agents) for the latest info.