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 32156b120b
Add subprocess isolation setup and git credential helper (#1132) 
- Add optional bubblewrap setup step for Linux subprocess isolation
  when allowed_non_write_users is configured
- Use git credential helper instead of embedding token in remote URL
- edit-issue-labels.sh: read issue number from workflow event payload
  instead of CLI arg
- Add CLAUDE_CODE_SCRIPT_CAPS env for per-script call limit config
- docs/security.md: note recommended github_token configuration

🏠 Remote-Dev: homespace
2026-03-31 12:36:51 +01:00

2.7 KiB
Raw Blame History

allowed-tools description
Bash(./scripts/gh.sh:*),Bash(./scripts/edit-issue-labels.sh:*) 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: ./scripts/gh.sh label list. Run exactly this command with nothing else.

  2. Next, use gh wrapper commands to get context about the issue:

    • Use ./scripts/gh.sh issue view ${{ github.event.issue.number }} to retrieve the current issue's details
    • Use ./scripts/gh.sh search issues to find similar issues that might provide context for proper categorization
    • ./scripts/gh.sh is a wrapper for gh CLI. Example commands:
      • ./scripts/gh.sh label list — fetch all available labels
      • ./scripts/gh.sh issue view 123 — view issue details
      • ./scripts/gh.sh issue view 123 --comments — view with comments
      • ./scripts/gh.sh search issues "query" --limit 10 — search for issues
    • ./scripts/edit-issue-labels.sh — apply labels to the issue

  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 ./scripts/gh.sh label list
    • Consider platform labels (android, ios) if applicable
    • If you find similar issues using ./scripts/gh.sh 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 --add-label LABEL1 --add-label LABEL2 to apply your selected labels (issue number is read from the workflow event)
    • 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