بنقرة واحدة
source-command-oncall-triage
Triage GitHub issues and label critical ones for oncall
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Triage GitHub issues and label critical ones for oncall
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | source-command-oncall-triage |
| description | Triage GitHub issues and label critical ones for oncall |
Use this skill when the user asks to run the migrated source command oncall-triage.
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.
Repository: OrcaSlicer/OrcaSlicer
Task overview:
First, get all open bugs updated in the last 3 days with at least 50 engagements:
gh issue list --repo OrcaSlicer/OrcaSlicer --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)"'
Save the list of issue numbers and create a TODO list with ALL of them. This ensures you process every single one.
For each issue in your TODO list:
gh issue view <number> --repo OrcaSlicer/OrcaSlicer --json title,body,labels,comments to get full detailsFor issues that are truly blocking and don't already have the "oncall" label:
gh issue edit <number> --repo OrcaSlicer/OrcaSlicer --add-label "oncall"After processing all issues, provide a summary:
Important:
gh issue view commands instead of bash for loops to avoid approval prompts