feat(ci): Add Claude issue triage and similar issues workflows#977
feat(ci): Add Claude issue triage and similar issues workflows#977
Conversation
Add automated issue labeling workflow that triggers when new issues are opened. Claude analyzes the issue content and applies appropriate labels without posting comments.
Configure claude.yml and claude-code-review.yml to use the Opus model for higher quality responses in issue handling and PR reviews.
Add workflow that searches for related issues when a new issue is opened and posts a comment with up to 3 similar issues if found.
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the WalkthroughFour GitHub Actions workflows are modified and introduced. Existing claude-code-review.yml and claude.yml workflows now include explicit Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes
Possibly related PRs
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #977 +/- ##
=======================================
Coverage 90.38% 90.38%
=======================================
Files 110 110
Lines 7890 7890
Branches 1528 1528
=======================================
Hits 7131 7131
Misses 759 759 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Deploying repomix with
|
| Latest commit: |
c23e3e3
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://48c074be.repomix.pages.dev |
| Branch Preview URL: | https://chore-claude.repomix.pages.dev |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (4)
.github/workflows/claude-code-review.yml(1 hunks).github/workflows/claude-issue-similar.yml(1 hunks).github/workflows/claude-issue-triage.yml(1 hunks).github/workflows/claude.yml(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (12)
- GitHub Check: Build and run (windows-latest, 24.x)
- GitHub Check: Build and run (windows-latest, 25.x)
- GitHub Check: Build and run (macos-latest, 24.x)
- GitHub Check: Build and run (ubuntu-latest, 20.x)
- GitHub Check: Build and run (windows-latest, 20.x)
- GitHub Check: Build and run (ubuntu-latest, 22.x)
- GitHub Check: Test (windows-latest, 20.x)
- GitHub Check: Test (windows-latest, 22.x)
- GitHub Check: Build and run (windows-latest, 22.x)
- GitHub Check: Test (windows-latest, 24.x)
- GitHub Check: Build and run with Bun (windows-latest, latest)
- GitHub Check: Cloudflare Pages
🔇 Additional comments (6)
.github/workflows/claude.yml (1)
48-48: LGTM. Straightforward addition of the opus model specification aligns with the PR goal..github/workflows/claude-issue-triage.yml (2)
25-25: Note the use ofallowed_non_write_users: "*".Setting
allowed_non_write_users: "*"allows the Claude action to execute for any user, regardless of repository write permissions. For public repositories with issue automation, this is likely intentional to ensure all users' issues get triaged. However, verify this aligns with your security and operational posture, especially if sensitive actions expand in scope.
27-75: Prompt structure and instructions are clear and well-designed.The prompt provides explicit instructions to avoid posting comments, fetch available labels, analyze issue context, and apply only repository labels. The guidance on label categories (bug, enhancement, question, documentation, etc.) is helpful, and the conditional logic (only label if applicable) reduces noise.
.github/workflows/claude-issue-similar.yml (2)
25-25: Note the use ofallowed_non_write_users: "*".Same consideration as
claude-issue-triage.yml: this setting allows any user to trigger the Claude automation. For public issue tracking, this is likely intentional, but verify it aligns with your operational and security policies.
27-75: Prompt logic and structure are well-designed.The multi-step approach (fetch issue details, search for similar, analyze, filter to top 3, post or skip) is sound. The conditional "don't post if no matches" prevents noise, and the output format is user-friendly with explanations of relevance.
.github/workflows/claude-code-review.yml (1)
64-66: Theclaude_argssyntax is valid, but the allowed-tools list includes several unused tools that could be trimmed.Line 66 uses valid syntax:
--model opusis an accepted shorthand (per Claude Code documentation), and the--allowed-toolsparameter syntax is correct. However, comparing the allowlist to the actual prompt usage (lines 39–62):Tools actually used in prompt:
gh pr view(line 55: reads existing comments)mcp__github_inline_comment__create_inline_comment(line 59: creates inline comments)gh pr comment(line 61: posts PR comment)Tools in allowlist but never invoked:
Bash(gh issue view:*)Bash(gh search:*)Bash(gh issue list:*)Bash(gh pr diff:*)Bash(gh pr list:*)Recommendation: Consider removing unused tools to follow the principle of least privilege. If these are intentionally retained for future extensibility or model experimentation, document that intent in a comment.
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Fork PRs cannot access secrets, and bot PRs fail OIDC workflow validation. Adding conditions to skip these cases prevents unnecessary workflow failures.
1 participant
Add automated issue management workflows using Claude Code Action:
Changes
claude-issue-triage.yml: Automatically labels new issues based on content analysis
claude-issue-similar.yml: Finds and suggests related issues
claude.yml & claude-code-review.yml: Use Opus model for higher quality responses
Checklist
npm run test(N/A - workflow files only)npm run lint(N/A - workflow files only)