actions/claude-code-action
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
claude-code-action/.claude/commands/label-issue.md
Octavian Guzu dd8541688d
Use wrapper script for label operations in issue triage (#968) 
* Use wrapper script for label operations in issue triage

Updates /label-issue command and examples to use a dedicated
edit-issue-labels.sh script for label operations instead of raw
gh issue edit. The script validates labels against the repo's existing
labels before applying them. Also tightens gh search permission to
gh search issues.

* Show multiple --add-label flags in label-issue example
2026-02-23 17:16:07 +00:00

2.6 KiB
Raw Blame History

allowed-tools description
Bash(gh label list:*),Bash(gh issue view:*),Bash(./scripts/edit-issue-labels.sh:*),Bash(gh search issues:*) 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(./scripts/edit-issue-labels.sh:*) - to apply labels to the issue
      • Bash(gh search issues:*) - 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 ./scripts/edit-issue-labels.sh --issue NUMBER --add-label LABEL1 --add-label LABEL2 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 ./scripts/edit-issue-labels.sh
  • It's okay to not add any labels if none are clearly applicable