@vicoa/cli 0.1.4-darwin-arm64 → 0.1.4

package/bin/_internal/integrations/github/claude-code-action/examples/issue-deduplication.yml

@@ -1,63 +0,0 @@
-name: Issue Deduplication
-
-on:
-  issues:
-    types: [opened]
-
-jobs:
-  deduplicate:
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    permissions:
-      contents: read
-      issues: write
-      id-token: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 1
-
-      - name: Check for duplicate issues
-        uses: anthropics/claude-code-action@v1-dev
-        with:
-          prompt: |
-            Analyze this new issue and check if it's a duplicate of existing issues in the repository.
-
-            Issue: #${{ github.event.issue.number }}
-            Repository: ${{ github.repository }}
-
-            Your task:
-            1. Use mcp__github__get_issue to get details of the current issue (#${{ github.event.issue.number }})
-            2. Search for similar existing issues using mcp__github__search_issues with relevant keywords from the issue title and body
-            3. Compare the new issue with existing ones to identify potential duplicates
-
-            Criteria for duplicates:
-            - Same bug or error being reported
-            - Same feature request (even if worded differently)
-            - Same question being asked
-            - Issues describing the same root problem
-
-            If you find duplicates:
-            - Add a comment on the new issue linking to the original issue(s)
-            - Apply a "duplicate" label to the new issue
-            - Be polite and explain why it's a duplicate
-            - Suggest the user follow the original issue for updates
-
-            If it's NOT a duplicate:
-            - Don't add any comments
-            - You may apply appropriate topic labels based on the issue content
-
-            Use these tools:
-            - mcp__github__get_issue: Get issue details
-            - mcp__github__search_issues: Search for similar issues
-            - mcp__github__list_issues: List recent issues if needed
-            - mcp__github__create_issue_comment: Add a comment if duplicate found
-            - mcp__github__update_issue: Add labels
-
-            Be thorough but efficient. Focus on finding true duplicates, not just similar issues.
-
-          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-          claude_args: |
-            --allowedTools "mcp__github__get_issue,mcp__github__search_issues,mcp__github__list_issues,mcp__github__create_issue_comment,mcp__github__update_issue,mcp__github__get_issue_comments"

package/bin/_internal/integrations/github/claude-code-action/examples/issue-triage.yml

@@ -1,75 +0,0 @@
-name: Issue Triage
-on:
-  issues:
-    types: [opened]
-
-jobs:
-  triage-issue:
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    permissions:
-      contents: read
-      issues: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Triage issue with Claude
-        uses: anthropics/claude-code-action@v1-dev
-        with:
-          prompt: |
-            You're an issue triage assistant for GitHub issues. Your task is to analyze the issue and select appropriate labels from the provided list.
-
-            IMPORTANT: Don't post any comments or messages to the issue. Your only action should be to apply labels.
-
-            Issue Information:
-            - REPO: ${{ github.repository }}
-            - ISSUE_NUMBER: ${{ github.event.issue.number }}
-
-            TASK OVERVIEW:
-
-            1. First, fetch the list of labels available in this repository by running: `gh label list`. Run exactly this command with nothing else.
-
-            2. Next, use the GitHub tools to get context about the issue:
-               - You have access to these tools:
-                 - mcp__github__get_issue: Use this to retrieve the current issue's details including title, description, and existing labels
-                 - mcp__github__get_issue_comments: Use this to read any discussion or additional context provided in the comments
-                 - mcp__github__update_issue: Use this to apply labels to the issue (do not use this for commenting)
-                 - mcp__github__search_issues: Use this to find similar issues that might provide context for proper categorization and to identify potential duplicate issues
-                 - mcp__github__list_issues: Use this to understand patterns in how other issues are labeled
-               - Start by using mcp__github__get_issue to get the issue details
-
-            3. Analyze the issue content, considering:
-               - The issue title and description
-               - The type of issue (bug report, feature request, question, etc.)
-               - Technical areas mentioned
-               - Severity or priority indicators
-               - User impact
-               - Components affected
-
-            4. Select appropriate labels from the available labels list provided above:
-               - Choose labels that accurately reflect the issue's nature
-               - Be specific but comprehensive
-               - Select priority labels if you can determine urgency (high-priority, med-priority, or low-priority)
-               - Consider platform labels (android, ios) if applicable
-               - If you find similar issues using mcp__github__search_issues, consider using a "duplicate" label if appropriate. Only do so if the issue is a duplicate of another OPEN issue.
-
-            5. Apply the selected labels:
-               - Use mcp__github__update_issue to apply your selected labels
-               - DO NOT post any comments explaining your decision
-               - DO NOT communicate directly with users
-               - If no labels are clearly applicable, do not apply any labels
-
-            IMPORTANT GUIDELINES:
-            - Be thorough in your analysis
-            - Only select labels from the provided list above
-            - DO NOT post any comments to the issue
-            - Your ONLY action should be to apply labels using mcp__github__update_issue
-            - It's okay to not add any labels if none are clearly applicable
-
-          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-          claude_args: |
-            --allowedTools "Bash(gh label list),mcp__github__get_issue,mcp__github__get_issue_comments,mcp__github__update_issue,mcp__github__search_issues,mcp__github__list_issues"

package/bin/_internal/integrations/github/claude-code-action/examples/vicoa.yml

@@ -1,75 +0,0 @@
-name: Vicoa AI Assistant
-
-on:
-  # Trigger via repository_dispatch (from Vicoa dashboard)
-  repository_dispatch:
-    types: [vicoa-trigger]
-  
-  # Direct triggers from GitHub events (for @vicoa mentions)
-  issue_comment:
-    types: [created]
-  pull_request_review_comment:
-    types: [created]
-
-permissions:
-  contents: write
-  issues: write
-  pull-requests: write
-  actions: write
-  id-token: write  # Required for OIDC
-
-jobs:
-  vicoa-assistant:
-    runs-on: ubuntu-latest
-    
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0  # Fetch all history for all branches
-      
-      - name: Setup branch from payload
-        if: github.event.client_payload.branch_name
-        run: |
-          BRANCH_NAME="${{ github.event.client_payload.branch_name }}"
-          echo "Branch requested: $BRANCH_NAME"
-          
-          # Check if branch exists remotely
-          if git ls-remote --heads origin "$BRANCH_NAME" | grep -q "$BRANCH_NAME"; then
-            echo "Branch exists, checking it out..."
-            git checkout "$BRANCH_NAME"
-          else
-            echo "Branch doesn't exist, creating new branch from main..."
-            # Fetch main branch first
-            git checkout main || git checkout master || git checkout $(git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@')
-            git pull origin $(git branch --show-current)
-            # Create and checkout new branch
-            git checkout -b "$BRANCH_NAME"
-            echo "Created new branch: $BRANCH_NAME"
-          fi
-      
-      - name: Run Vicoa Claude Code Action
-        uses: vicoa-ai/vicoa/src/integrations/github/claude-code-action@main
-        with:
-          # The prompt will come from repository_dispatch payload
-          # For @vicoa mentions, the action auto-detects from comments
-          prompt: ${{ github.event.client_payload.prompt }}
-          
-          # Claude configuration using new v1.0 claude_args format
-          claude_args: |
-            --max-turns 30
-            --model claude-3-5-sonnet-latest
-          
-          # Override trigger phrase to use @vicoa instead of @claude
-          trigger_phrase: "@vicoa"
-          
-          # Authentication for Claude
-          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-          
-        env:
-          # Vicoa configuration - automatically activates Vicoa when:
-          # 1. VICOA_API_KEY is present AND
-          # 2. Either triggered by repository_dispatch OR @vicoa mention
-          VICOA_API_KEY: ${{ github.event.client_payload.vicoa_api_key || secrets.VICOA_API_KEY }}
-          VICOA_AGENT_INSTANCE_ID: ${{ github.event.client_payload.agent_instance_id || format('vicoa-{0}', github.run_id) }}
-          VICOA_AGENT_TYPE: ${{ github.event.client_payload.agent_type || 'Claude Code' }}

package/bin/_internal/integrations/github/claude-code-action/package.json

@@ -1,31 +0,0 @@
-{
-  "name": "@anthropic-ai/claude-code-action",
-  "version": "1.0.0",
-  "private": true,
-  "scripts": {
-    "format": "prettier --write .",
-    "format:check": "prettier --check .",
-    "install-hooks": "bun run scripts/install-hooks.sh",
-    "test": "bun test",
-    "typecheck": "tsc --noEmit"
-  },
-  "dependencies": {
-    "@actions/core": "^1.10.1",
-    "@actions/github": "^6.0.1",
-    "@modelcontextprotocol/sdk": "^1.11.0",
-    "@octokit/graphql": "^8.2.2",
-    "@octokit/rest": "^21.1.1",
-    "@octokit/webhooks-types": "^7.6.1",
-    "node-fetch": "^3.3.2",
-    "shell-quote": "^1.8.3",
-    "zod": "^3.24.4"
-  },
-  "devDependencies": {
-    "@types/bun": "1.2.11",
-    "@types/node": "^20.0.0",
-    "@types/node-fetch": "^2.6.12",
-    "@types/shell-quote": "^1.7.5",
-    "prettier": "3.5.3",
-    "typescript": "^5.8.3"
-  }
-}

package/bin/_internal/integrations/github/claude-code-action/scripts/install-hooks.sh

@@ -1,13 +0,0 @@
-#!/bin/sh
-
-# Install git hooks
-echo "Installing git hooks..."
-
-# Make sure hooks directory exists
-mkdir -p .git/hooks
-
-# Install pre-commit hook
-cp scripts/pre-commit .git/hooks/pre-commit
-chmod +x .git/hooks/pre-commit
-
-echo "Git hooks installed successfully!"

package/bin/_internal/integrations/github/claude-code-action/scripts/pre-commit

@@ -1,46 +0,0 @@
-#!/bin/sh
-
-# Check if files need formatting before push
-echo "Checking code formatting..."
-
-# First check if any files need formatting
-if ! bun run format:check; then
-    echo "Code formatting errors found. Running formatter..."
-    bun run format
-
-    # Check if there are any staged changes after formatting
-    if git diff --name-only --exit-code; then
-        echo "All files are now properly formatted."
-    else
-        echo ""
-        echo "ERROR: Code has been formatted but changes need to be committed!"
-        echo "Please commit the formatted files and try again."
-        echo ""
-        echo "The following files were modified:"
-        git diff --name-only
-        echo ""
-        exit 1
-    fi
-else
-    echo "Code formatting is already correct."
-fi
-
-# Run type checking
-echo "Running type checking..."
-if ! bun run typecheck; then
-    echo "Type checking failed. Please fix the type errors and try again."
-    exit 1
-else
-    echo "Type checking passed."
-fi
-
-# Run tests
-echo "Running tests..."
-if ! bun run test; then
-    echo "Tests failed. Please fix the failing tests and try again."
-    exit 1
-else
-    echo "All tests passed."
-fi
-
-exit 0

package/bin/_internal/integrations/github/claude-code-action/scripts/setup-network-restrictions.sh

@@ -1,123 +0,0 @@
-#!/bin/bash
-
-# Setup Network Restrictions with Squid Proxy
-# This script sets up a Squid proxy to restrict network access to whitelisted domains only.
-
-set -e
-
-# Check if experimental_allowed_domains is provided
-if [ -z "$EXPERIMENTAL_ALLOWED_DOMAINS" ]; then
-  echo "ERROR: EXPERIMENTAL_ALLOWED_DOMAINS environment variable is required"
-  exit 1
-fi
-
-# Check required environment variables
-if [ -z "$RUNNER_TEMP" ]; then
-  echo "ERROR: RUNNER_TEMP environment variable is required"
-  exit 1
-fi
-
-if [ -z "$GITHUB_ENV" ]; then
-  echo "ERROR: GITHUB_ENV environment variable is required"
-  exit 1
-fi
-
-echo "Setting up network restrictions with Squid proxy..."
-
-SQUID_START_TIME=$(date +%s.%N)
-
-# Create whitelist file
-echo "$EXPERIMENTAL_ALLOWED_DOMAINS" > $RUNNER_TEMP/whitelist.txt
-
-# Ensure each domain has proper format
-# If domain doesn't start with a dot and isn't an IP, add the dot for subdomain matching
-mv $RUNNER_TEMP/whitelist.txt $RUNNER_TEMP/whitelist.txt.orig
-while IFS= read -r domain; do
-  if [ -n "$domain" ]; then
-    # Trim whitespace
-    domain=$(echo "$domain" | xargs)
-    # If it's not empty and doesn't start with a dot, add one
-    if [[ "$domain" != .* ]] && [[ ! "$domain" =~ ^[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+$ ]]; then
-      echo ".$domain" >> $RUNNER_TEMP/whitelist.txt
-    else
-      echo "$domain" >> $RUNNER_TEMP/whitelist.txt
-    fi
-  fi
-done < $RUNNER_TEMP/whitelist.txt.orig
-
-# Create Squid config with whitelist
-echo "http_port 3128" > $RUNNER_TEMP/squid.conf
-echo "" >> $RUNNER_TEMP/squid.conf
-echo "# Define ACLs" >> $RUNNER_TEMP/squid.conf
-echo "acl whitelist dstdomain \"/etc/squid/whitelist.txt\"" >> $RUNNER_TEMP/squid.conf
-echo "acl localnet src 127.0.0.1/32" >> $RUNNER_TEMP/squid.conf
-echo "acl localnet src 172.17.0.0/16" >> $RUNNER_TEMP/squid.conf
-echo "acl SSL_ports port 443" >> $RUNNER_TEMP/squid.conf
-echo "acl Safe_ports port 80" >> $RUNNER_TEMP/squid.conf
-echo "acl Safe_ports port 443" >> $RUNNER_TEMP/squid.conf
-echo "acl CONNECT method CONNECT" >> $RUNNER_TEMP/squid.conf
-echo "" >> $RUNNER_TEMP/squid.conf
-echo "# Deny requests to certain unsafe ports" >> $RUNNER_TEMP/squid.conf
-echo "http_access deny !Safe_ports" >> $RUNNER_TEMP/squid.conf
-echo "" >> $RUNNER_TEMP/squid.conf
-echo "# Only allow CONNECT to SSL ports" >> $RUNNER_TEMP/squid.conf
-echo "http_access deny CONNECT !SSL_ports" >> $RUNNER_TEMP/squid.conf
-echo "" >> $RUNNER_TEMP/squid.conf
-echo "# Allow localhost" >> $RUNNER_TEMP/squid.conf
-echo "http_access allow localhost" >> $RUNNER_TEMP/squid.conf
-echo "" >> $RUNNER_TEMP/squid.conf
-echo "# Allow localnet access to whitelisted domains" >> $RUNNER_TEMP/squid.conf
-echo "http_access allow localnet whitelist" >> $RUNNER_TEMP/squid.conf
-echo "" >> $RUNNER_TEMP/squid.conf
-echo "# Deny everything else" >> $RUNNER_TEMP/squid.conf
-echo "http_access deny all" >> $RUNNER_TEMP/squid.conf
-
-echo "Starting Squid proxy..."
-# First, remove any existing container
-sudo docker rm -f squid-proxy 2>/dev/null || true
-
-# Ensure whitelist file is not empty (Squid fails with empty files)
-if [ ! -s "$RUNNER_TEMP/whitelist.txt" ]; then
-  echo "WARNING: Whitelist file is empty, adding a dummy entry"
-  echo ".example.com" >> $RUNNER_TEMP/whitelist.txt
-fi
-
-# Use sudo to prevent Claude from stopping the container
-CONTAINER_ID=$(sudo docker run -d \
-  --name squid-proxy \
-  -p 127.0.0.1:3128:3128 \
-  -v $RUNNER_TEMP/squid.conf:/etc/squid/squid.conf:ro \
-  -v $RUNNER_TEMP/whitelist.txt:/etc/squid/whitelist.txt:ro \
-  ubuntu/squid:latest 2>&1) || {
-  echo "ERROR: Failed to start Squid container"
-  exit 1
-}
-
-# Wait for proxy to be ready (usually < 1 second)
-READY=false
-for i in {1..30}; do
-  if nc -z 127.0.0.1 3128 2>/dev/null; then
-    TOTAL_TIME=$(echo "scale=3; $(date +%s.%N) - $SQUID_START_TIME" | bc)
-    echo "Squid proxy ready in ${TOTAL_TIME}s"
-    READY=true
-    break
-  fi
-  sleep 0.1
-done
-
-if [ "$READY" != "true" ]; then
-  echo "ERROR: Squid proxy failed to start within 3 seconds"
-  echo "Container logs:"
-  sudo docker logs squid-proxy 2>&1 || true
-  echo "Container status:"
-  sudo docker ps -a | grep squid-proxy || true
-  exit 1
-fi
-
-# Set proxy environment variables
-echo "http_proxy=http://127.0.0.1:3128" >> $GITHUB_ENV
-echo "https_proxy=http://127.0.0.1:3128" >> $GITHUB_ENV
-echo "HTTP_PROXY=http://127.0.0.1:3128" >> $GITHUB_ENV
-echo "HTTPS_PROXY=http://127.0.0.1:3128" >> $GITHUB_ENV
-
-echo "Network restrictions setup completed successfully"