Files
claude-code-action/.claude/commands/label-issue.md
Ashwin Bhat 69dec299f8 feat: add allowed_non_write_users input to bypass permission checks (#550)
* chore: bump Claude Code version to 1.0.108

* triage fix

---------

Co-authored-by: GitHub Actions <actions@github.com>
2025-09-07 14:20:02 -07:00

2.4 KiB

allowed-tools, description
allowed-tools description
Bash(gh label list:*),Bash(gh issue view:*),Bash(gh issue edit:*),Bash(gh search:*) Apply labels to GitHub issues

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 gh commands to get context about the issue:

    • Use gh issue view ${{ github.event.issue.number }} to retrieve the current issue's details
    • Use gh search issues to find similar issues that might provide context for proper categorization
    • You have access to these Bash commands:
      • Bash(gh label list:*) - to get available labels
      • Bash(gh issue view:*) - to view issue details
      • Bash(gh issue edit:*) - to apply labels to the issue
      • Bash(gh search:*) - to search for similar issues
  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
    • IMPORTANT: Add a priority label (P1, P2, or P3) based on the label descriptions from gh label list
    • Consider platform labels (android, ios) if applicable
    • If you find similar issues using gh search, 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 gh issue edit 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 gh issue edit
  • It's okay to not add any labels if none are clearly applicable