surshar / claude-code
Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.
Built by Anthropic · github.com/anthropics
Add oncall triage slash command for issue management
| @@ -1,0 +1,40 @@ | ||
| 1 | +--- | |
| 2 | +allowed-tools: Bash(gh issue list:*), Bash(gh issue view:*), Bash(gh issue edit:*), TodoWrite | |
| 3 | +description: Triage GitHub issues and label critical ones for oncall | |
| 4 | +--- | |
| 5 | + | |
| 6 | +You're an oncall triage assistant for GitHub issues. Your task is to identify critical issues that require immediate oncall attention and apply the "oncall" label. | |
| 7 | + | |
| 8 | +Repository: anthropics/claude-code | |
| 9 | + | |
| 10 | +Task overview: | |
| 11 | + | |
| 12 | +1. First, get all open bugs updated in the last 3 days with at least 50 engagements: | |
| 13 | + ```bash | |
| 14 | + gh issue list --repo anthropics/claude-code --state open --label bug --limit 1000 --json number,title,updatedAt,comments,reactions | jq -r '.[] | select((.updatedAt >= (now - 259200 | strftime("%Y-%m-%dT%H:%M:%SZ"))) and ((.comments | length) + ([.reactions[].content] | length) >= 50)) | "\(.number)"' | |
| 15 | + ``` | |
| 16 | + | |
| 17 | +2. Save the list of issue numbers and create a TODO list with ALL of them. This ensures you process every single one. | |
| 18 | + | |
| 19 | +3. For each issue in your TODO list: | |
| 20 | + - Use `gh issue view <number> --repo anthropics/claude-code --json title,body,labels,comments` to get full details | |
| 21 | + - Read and understand the full issue content and comments to determine actual user impact | |
| 22 | + - Evaluate: Is this truly blocking users from using Claude Code? | |
| 23 | + - Consider: "crash", "stuck", "frozen", "hang", "unresponsive", "cannot use", "blocked", "broken" | |
| 24 | + - Does it prevent core functionality? Can users work around it? | |
| 25 | + - Be conservative - only flag issues that truly prevent users from getting work done | |
| 26 | + | |
| 27 | +4. For issues that are truly blocking and don't already have the "oncall" label: | |
| 28 | + - Use `gh issue edit <number> --repo anthropics/claude-code --add-label "oncall"` | |
| 29 | + - Mark the issue as complete in your TODO list | |
| 30 | + | |
| 31 | +5. After processing all issues, provide a summary: | |
| 32 | + - List each issue number that received the "oncall" label | |
| 33 | + - Include the issue title and brief reason why it qualified | |
| 34 | + - If no issues qualified, state that clearly | |
| 35 | + | |
| 36 | +Important: | |
| 37 | +- Process ALL issues in your TODO list systematically | |
| 38 | +- Don't post any comments to issues | |
| 39 | +- Only add the "oncall" label, never remove it | |
| 40 | +- Use individual `gh issue view` commands instead of bash for loops to avoid approval prompts |
| @@ -54,7 +54,7 @@ | ||
| 54 | 54 | - Use mcp__github__get_issue_comments to read all comments |
| 55 | 55 | - Evaluate whether this issue needs the oncall label: |
| 56 | 56 | a) Is it a bug? (has "bug" label or describes bug behavior) |
| 57 | - b) Does it have at least 5 engagements? (count comments + reactions) | |
| 57 | + b) Does it have at least 50 engagements? (count comments + reactions) | |
| 58 | 58 | c) Is it truly blocking? Read and understand the full content to determine: |
| 59 | 59 | - Does this prevent core functionality from working? |
| 60 | 60 | - Can users work around it? |