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

Increase oncall triage engagement threshold to 50Browse files

Updates the oncall triage automation to require 50+ engagements
(comments + reactions) before applying the oncall label, making the
criteria more conservative to focus on the most critical issues.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Cat Wu authored on Oct 29, 2025 parent 5d0e5cf · commit 5484a86d289f

2 changed files+3 -3compared with 5d0e5cf

M.claude/commands/oncall-triage.md

M.github/workflows/oncall-triage.yml

M.claude/commands/oncall-triage.md+2 -2

		@@ -9,9 +9,9 @@
9	9
10	10	Task overview:
11	11
12		-1. First, get all open bugs updated in the last 3 days with at least 5 engagements:
	12	+1. First, get all open bugs updated in the last 3 days with at least 50 engagements:
13	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) >= 5)) \| "\(.number)"'
	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	15	```
16	16
17	17	2. Save the list of issue numbers and create a TODO list with ALL of them. This ensures you process every single one.

M.github/workflows/oncall-triage.yml+1 -1

		@@ -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?