“triage”的搜索结果

Triages a batch of customer support tickets (helpdesk export, shared mailbox, chat transcripts, web forms) into one row per ticket with category, urgency graded on the evidence in the ticket, suggested next action and owner, plus a DRAFT customer reply for every ticket that needs one, returned as one Markdown pack. Use when the user asks to "triage these tickets", "sort the support queue", "what needs an answer first", "categorise this backlog", "draft replies for these tickets" or "build today's queue review". Do not use for internal requests from colleagues, use request-intake-triage instead; for one long thread that needs handing over, use escalation-summary; for a personal mailbox, use inbox-triage. Drafts for human review; never approves, authorises or signs off.

中文简介正在准备中。当前显示原文说明。

Triage new issues in the Sentry `javascript` project by archiving non-actionable noise. Use when asked to "triage issues", "triage the javascript project", "archive non-actionable issues", "triage new frontend issues", or "clean up the sentry/javascript queue". Operates only on the sentry/javascript project, only archives (never resolves), and always archives with `untilEscalating`.

中文简介正在准备中。当前显示原文说明。

The runbook a triage agent follows on each run over the super-admin attention dock, through the attention MCP tool. Use when a scheduled attention-triage routine wakes, when asked to triage, clean up or shrink the attention dock or admin alerts, or when the dock's card is over budget.

中文简介正在准备中。当前显示原文说明。

为首次使用开发技能整理仓库共用配置，确认任务管理位置、分类标签及术语表和设计决策记录的存放方式，经用户审核后写入配置文档。

• 首次使用开发技能前的配置
• 整理任务管理位置和分类标签
• 确定术语表与设计决策记录的位置

Organize open pull requests before a release, classify what to merge or defer, and track decisions in a resumable document. Guide review, merging, follow-up fixes, and closing requests already covered by other changes.

中文简介正在准备中。当前显示英语简介。

• Sort a backlog of pull requests before a release
• Prioritize bug fixes for the next version
• Resume interrupted reviews from a progress document

Investigate a GitHub issue or reported problem, check whether it is a bug, and test a proof of concept. Explain the behavior changes and supporting evidence so the user can decide whether to proceed with the full fix.

中文简介正在准备中。当前显示英语简介。

• Checking whether a reported issue is a real bug
• Testing a proposed fix before full implementation
• Comparing performance before and after a change

Review Monte Carlo alerts, score their likelihood of indicating an incident and their potential impact, and investigate likely causes. Use the same stages to design and test a repeatable triage workflow, starting with recommendations before enabling actions.

中文简介正在准备中。当前显示英语简介。

• Reviewing recent Monte Carlo alerts
• Prioritizing alerts by incident likelihood and impact
• Designing and testing a recurring triage workflow

Coordinate GitHub pull request reviews by assigning comment triage and code changes to dedicated sub-agents. Repeat the process, track decisions and progress, and reply to and resolve threads as fixes are completed.

中文简介正在准备中。当前显示英语简介。

• Work through outstanding pull request review comments
• Separate required fixes from items outside the pull request scope
• Repeat review and implementation until actionable items are cleared

Prepare a daily sales call list ranked by lead priority, with talking points drawn from recent emails. Get proposed calendar slots, follow-up email drafts, and a printable call sheet with space to record outcomes.

中文简介正在准备中。当前显示英语简介。

• Choose the highest-priority leads to call today
• Prepare talking points from past emails
• Reserve time for sales calls

Assess incoming support requests, assign a category and P1–P4 urgency level, and recommend the team to handle them. Check available records for duplicates or known issues, then prepare an initial customer response and internal handoff notes.

中文简介正在准备中。当前显示英语简介。

• Classify and prioritize new support requests
• Recommend the right team for an issue
• Check for duplicate tickets and known problems

Review NemoClaw issues and pull requests, propose issue types, project priorities, statuses, and labels, then apply only approved changes. Supports individual items and batch triage, with explanations and a report of each update.

中文简介正在准备中。当前显示英语简介。

• Classify a newly opened issue
• Review priorities and statuses for issues and pull requests
• Triage unlabeled items in a batch

Process one recommendation selected by ID from a local issue or CI triage report. Apply, reject, or defer it, record the outcome, and obtain separate confirmation before each change made on GitHub.

中文简介正在准备中。当前显示英语简介。

• Apply one recommendation selected by its item ID
• Reject a recommendation and record the reason
• Defer a decision for the next queue review

Sort open GitHub issues by category, risk, inactivity, and possible duplication. Examine selected reports in detail, identify missing information, and prepare comments, labels, or closures for user approval before taking action.

中文简介正在准备中。当前显示英语简介。

• Sort accumulated bug reports and feature requests
• Check possible duplicates against open and closed issues
• Review inactive issues for follow-up or closure

Set up the repository settings that engineering skills read: where work is tracked, which triage labels to use, and where domain documents belong. Review existing files and confirm drafts before writing configuration documents.

中文简介正在准备中。当前显示英语简介。

• Prepare a repository before using engineering skills
• Configure GitHub, GitLab, or local Markdown issue tracking
• Match triage labels to an existing workflow

[omh] Failing run handed to Jev for a next move: Jev failure triage: retry, fix a dependency, ask for access, or change approach on a failing run. Use when the user says: jev-failure-triage, jev failure triage, ask jev if this failure is transient.

中文简介正在准备中。当前显示原文说明。

[omh] Build or CI failure to triage: classify build, typecheck, lint, test, CI, and DCO failures into minimal safe fix handoffs. Use when the user says: build-failure-triage, build failure triage, build failure, build-failure, build fix, build failed, build failing, compile error.

中文简介正在准备中。当前显示原文说明。

Triage an incoming insurance claim: check the coverage trigger against policy wording, band severity and complexity, screen for fraud indicators, set a first-pass reserve range, and route with an SLA. Use when asked to triage a claim, review a first notice of loss (FNOL), assess a new claim, decide fast-track vs adjuster routing, or screen a claim for SIU referral. Produces a structured triage note with coverage view, severity band, indicator screen, reserve range, and a routing recommendation.

中文简介正在准备中。当前显示原文说明。

Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

中文简介正在准备中。当前显示原文说明。

Triage the improvements backlog at .turbo/improvements.md: merge duplicate entries, state the user story or simplification behind each one, and decide with the user which to keep and which to drop. Use when the user asks to "triage improvements", "triage the backlog", "clean up the backlog", "clean up improvements", "groom the backlog", "prune the improvements backlog", or "go through the backlog with me".

中文简介正在准备中。当前显示原文说明。

Bug bounty report triage, validation, and severity escalation. Use when the user provides a bug bounty report to validate, wants to check if a finding is submittable, needs to escalate severity for maximum payout, or says 'triage this', 'validate this report', 'escalate this', 'is this submittable', 'check this bounty report', 'max bounty', or 'will this get accepted'.

中文简介正在准备中。当前显示原文说明。

Triage mode operational spec for the team lead. Returns lead identity, facilitator identity, mode-specific rules, suggest-members guidance, and phase arc for triage teams that diagnose an issue without changing it.

中文简介正在准备中。当前显示原文说明。

Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.

中文简介正在准备中。当前显示原文说明。

Claudeデスクトップアプリ（Codeタブ）の全セッションを見回り、名前の先頭の絵文字で「⏳作業中／👀確認中／📤送信待ち／🔴要確認／✅完了」を表し、「絵文字【フォルダ】内容」の形に付け直すスキル。自分の判断が要るものだけを一覧にまとめ、完了したものは夜にまとめてアーカイブする。「セッションを整理して」「どのセッションが自分待ち？」「セッションに絵文字を付けて」「session triage」等で使う。定期実行（15分おき）に載せると、サイドバーを見るだけで状況が分かる状態を保てる。

中文简介正在准备中。当前显示原文说明。

Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

中文简介正在准备中。当前显示原文说明。