@vicoa/cli 1.3.11-linux-x64 → 1.3.11-win32-x64

package/bin/_internal/integrations/github/claude-code-action/docs/custom-automations.md

@@ -1,113 +1,113 @@
-# Custom Automations
-
-These examples show how to configure Claude to act automatically based on GitHub events. When you provide a `prompt` input, the action automatically runs in agent mode without requiring manual @mentions. Without a `prompt`, it runs in interactive mode, responding to @claude mentions.
-
-## Supported GitHub Events
-
-This action supports the following GitHub events ([learn more GitHub event triggers](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows)):
-
-- `pull_request` - When PRs are opened or synchronized
-- `issue_comment` - When comments are created on issues or PRs
-- `pull_request_comment` - When comments are made on PR diffs
-- `issues` - When issues are opened or assigned
-- `pull_request_review` - When PR reviews are submitted
-- `pull_request_review_comment` - When comments are made on PR reviews
-- `repository_dispatch` - Custom events triggered via API (coming soon)
-- `workflow_dispatch` - Manual workflow triggers (coming soon)
-
-## Automated Documentation Updates
-
-Automatically update documentation when specific files change (see [`examples/claude-pr-path-specific.yml`](../examples/claude-pr-path-specific.yml)):
-
-```yaml
-on:
-  pull_request:
-    paths:
-      - "src/api/**/*.ts"
-
-steps:
-  - uses: anthropics/claude-code-action@v1
-    with:
-      prompt: |
-        Update the API documentation in README.md to reflect
-        the changes made to the API endpoints in this PR.
-      anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-```
-
-When API files are modified, the action automatically detects that a `prompt` is provided and runs in agent mode. Claude updates your README with the latest endpoint documentation and pushes the changes back to the PR, keeping your docs in sync with your code.
-
-## Author-Specific Code Reviews
-
-Automatically review PRs from specific authors or external contributors (see [`examples/claude-review-from-author.yml`](../examples/claude-review-from-author.yml)):
-
-```yaml
-on:
-  pull_request:
-    types: [opened, synchronize]
-
-jobs:
-  review-by-author:
-    if: |
-      github.event.pull_request.user.login == 'developer1' ||
-      github.event.pull_request.user.login == 'external-contributor'
-    steps:
-      - uses: anthropics/claude-code-action@v1
-        with:
-          prompt: |
-            Please provide a thorough review of this pull request.
-            Pay extra attention to coding standards, security practices,
-            and test coverage since this is from an external contributor.
-          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-```
-
-Perfect for automatically reviewing PRs from new team members, external contributors, or specific developers who need extra guidance. The action automatically runs in agent mode when a `prompt` is provided.
-
-## Custom Prompt Templates
-
-Use the `prompt` input with GitHub context variables for dynamic automation:
-
-```yaml
-- uses: anthropics/claude-code-action@v1
-  with:
-    prompt: |
-      Analyze PR #${{ github.event.pull_request.number }} in ${{ github.repository }} for security vulnerabilities.
-
-      Focus on:
-      - SQL injection risks
-      - XSS vulnerabilities
-      - Authentication bypasses
-      - Exposed secrets or credentials
-
-      Provide severity ratings (Critical/High/Medium/Low) for any issues found.
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-```
-
-You can access any GitHub context variable using the standard GitHub Actions syntax:
-
-- `${{ github.repository }}` - The repository name
-- `${{ github.event.pull_request.number }}` - PR number
-- `${{ github.event.issue.number }}` - Issue number
-- `${{ github.event.pull_request.title }}` - PR title
-- `${{ github.event.pull_request.body }}` - PR description
-- `${{ github.event.comment.body }}` - Comment text
-- `${{ github.actor }}` - User who triggered the workflow
-- `${{ github.base_ref }}` - Base branch for PRs
-- `${{ github.head_ref }}` - Head branch for PRs
-
-## Advanced Configuration with claude_args
-
-For more control over Claude's behavior, use the `claude_args` input to pass CLI arguments directly:
-
-```yaml
-- uses: anthropics/claude-code-action@v1
-  with:
-    prompt: "Review this PR for performance issues"
-    claude_args: |
-      --max-turns 15
-      --model claude-4-0-sonnet-20250805
-      --allowedTools Edit,Read,Write,Bash
-      --system-prompt "You are a performance optimization expert. Focus on identifying bottlenecks and suggesting improvements."
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-```
-
-This provides full access to Claude Code CLI capabilities while maintaining the simplified action interface.
+# Custom Automations
+
+These examples show how to configure Claude to act automatically based on GitHub events. When you provide a `prompt` input, the action automatically runs in agent mode without requiring manual @mentions. Without a `prompt`, it runs in interactive mode, responding to @claude mentions.
+
+## Supported GitHub Events
+
+This action supports the following GitHub events ([learn more GitHub event triggers](https://docs.github.com/en/actions/writing-workflows/choosing-when-your-workflow-runs/events-that-trigger-workflows)):
+
+- `pull_request` - When PRs are opened or synchronized
+- `issue_comment` - When comments are created on issues or PRs
+- `pull_request_comment` - When comments are made on PR diffs
+- `issues` - When issues are opened or assigned
+- `pull_request_review` - When PR reviews are submitted
+- `pull_request_review_comment` - When comments are made on PR reviews
+- `repository_dispatch` - Custom events triggered via API (coming soon)
+- `workflow_dispatch` - Manual workflow triggers (coming soon)
+
+## Automated Documentation Updates
+
+Automatically update documentation when specific files change (see [`examples/claude-pr-path-specific.yml`](../examples/claude-pr-path-specific.yml)):
+
+```yaml
+on:
+  pull_request:
+    paths:
+      - "src/api/**/*.ts"
+
+steps:
+  - uses: anthropics/claude-code-action@v1
+    with:
+      prompt: |
+        Update the API documentation in README.md to reflect
+        the changes made to the API endpoints in this PR.
+      anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+```
+
+When API files are modified, the action automatically detects that a `prompt` is provided and runs in agent mode. Claude updates your README with the latest endpoint documentation and pushes the changes back to the PR, keeping your docs in sync with your code.
+
+## Author-Specific Code Reviews
+
+Automatically review PRs from specific authors or external contributors (see [`examples/claude-review-from-author.yml`](../examples/claude-review-from-author.yml)):
+
+```yaml
+on:
+  pull_request:
+    types: [opened, synchronize]
+
+jobs:
+  review-by-author:
+    if: |
+      github.event.pull_request.user.login == 'developer1' ||
+      github.event.pull_request.user.login == 'external-contributor'
+    steps:
+      - uses: anthropics/claude-code-action@v1
+        with:
+          prompt: |
+            Please provide a thorough review of this pull request.
+            Pay extra attention to coding standards, security practices,
+            and test coverage since this is from an external contributor.
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+```
+
+Perfect for automatically reviewing PRs from new team members, external contributors, or specific developers who need extra guidance. The action automatically runs in agent mode when a `prompt` is provided.
+
+## Custom Prompt Templates
+
+Use the `prompt` input with GitHub context variables for dynamic automation:
+
+```yaml
+- uses: anthropics/claude-code-action@v1
+  with:
+    prompt: |
+      Analyze PR #${{ github.event.pull_request.number }} in ${{ github.repository }} for security vulnerabilities.
+
+      Focus on:
+      - SQL injection risks
+      - XSS vulnerabilities
+      - Authentication bypasses
+      - Exposed secrets or credentials
+
+      Provide severity ratings (Critical/High/Medium/Low) for any issues found.
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+```
+
+You can access any GitHub context variable using the standard GitHub Actions syntax:
+
+- `${{ github.repository }}` - The repository name
+- `${{ github.event.pull_request.number }}` - PR number
+- `${{ github.event.issue.number }}` - Issue number
+- `${{ github.event.pull_request.title }}` - PR title
+- `${{ github.event.pull_request.body }}` - PR description
+- `${{ github.event.comment.body }}` - Comment text
+- `${{ github.actor }}` - User who triggered the workflow
+- `${{ github.base_ref }}` - Base branch for PRs
+- `${{ github.head_ref }}` - Head branch for PRs
+
+## Advanced Configuration with claude_args
+
+For more control over Claude's behavior, use the `claude_args` input to pass CLI arguments directly:
+
+```yaml
+- uses: anthropics/claude-code-action@v1
+  with:
+    prompt: "Review this PR for performance issues"
+    claude_args: |
+      --max-turns 15
+      --model claude-4-0-sonnet-20250805
+      --allowedTools Edit,Read,Write,Bash
+      --system-prompt "You are a performance optimization expert. Focus on identifying bottlenecks and suggesting improvements."
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+```
+
+This provides full access to Claude Code CLI capabilities while maintaining the simplified action interface.

package/bin/_internal/integrations/github/claude-code-action/docs/experimental.md

@@ -1,128 +1,128 @@
-# Experimental Features
-
-**Note:** Experimental features are considered unstable and not supported for production use. They may change or be removed at any time.
-
-## Automatic Mode Detection
-
-The action intelligently detects the appropriate execution mode based on your workflow context, eliminating the need for manual mode configuration.
-
-### Interactive Mode (Tag Mode)
-
-Activated when Claude detects @mentions, issue assignments, or labels—without an explicit `prompt`.
-
-- **Triggers**: `@claude` mentions in comments, issue assignment to claude user, label application
-- **Features**: Creates tracking comments with progress checkboxes, full implementation capabilities
-- **Use case**: Interactive code assistance, Q&A, and implementation requests
-
-```yaml
-- uses: anthropics/claude-code-action@v1
-  with:
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    # No prompt needed - responds to @claude mentions
-```
-
-### Automation Mode (Agent Mode)
-
-Automatically activated when you provide a `prompt` input.
-
-- **Triggers**: Any GitHub event when `prompt` input is provided
-- **Features**: Direct execution without requiring @claude mentions, streamlined for automation
-- **Use case**: Automated PR reviews, scheduled tasks, workflow automation
-
-```yaml
-- uses: anthropics/claude-code-action@v1
-  with:
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    prompt: |
-      Check for outdated dependencies and create an issue if any are found.
-    # Automatically runs in agent mode when prompt is provided
-```
-
-### How It Works
-
-The action uses this logic to determine the mode:
-
-1. **If `prompt` is provided** → Runs in **agent mode** for automation
-2. **If no `prompt` but @claude is mentioned** → Runs in **tag mode** for interaction
-3. **If neither** → No action is taken
-
-This automatic detection ensures your workflows are simpler and more intuitive, without needing to understand or configure different modes.
-
-### Advanced Mode Control
-
-For specialized use cases, you can fine-tune behavior using `claude_args`:
-
-```yaml
-- uses: anthropics/claude-code-action@v1
-  with:
-    prompt: "Review this PR"
-    claude_args: |
-      --max-turns 20
-      --system-prompt "You are a code review specialist"
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-```
-
-## Network Restrictions
-
-For enhanced security, you can restrict Claude's network access to specific domains only. This feature is particularly useful for:
-
-- Enterprise environments with strict security policies
-- Preventing access to external services
-- Limiting Claude to only your internal APIs and services
-
-When `experimental_allowed_domains` is set, Claude can only access the domains you explicitly list. You'll need to include the appropriate provider domains based on your authentication method.
-
-### Provider-Specific Examples
-
-#### If using Anthropic API or subscription
-
-```yaml
-- uses: anthropics/claude-code-action@v1
-  with:
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    # Or: claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
-    experimental_allowed_domains: |
-      .anthropic.com
-```
-
-#### If using AWS Bedrock
-
-```yaml
-- uses: anthropics/claude-code-action@v1
-  with:
-    use_bedrock: "true"
-    experimental_allowed_domains: |
-      bedrock.*.amazonaws.com
-      bedrock-runtime.*.amazonaws.com
-```
-
-#### If using Google Vertex AI
-
-```yaml
-- uses: anthropics/claude-code-action@v1
-  with:
-    use_vertex: "true"
-    experimental_allowed_domains: |
-      *.googleapis.com
-      vertexai.googleapis.com
-```
-
-### Common GitHub Domains
-
-In addition to your provider domains, you may need to include GitHub-related domains. For GitHub.com users, common domains include:
-
-```yaml
-- uses: anthropics/claude-code-action@v1
-  with:
-    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-    experimental_allowed_domains: |
-      .anthropic.com  # For Anthropic API
-      .github.com
-      .githubusercontent.com
-      ghcr.io
-      .blob.core.windows.net
-```
-
-For GitHub Enterprise users, replace the GitHub.com domains above with your enterprise domains (e.g., `.github.company.com`, `packages.company.com`, etc.).
-
-To determine which domains your workflow needs, you can temporarily run without restrictions and monitor the network requests, or check your GitHub Enterprise configuration for the specific services you use.
+# Experimental Features
+
+**Note:** Experimental features are considered unstable and not supported for production use. They may change or be removed at any time.
+
+## Automatic Mode Detection
+
+The action intelligently detects the appropriate execution mode based on your workflow context, eliminating the need for manual mode configuration.
+
+### Interactive Mode (Tag Mode)
+
+Activated when Claude detects @mentions, issue assignments, or labels—without an explicit `prompt`.
+
+- **Triggers**: `@claude` mentions in comments, issue assignment to claude user, label application
+- **Features**: Creates tracking comments with progress checkboxes, full implementation capabilities
+- **Use case**: Interactive code assistance, Q&A, and implementation requests
+
+```yaml
+- uses: anthropics/claude-code-action@v1
+  with:
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    # No prompt needed - responds to @claude mentions
+```
+
+### Automation Mode (Agent Mode)
+
+Automatically activated when you provide a `prompt` input.
+
+- **Triggers**: Any GitHub event when `prompt` input is provided
+- **Features**: Direct execution without requiring @claude mentions, streamlined for automation
+- **Use case**: Automated PR reviews, scheduled tasks, workflow automation
+
+```yaml
+- uses: anthropics/claude-code-action@v1
+  with:
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    prompt: |
+      Check for outdated dependencies and create an issue if any are found.
+    # Automatically runs in agent mode when prompt is provided
+```
+
+### How It Works
+
+The action uses this logic to determine the mode:
+
+1. **If `prompt` is provided** → Runs in **agent mode** for automation
+2. **If no `prompt` but @claude is mentioned** → Runs in **tag mode** for interaction
+3. **If neither** → No action is taken
+
+This automatic detection ensures your workflows are simpler and more intuitive, without needing to understand or configure different modes.
+
+### Advanced Mode Control
+
+For specialized use cases, you can fine-tune behavior using `claude_args`:
+
+```yaml
+- uses: anthropics/claude-code-action@v1
+  with:
+    prompt: "Review this PR"
+    claude_args: |
+      --max-turns 20
+      --system-prompt "You are a code review specialist"
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+```
+
+## Network Restrictions
+
+For enhanced security, you can restrict Claude's network access to specific domains only. This feature is particularly useful for:
+
+- Enterprise environments with strict security policies
+- Preventing access to external services
+- Limiting Claude to only your internal APIs and services
+
+When `experimental_allowed_domains` is set, Claude can only access the domains you explicitly list. You'll need to include the appropriate provider domains based on your authentication method.
+
+### Provider-Specific Examples
+
+#### If using Anthropic API or subscription
+
+```yaml
+- uses: anthropics/claude-code-action@v1
+  with:
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    # Or: claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
+    experimental_allowed_domains: |
+      .anthropic.com
+```
+
+#### If using AWS Bedrock
+
+```yaml
+- uses: anthropics/claude-code-action@v1
+  with:
+    use_bedrock: "true"
+    experimental_allowed_domains: |
+      bedrock.*.amazonaws.com
+      bedrock-runtime.*.amazonaws.com
+```
+
+#### If using Google Vertex AI
+
+```yaml
+- uses: anthropics/claude-code-action@v1
+  with:
+    use_vertex: "true"
+    experimental_allowed_domains: |
+      *.googleapis.com
+      vertexai.googleapis.com
+```
+
+### Common GitHub Domains
+
+In addition to your provider domains, you may need to include GitHub-related domains. For GitHub.com users, common domains include:
+
+```yaml
+- uses: anthropics/claude-code-action@v1
+  with:
+    anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+    experimental_allowed_domains: |
+      .anthropic.com  # For Anthropic API
+      .github.com
+      .githubusercontent.com
+      ghcr.io
+      .blob.core.windows.net
+```
+
+For GitHub Enterprise users, replace the GitHub.com domains above with your enterprise domains (e.g., `.github.company.com`, `packages.company.com`, etc.).
+
+To determine which domains your workflow needs, you can temporarily run without restrictions and monitor the network requests, or check your GitHub Enterprise configuration for the specific services you use.