ci: add Claude Code issue triage bot (#31211)

Alternative to #31210

Author: bartlomieju

.github/workflows/issue_triage.yml

@@ -0,0 +1,63 @@
+name: AI Issue Triage
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  triage:
+    if: github.event.issue.author_association != 'MEMBER' && github.event.issue.author_association != 'OWNER'
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      id-token: write
+    steps:
+      - uses: anthropics/claude-code-action@v1
+        with:
+          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
+          prompt: |
+            REPO: ${{ github.repository }}
+            ISSUE NUMBER: ${{ github.event.issue.number }}
+            TITLE: ${{ github.event.issue.title }}
+            BODY: ${{ github.event.issue.body }}
+            AUTHOR: ${{ github.event.issue.user.login }}
+
+            This is a new issue from an external contributor. Please analyze it and:
+
+            1. **Categorize the issue type**: Determine if it's a:
+               - Bug report
+               - Feature request/suggestion
+               - Node.js compatibility problem
+               - Question
+               - Documentation issue
+               - Performance issue
+               - Other
+
+            2. **Assess completeness**: Check if the issue contains:
+               - Clear description of the problem/request
+               - Steps to reproduce (for bugs)
+               - Expected vs actual behavior (for bugs)
+               - Deno version and platform info (when relevant)
+               - Minimal reproducible example (for bugs)
+
+            3. **Check for duplicates**: Search existing issues to see if this has been reported before:
+               `gh search issues --repo denoland/deno [relevant keywords]`
+
+            4. **Suggest appropriate labels** based on:
+               - Type: bug, feat, suggestion, question, docs
+               - Platform: windows (if Windows-specific)
+               - Node.js compatibility bug
+               - Priority/Status: needs info, good first issue (for simple, well-defined bugs), etc.
+               - Other: performance/perf, benchmarks, build, breaking change, tls, design limitation, etc.
+
+            5. **Add labels** using: `gh issue edit ${{ github.event.issue.number }} --add-label "label1,label2,label3"`, make sure to add "ai:triage" label.
+
+            6. **If the issue needs more information**, also add a comment requesting specific details needed for triage and the "needs info" label.
+
+            7. **If you find a likely duplicate**, post a comment mentioning the original issue(s) and add the "duplicate" label.
+
+            Be thorough but efficient. Focus on accurate categorization to help maintainers prioritize their work. Make sure that your
+            comments includes this banner at the very end: "_This response is autogenerated and may contain mistakes._"
+
+          claude_args: |
+            --allowedTools "Bash(gh issue:*),Bash(gh search:*)"