'triage' 검색 결과

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

[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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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 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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Triages an incoming non-disclosure agreement against the organisation's written standard NDA positions and returns a DRAFT triage pack: a clause-by-clause deviations table with a severity band, a suggested response per clause quoted from the positions document, open questions and a governing-law flag, all for counsel to decide. Never gives legal advice or an acceptability call. Use when the user asks to "triage this NDA against our standard positions", "screen this confidentiality agreement before it goes to legal", "red-flag this mutual NDA", "first-pass the counterparty's NDA" or "is this NDA standard or does it need counsel". Do not use for a full review of an MSA, SOW, licence or any whole contract, use contract-review-pack instead; for one clause lined up across several documents, use clause-comparison-table. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Sorts a personal inbox backlog into five buckets (needs-reply-today, needs-reply-this-week, waiting-on-others, FYI, noise), writes DRAFT reply text for the messages that need an answer (up to 10 per run), and returns a dated triage report as one Markdown document. Lists moves or archives only as proposals for the user to perform, and only where a rule the user supplied says so; the agent changes nothing in the mailbox. Use when the user asks to "triage my inbox", "sort my mail", "clean up my inbox", "catch up after leave" or "what needs a reply today or this week". Do not use for a shared support queue or helpdesk export, use ticket-triage-pack instead; for what the user promised or is owed, use commitment-catcher; for one named thread, answer directly. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Orchestrate HITL triage of review findings using parallel agents. Use when the user says 'triage these findings' or 'run findings triage' or has a batch of review findings to process.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.