Add manual issue triage workflow

- Add optional issue_number parameter to Claude Issue Triage Action
- Create manual workflow that accepts comma-separated issue numbers
- Maintains backward compatibility with existing issue event workflow

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

.github/actions/claude-code-action/action.yml

@@ -0,0 +1,136 @@
+name: "Claude Code Action"
+description: "Run Claude Code in GitHub Actions workflows"
+
+inputs:
+  github_token:
+    description: "GitHub token with repo and issues permissions"
+    required: true
+  anthropic_api_key:
+    description: "Anthropic API key"
+    required: true
+  prompt:
+    description: "The prompt to send to Claude Code"
+    required: false
+    default: ""
+  prompt_file:
+    description: "Path to a file containing the prompt to send to Claude Code"
+    required: false
+    default: ""
+  allowed_tools:
+    description: "Comma-separated list of allowed tools for Claude Code to use"
+    required: false
+    default: ""
+  output_file:
+    description: "File to save Claude Code output to (optional)"
+    required: false
+    default: ""
+  timeout_minutes:
+    description: "Timeout in minutes for Claude Code execution"
+    required: false
+    default: "10"
+  install_github_mcp:
+    description: "Whether to install the GitHub MCP server"
+    required: false
+    default: "false"
+
+runs:
+  using: "composite"
+  steps:
+    - name: Install Claude Code
+      shell: bash
+      run: npm install -g @anthropic-ai/claude-code
+
+    - name: Install GitHub MCP Server
+      if: inputs.install_github_mcp == 'true'
+      shell: bash
+      run: |
+        claude mcp add-json github '{
+          "command": "docker",
+          "args": [
+            "run",
+            "-i",
+            "--rm",
+            "-e",
+            "GITHUB_PERSONAL_ACCESS_TOKEN",
+            "ghcr.io/github/github-mcp-server:sha-ff3036d"
+          ],
+          "env": {
+            "GITHUB_PERSONAL_ACCESS_TOKEN": "${{ inputs.GITHUB_TOKEN }}"
+          }
+        }'
+
+    - name: Prepare Prompt File
+      shell: bash
+      id: prepare_prompt
+      run: |
+        # Check if either prompt or prompt_file is provided
+        if [ -z "${{ inputs.prompt }}" ] && [ -z "${{ inputs.prompt_file }}" ]; then
+          echo "::error::Neither 'prompt' nor 'prompt_file' was provided. At least one is required."
+          exit 1
+        fi
+
+        # Determine which prompt source to use
+        if [ ! -z "${{ inputs.prompt_file }}" ]; then
+          # Check if the prompt file exists
+          if [ ! -f "${{ inputs.prompt_file }}" ]; then
+            echo "::error::Prompt file '${{ inputs.prompt_file }}' does not exist."
+            exit 1
+          fi
+
+          # Use the provided prompt file
+          PROMPT_PATH="${{ inputs.prompt_file }}"
+        else
+          mkdir -p /tmp/claude-action
+          PROMPT_PATH="/tmp/claude-action/prompt.txt"
+          echo "${{ inputs.prompt }}" > "$PROMPT_PATH"
+        fi
+
+        # Verify the prompt file is not empty
+        if [ ! -s "$PROMPT_PATH" ]; then
+          echo "::error::Prompt is empty. Please provide a non-empty prompt."
+          exit 1
+        fi
+
+        # Save the prompt path for the next step
+        echo "PROMPT_PATH=$PROMPT_PATH" >> $GITHUB_ENV
+
+    - name: Run Claude Code
+      shell: bash
+      id: run_claude
+      run: |
+        ALLOWED_TOOLS_ARG=""
+        if [ ! -z "${{ inputs.allowed_tools }}" ]; then
+          ALLOWED_TOOLS_ARG="--allowedTools ${{ inputs.allowed_tools }}"
+        fi
+
+        # Set a timeout to ensure the command doesn't run indefinitely
+        timeout_seconds=$((${{ inputs.timeout_minutes }} * 60))
+
+        if [ -z "${{ inputs.output_file }}" ]; then
+          # Run Claude Code and output to console
+          timeout $timeout_seconds claude \
+            -p \
+            --verbose \
+            --output-format stream-json \
+            "$(cat ${{ env.PROMPT_PATH }})" \
+            ${{ inputs.allowed_tools != '' && format('--allowedTools "{0}"', inputs.allowed_tools) || '' }}
+        else
+          # Run Claude Code and tee output to console and file
+          timeout $timeout_seconds claude \
+            -p \
+            --verbose \
+            --output-format stream-json \
+            "$(cat ${{ env.PROMPT_PATH }})" \
+            ${{ inputs.allowed_tools != '' && format('--allowedTools "{0}"', inputs.allowed_tools) || '' }} | tee output.txt
+
+          # Process output.txt into JSON in a separate step
+          jq -s '.' output.txt > output.json
+
+          # Extract the result from the last item in the array (system message)
+          jq -r '.[-1].result' output.json > "${{ inputs.output_file }}"
+
+          echo "Complete output saved to output.json, final response saved to ${{ inputs.output_file }}"
+        fi
+      env:
+        ANTHROPIC_API_KEY: ${{ inputs.anthropic_api_key }}
+        GITHUB_TOKEN: ${{ inputs.github_token }}

.github/actions/claude-issue-triage-action/action.yml

@@ -0,0 +1,98 @@
+name: "Claude Issue Triage Action"
+description: "Automatically triage GitHub issues using Claude Code"
+
+inputs:
+  timeout_minutes:
+    description: "Timeout in minutes for execution"
+    required: false
+    default: "5"
+  anthropic_api_key:
+    description: "Anthropic API key"
+    required: true
+  github_token:
+    description: "GitHub token with repo and issues permissions"
+    required: true
+  issue_number:
+    description: "Issue number to triage (optional - defaults to event issue number)"
+    required: false
+
+runs:
+  using: "composite"
+  steps:
+    - name: Checkout repository code
+      uses: actions/checkout@v4
+      with:
+        fetch-depth: 0
+
+    - name: Create prompt file
+      shell: bash
+      run: |
+        mkdir -p /tmp/claude-prompts
+        cat > /tmp/claude-prompts/claude-issue-triage-prompt.txt << 'EOF'
+        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: ${{ inputs.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. Identify existing duplicate issues:
+           - Use mcp__github__search_issues to find similar issues
+           - List out all open or recently closed issues that seem likely to be reports of the same problem
+           - Place the best candidate issue to merge into at the top of the list.
+             The best candidate issue is the one that is:
+               1. Has the same underlying cause as the current issue
+               2. Is the most complete and well-documented
+               3. Is the oldest open issue that is still relevant
+
+        5. Select appropriate labels from the available labels list provided above:
+           - Choose labels that accurately reflect the issue's nature
+           - Be specific but comprehensive
+           - Consider platform labels (macos, linux, windows) if applicable
+           - Do not apply the "duplicate" label unless you are certain the issue is a duplicate of another open issue
+
+        6. 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
+        EOF
+
+    - name: Run Claude Code
+      uses: ./.github/actions/claude-code-action
+      with:
+        prompt_file: /tmp/claude-prompts/claude-issue-triage-prompt.txt
+        allowed_tools: "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"
+        install_github_mcp: "true"
+        timeout_minutes: ${{ inputs.timeout_minutes }}
+        anthropic_api_key: ${{ inputs.anthropic_api_key }}
+        github_token: ${{ inputs.github_token }}

.github/workflows/claude-issue-triage-manual.yml

@@ -0,0 +1,46 @@
+name: Claude Issue Triage Manual
+description: "Manually triage GitHub issues using Claude Code"
+
+on:
+  workflow_dispatch:
+    inputs:
+      issue_numbers:
+        description: 'Comma-separated list of issue numbers to triage (e.g., 123,456,789)'
+        required: true
+        type: string
+
+jobs:
+  parse-issues:
+    runs-on: ubuntu-latest
+    outputs:
+      matrix: ${{ steps.set-matrix.outputs.matrix }}
+    steps:
+      - name: Parse issue numbers
+        id: set-matrix
+        run: |
+          # Remove spaces and convert to JSON array
+          CLEANED=$(echo "${{ github.event.inputs.issue_numbers }}" | tr -d ' ')
+          IFS=',' read -ra ISSUES <<< "$CLEANED"
+          MATRIX_JSON=$(printf '%s\n' "${ISSUES[@]}" | jq -R . | jq -s -c '{issue: .}')
+          echo "matrix=$MATRIX_JSON" >> $GITHUB_OUTPUT
+
+  triage-issue:
+    needs: parse-issues
+    runs-on: ubuntu-latest
+    timeout-minutes: 10
+    permissions:
+      contents: read
+      issues: write
+    strategy:
+      matrix: ${{ fromJson(needs.parse-issues.outputs.matrix) }}
+      max-parallel: 5
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683  # v4
+
+      - name: Run Claude Issue Triage
+        uses: ./.github/actions/claude-issue-triage-action
+        with:
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+          github_token: ${{ secrets.GITHUB_TOKEN }}
+          issue_number: ${{ matrix.issue }}

.github/workflows/claude-issue-triage.yml

@@ -1,5 +1,6 @@
 name: Claude Issue Triage
-description: Automatically triage GitHub issues using Claude Code
+description: "Automatically triage GitHub issues using Claude Code"
+
 on:
   issues:
     types: [opened]
@@ -11,96 +12,12 @@ jobs:
     permissions:
       contents: read
       issues: write
-
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v4
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683  # v4
 
-      - name: Create triage prompt
-        run: |
-          mkdir -p /tmp/claude-prompts
-          cat > /tmp/claude-prompts/triage-prompt.txt << 'EOF'
-          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
-          EOF
-
-      - name: Setup GitHub MCP Server
-        run: |
-          mkdir -p /tmp/mcp-config
-          cat > /tmp/mcp-config/mcp-servers.json << 'EOF'
-          {
-            "mcpServers": {
-              "github": {
-                "command": "docker",
-                "args": [
-                  "run",
-                  "-i",
-                  "--rm",
-                  "-e",
-                  "GITHUB_PERSONAL_ACCESS_TOKEN",
-                  "ghcr.io/github/github-mcp-server:sha-7aced2b"
-                ],
-                "env": {
-                  "GITHUB_PERSONAL_ACCESS_TOKEN": "${{ secrets.GITHUB_TOKEN }}"
-                }
-              }
-            }
-          }
-          EOF
-
-      - name: Run Claude Code for Issue Triage
-        uses: anthropics/claude-code-base-action@beta
+      - name: Run Claude Issue Triage
+        uses: ./.github/actions/claude-issue-triage-action
         with:
-          prompt_file: /tmp/claude-prompts/triage-prompt.txt
-          allowed_tools: "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"
-          timeout_minutes: "5"
           anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-          mcp_config: /tmp/mcp-config/mcp-servers.json
-          claude_env: |
-            GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          github_token: ${{ secrets.GITHUB_TOKEN }}

CHANGELOG.md

@@ -1,112 +1,5 @@
 # Changelog
 
-## 1.0.38
-
-- Released [hooks](https://docs.anthropic.com/en/docs/claude-code/hooks). Special thanks to community input in [Github Issues](https://github.com/anthropics/claude-code/issues/712)
-
-## 1.0.37
-
-- Remove ability to set `Proxy-Authorization` header via ANTHROPIC_AUTH_TOKEN or apiKeyHelper
-
-## 1.0.36
-
-- Web search now takes today's date into context
-- Fixed a bug where stdio MCP servers were not terminating properly on exit
-
-## 1.0.35
-
-- Added support for MCP OAuth Authorization Server discovery
-
-## 1.0.34
-
-- Fixed a memory leak causing a MaxListenersExceededWarning message to appear
-
-## 1.0.33
-
-- Improved logging functionality with session ID support
-- Added undo functionality (Ctrl+Z and vim 'u' command)
-- Improvements to plan mode
-
-## 1.0.32
-
-- Updated loopback config for litellm
-- Added forceLoginMethod setting to bypass login selection screen
-
-## 1.0.31
-
-- Fixed a bug where ~/.claude.json would get reset when file contained invalid JSON
-
-## 1.0.30
-
-- Custom slash commands: Run bash output, @-mention files, enable thinking with thinking keywords
-- Improved file path autocomplete with filename matching
-- Added timestamps in Ctrl-r mode and fixed Ctrl-c handling
-- Enhanced jq regex support for complex filters with pipes and select
-
-## 1.0.29
-
-- Improved CJK character support in cursor navigation and rendering
-
-## 1.0.28
-
-- Slash commands: Fix selector display during history navigation
-- Resizes images before upload to prevent API size limit errors
-- Added XDG_CONFIG_HOME support to configuration directory
-- Performance optimizations for memory usage
-- New attributes (terminal.type, language) in OpenTelemetry logging
-
-## 1.0.27
-
-- Streamable HTTP MCP servers are now supported
-- Remote MCP servers (SSE and HTTP) now support OAuth
-- MCP resources can now be @-mentioned
-- /resume slash command to switch conversations within Claude Code
-
-## 1.0.25
-
-- Slash commands: moved "project" and "user" prefixes to descriptions
-- Slash commands: improved reliability for command discovery
-- Improved support for Ghostty
-- Improved web search reliability
-
-## 1.0.24
-
-- Improved /mcp output
-- Fixed a bug where settings arrays got overwritten instead of merged
-
-## 1.0.23
-
-- Released TypeScript SDK: import @anthropic-ai/claude-code to get started
-- Released Python SDK: pip install claude-code-sdk to get started
-
-## 1.0.22
-
-- SDK: Renamed `total_cost` to `total_cost_usd`
-
-## 1.0.21
-
-- Improved editing of files with tab-based indentation
-- Fix for tool_use without matching tool_result errors
-- Fixed a bug where stdio MCP server processes would linger after quitting Claude Code
-
-## 1.0.18
-
-- Added --add-dir CLI argument for specifying additional working directories
-- Added streaming input support without require -p flag
-- Improved startup performance and session storage performance
-- Added CLAUDE_BASH_MAINTAIN_PROJECT_WORKING_DIR environment variable to freeze working directory for bash commands
-- Added detailed MCP server tools display (/mcp)
-- MCP authentication and permission improvements
-- Added auto-reconnection for MCP SSE connections on disconnect
-- Fixed issue where pasted content was lost when dialogs appeared
-
-## 1.0.17
-
-- We now emit messages from sub-tasks in -p mode (look for the parent_tool_use_id property)
-- Fixed crashes when the VS Code diff tool is invoked multiple times quickly
-- MCP server list UI improvements
-- Update Claude Code process title to display "claude" instead of "node"
-
 ## 1.0.11
 
 - Claude Code can now also be used with a Claude Pro subscription

README.md

@@ -22,7 +22,7 @@ npm install -g @anthropic-ai/claude-code
 
 ## Reporting Bugs
 
-We welcome your feedback. Use the `/bug` command to report issues directly within Claude Code, or file a [GitHub issue](https://github.com/anthropics/claude-code/issues).
+We welcome feedback during this beta period. Use the `/bug` command to report issues directly within Claude Code, or file a [GitHub issue](https://github.com/anthropics/claude-code/issues).
 
 ## Data collection, usage, and retention