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

package/bin/_internal/integrations/github/claude-code-action/examples/auto-fix-ci-signed/commands/fix-ci-signed.md

@@ -1,148 +1,148 @@
----
-description: Analyze and fix CI failures with signed commits using MCP tools
-allowed_tools: Edit,MultiEdit,Write,Read,Glob,Grep,LS,Bash(bun:*),Bash(npm:*),Bash(npx:*),Bash(gh:*),mcp__github_file_ops__commit_files,mcp__github_file_ops__delete_files
----
-
-# Fix CI Failures with Signed Commits
-
-You are tasked with analyzing CI failure logs and fixing the issues using MCP tools for signed commits. Follow these steps:
-
-## Context Provided
-
-$ARGUMENTS
-
-## Important Context Information
-
-Look for these key pieces of information in the arguments:
-
-- **Failed CI Run URL**: Link to the failed CI run
-- **Failed Jobs**: List of jobs that failed
-- **PR Number**: The PR number to comment on
-- **Branch Name**: The fix branch you're working on
-- **Base Branch**: The original PR branch
-- **Error logs**: Detailed logs from failed jobs
-
-## CRITICAL: Use MCP Tools for Git Operations
-
-**IMPORTANT**: You MUST use MCP tools for all git operations to ensure commits are properly signed. DO NOT use `git` commands directly via Bash.
-
-- Use `mcp__github_file_ops__commit_files` to commit and push changes
-- Use `mcp__github_file_ops__delete_files` to delete files
-
-## Step 1: Analyze the Failure
-
-Parse the provided CI failure information to understand:
-
-- Which jobs failed and why
-- The specific error messages and stack traces
-- Whether failures are test-related, build-related, or linting issues
-
-## Step 2: Search and Understand the Codebase
-
-Use MCP search tools to locate the failing code:
-
-- Use `mcp_github_file_ops_server__search_files` or `mcp_github_file_ops_server__file_search` to find failing test names or functions
-- Use `mcp_github_file_ops_server__read_file` to read source files mentioned in error messages
-- Review related configuration files (package.json, tsconfig.json, etc.)
-
-## Step 3: Apply Targeted Fixes
-
-Make minimal, focused changes:
-
-- **For test failures**: Determine if the test or implementation needs fixing
-- **For type errors**: Fix type definitions or correct the code logic
-- **For linting issues**: Apply formatting using the project's tools
-- **For build errors**: Resolve dependency or configuration issues
-- **For missing imports**: Add the necessary imports or install packages
-
-Requirements:
-
-- Only fix the actual CI failures, avoid unrelated changes
-- Follow existing code patterns and conventions
-- Ensure changes are production-ready, not temporary hacks
-- Preserve existing functionality while fixing issues
-
-## Step 4: Verify Fixes Locally
-
-Run available verification commands using Bash:
-
-- Execute the failing tests locally to confirm they pass
-- Run the project's lint command (check package.json for scripts)
-- Run type checking if available
-- Execute any build commands to ensure compilation succeeds
-
-## Step 5: Commit and Push Changes Using MCP
-
-**CRITICAL**: You MUST use MCP tools for committing and pushing:
-
-1. Prepare all your file changes (using Edit/MultiEdit/Write tools as needed)
-2. **Use `mcp__github_file_ops__commit_files` to commit and push all changes**
-   - Pass the file paths you've edited in the `files` array
-   - Set `message` to describe the specific fixes (e.g., "Fix CI failures: remove syntax errors and format code")
-   - The MCP tool will automatically create the branch specified in "Branch Name:" from the context and push signed commits
-
-**IMPORTANT**: The MCP tool will create the branch from the context automatically. The branch name from "Branch Name:" in the context will be used.
-
-Example usage:
-
-```
-mcp__github_file_ops__commit_files with:
-- files: ["src/utils/retry.ts", "src/other/file.ts"]  // List of file paths you edited
-- message: "Fix CI failures: [describe specific fixes]"
-```
-
-Note: The branch will be created from the Base Branch specified in the context.
-
-## Step 6: Create PR Comment (REQUIRED - DO NOT SKIP)
-
-**CRITICAL: You MUST create a PR comment after pushing. This step is MANDATORY.**
-
-After successfully pushing the fixes, you MUST create a comment on the original PR to notify about the auto-fix. DO NOT end the task without completing this step.
-
-1. Extract the PR number from the context provided in arguments (look for "PR Number:" in the context)
-2. **MANDATORY**: Execute the gh CLI command below to create the comment
-3. Verify the comment was created successfully
-
-**YOU MUST RUN THIS COMMAND** (replace placeholders with actual values from context):
-
-```bash
-gh pr comment PR_NUMBER --body "## 🤖 CI Auto-Fix Available (Signed Commits)
-
-Claude has analyzed the CI failures and prepared fixes with signed commits.
-
-[**→ Create pull request to fix CI**](https://github.com/OWNER/REPO/compare/BASE_BRANCH...FIX_BRANCH?quick_pull=1)
-
-_This fix was generated automatically based on the [failed CI run](FAILED_CI_RUN_URL)._"
-```
-
-**IMPORTANT REPLACEMENTS YOU MUST MAKE:**
-
-- Replace `PR_NUMBER` with the actual PR number from "PR Number:" in context
-- Replace `OWNER/REPO` with the repository from "Repository:" in context
-- Replace `BASE_BRANCH` with the branch from "Base Branch:" in context
-- Replace `FIX_BRANCH` with the branch from "Branch Name:" in context
-- Replace `FAILED_CI_RUN_URL` with the URL from "Failed CI Run:" in context
-
-**DO NOT SKIP THIS STEP. The task is NOT complete until the PR comment is created.**
-
-## Step 7: Final Verification
-
-**BEFORE CONSIDERING THE TASK COMPLETE**, verify you have:
-
-1. ✅ Fixed all CI failures
-2. ✅ Committed the changes using `mcp_github_file_ops_server__push_files`
-3. ✅ Verified the branch was pushed successfully
-4. ✅ **CREATED THE PR COMMENT using `gh pr comment` command from Step 6**
-
-If you have NOT created the PR comment, go back to Step 6 and execute the command.
-
-## Important Guidelines
-
-- Always use MCP tools for git operations to ensure proper commit signing
-- Focus exclusively on fixing the reported CI failures
-- Maintain code quality and follow the project's established patterns
-- If a fix requires significant refactoring, document why it's necessary
-- When multiple solutions exist, choose the simplest one that maintains code quality
-- **THE TASK IS NOT COMPLETE WITHOUT THE PR COMMENT**
-
-Begin by analyzing the failure details provided above.
+---
+description: Analyze and fix CI failures with signed commits using MCP tools
+allowed_tools: Edit,MultiEdit,Write,Read,Glob,Grep,LS,Bash(bun:*),Bash(npm:*),Bash(npx:*),Bash(gh:*),mcp__github_file_ops__commit_files,mcp__github_file_ops__delete_files
+---
+
+# Fix CI Failures with Signed Commits
+
+You are tasked with analyzing CI failure logs and fixing the issues using MCP tools for signed commits. Follow these steps:
+
+## Context Provided
+
+$ARGUMENTS
+
+## Important Context Information
+
+Look for these key pieces of information in the arguments:
+
+- **Failed CI Run URL**: Link to the failed CI run
+- **Failed Jobs**: List of jobs that failed
+- **PR Number**: The PR number to comment on
+- **Branch Name**: The fix branch you're working on
+- **Base Branch**: The original PR branch
+- **Error logs**: Detailed logs from failed jobs
+
+## CRITICAL: Use MCP Tools for Git Operations
+
+**IMPORTANT**: You MUST use MCP tools for all git operations to ensure commits are properly signed. DO NOT use `git` commands directly via Bash.
+
+- Use `mcp__github_file_ops__commit_files` to commit and push changes
+- Use `mcp__github_file_ops__delete_files` to delete files
+
+## Step 1: Analyze the Failure
+
+Parse the provided CI failure information to understand:
+
+- Which jobs failed and why
+- The specific error messages and stack traces
+- Whether failures are test-related, build-related, or linting issues
+
+## Step 2: Search and Understand the Codebase
+
+Use MCP search tools to locate the failing code:
+
+- Use `mcp_github_file_ops_server__search_files` or `mcp_github_file_ops_server__file_search` to find failing test names or functions
+- Use `mcp_github_file_ops_server__read_file` to read source files mentioned in error messages
+- Review related configuration files (package.json, tsconfig.json, etc.)
+
+## Step 3: Apply Targeted Fixes
+
+Make minimal, focused changes:
+
+- **For test failures**: Determine if the test or implementation needs fixing
+- **For type errors**: Fix type definitions or correct the code logic
+- **For linting issues**: Apply formatting using the project's tools
+- **For build errors**: Resolve dependency or configuration issues
+- **For missing imports**: Add the necessary imports or install packages
+
+Requirements:
+
+- Only fix the actual CI failures, avoid unrelated changes
+- Follow existing code patterns and conventions
+- Ensure changes are production-ready, not temporary hacks
+- Preserve existing functionality while fixing issues
+
+## Step 4: Verify Fixes Locally
+
+Run available verification commands using Bash:
+
+- Execute the failing tests locally to confirm they pass
+- Run the project's lint command (check package.json for scripts)
+- Run type checking if available
+- Execute any build commands to ensure compilation succeeds
+
+## Step 5: Commit and Push Changes Using MCP
+
+**CRITICAL**: You MUST use MCP tools for committing and pushing:
+
+1. Prepare all your file changes (using Edit/MultiEdit/Write tools as needed)
+2. **Use `mcp__github_file_ops__commit_files` to commit and push all changes**
+   - Pass the file paths you've edited in the `files` array
+   - Set `message` to describe the specific fixes (e.g., "Fix CI failures: remove syntax errors and format code")
+   - The MCP tool will automatically create the branch specified in "Branch Name:" from the context and push signed commits
+
+**IMPORTANT**: The MCP tool will create the branch from the context automatically. The branch name from "Branch Name:" in the context will be used.
+
+Example usage:
+
+```
+mcp__github_file_ops__commit_files with:
+- files: ["src/utils/retry.ts", "src/other/file.ts"]  // List of file paths you edited
+- message: "Fix CI failures: [describe specific fixes]"
+```
+
+Note: The branch will be created from the Base Branch specified in the context.
+
+## Step 6: Create PR Comment (REQUIRED - DO NOT SKIP)
+
+**CRITICAL: You MUST create a PR comment after pushing. This step is MANDATORY.**
+
+After successfully pushing the fixes, you MUST create a comment on the original PR to notify about the auto-fix. DO NOT end the task without completing this step.
+
+1. Extract the PR number from the context provided in arguments (look for "PR Number:" in the context)
+2. **MANDATORY**: Execute the gh CLI command below to create the comment
+3. Verify the comment was created successfully
+
+**YOU MUST RUN THIS COMMAND** (replace placeholders with actual values from context):
+
+```bash
+gh pr comment PR_NUMBER --body "## 🤖 CI Auto-Fix Available (Signed Commits)
+
+Claude has analyzed the CI failures and prepared fixes with signed commits.
+
+[**→ Create pull request to fix CI**](https://github.com/OWNER/REPO/compare/BASE_BRANCH...FIX_BRANCH?quick_pull=1)
+
+_This fix was generated automatically based on the [failed CI run](FAILED_CI_RUN_URL)._"
+```
+
+**IMPORTANT REPLACEMENTS YOU MUST MAKE:**
+
+- Replace `PR_NUMBER` with the actual PR number from "PR Number:" in context
+- Replace `OWNER/REPO` with the repository from "Repository:" in context
+- Replace `BASE_BRANCH` with the branch from "Base Branch:" in context
+- Replace `FIX_BRANCH` with the branch from "Branch Name:" in context
+- Replace `FAILED_CI_RUN_URL` with the URL from "Failed CI Run:" in context
+
+**DO NOT SKIP THIS STEP. The task is NOT complete until the PR comment is created.**
+
+## Step 7: Final Verification
+
+**BEFORE CONSIDERING THE TASK COMPLETE**, verify you have:
+
+1. ✅ Fixed all CI failures
+2. ✅ Committed the changes using `mcp_github_file_ops_server__push_files`
+3. ✅ Verified the branch was pushed successfully
+4. ✅ **CREATED THE PR COMMENT using `gh pr comment` command from Step 6**
+
+If you have NOT created the PR comment, go back to Step 6 and execute the command.
+
+## Important Guidelines
+
+- Always use MCP tools for git operations to ensure proper commit signing
+- Focus exclusively on fixing the reported CI failures
+- Maintain code quality and follow the project's established patterns
+- If a fix requires significant refactoring, document why it's necessary
+- When multiple solutions exist, choose the simplest one that maintains code quality
+- **THE TASK IS NOT COMPLETE WITHOUT THE PR COMMENT**
+
+Begin by analyzing the failure details provided above.

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

@@ -1,63 +1,63 @@
-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"
+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 +1,75 @@
-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"
+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"