「triage」の検索結果

GitHubの課題やプルリクエストを仕分けし、実行予定の作業をLinearにつなげて、公開状況と社内の担当・優先度・次の対応を整理するスキル。

• 未対応の課題やプルリクエストの仕分け
• Linearのタスクが必要か判断したいとき
• 進行中の作業と社内の担当・優先度の連携

メールのやり取り全体から返信や対応が必要な案件を分類し、優先順位を整理します。過去の送信メールを参考に返信案を作り、承認された送信や整理の結果を確認します。

• 今日の受信箱の優先順位を付ける
• 急ぎのメールへの返信案を作る
• 顧客や取引先への返信漏れを探す

Prioritize support requests, identify owners, route internally, and prepare safe customer drafts

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrates a GitHub PR review loop by delegating triage and implementation to dedicated sub-agents, then repeating until actionable review items are cleared. Use when the user says “address PR review”, “triage review comments”, or “iterate until review is clean”.

日本語の概要は準備中です。原文の説明を表示しています。

Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.

日本語の概要は準備中です。原文の説明を表示しています。

Triage Monte Carlo alerts interactively or build an automated workflow. Fetch, score, and troubleshoot alerts using MCP tools now, or design a reusable workflow that runs on a schedule.

日本語の概要は準備中です。原文の説明を表示しています。

Triage and resolve Fedora issues with dnf, systemd, and SELinux-aware guidance.

日本語の概要は準備中です。原文の説明を表示しています。

Triage and resolve Debian Linux issues with apt, systemd, and AppArmor-aware guidance.

日本語の概要は準備中です。原文の説明を表示しています。

Triage and resolve CentOS issues using RHEL-compatible tooling, SELinux-aware practices, and firewalld.

日本語の概要は準備中です。原文の説明を表示しています。

Copilot left 14 review comments on your PR — half are nits. Hours of fix → reply → resolve → re-request, and each round lands MORE comments. This skill runs loop engineering: auto-triggers Copilot Code Review via GraphQL (no @copilot mention), triages every open thread (Copilot, humans, advanced-security) with a fix / decline / escalate rubric, dispatches parallel fix sub-agents that obey the repo build/test/lint conventions, commits per iteration, replies+resolves citing the pushed SHA, then re-triggers until HEAD is reviewed with zero threads awaiting the agent's reply (remaining open threads are explicit hand-offs to the human — escalated declines, design tradeoffs). You merge a clean PR; the bot runs it. Trigger phrases: "address copilot comments", "run a copilot review loop", "fix this PR", "iterate on copilot feedback". Repo-agnostic, gh CLI + PowerShell. Full autopilot needs repo Triage/Write; external PR authors get single-iteration mode plus manual re-trigger (UI 🔄 or substantive-commit push).

日本語の概要は準備中です。原文の説明を表示しています。

Triage and resolve Arch Linux issues with pacman, systemd, and rolling-release best practices.

日本語の概要は準備中です。原文の説明を表示しています。

Build a structured SOC escalation matrix defining severity tiers, response SLAs, tiered escalation paths, and notification procedures for security incidents, using context-driven criteria that combine business risk, asset criticality, and data sensitivity. Use when designing or revising how a SOC triages and escalates incidents across analyst tiers.

日本語の概要は準備中です。原文の説明を表示しています。

Implement a phishing report button (Microsoft 365 built-in Report button or third-party like KnowBe4/Cofense) in email clients with a SOAR-driven automated triage workflow that classifies reported emails, extracts IOCs, takes remediation actions, and gives feedback to reporters. Use when deploying user-reported phishing intake or automating triage of the resulting reporting mailbox.

日本語の概要は準備中です。原文の説明を表示しています。

Builds today's call list. Runs lead-triage to rank the top-5 leads most worth calling, supplies talking points from email history, blocks time on the calendar, and drafts follow-up messages. Trigger on "call list," "who am I calling today," "top five to call today," or "block time for calls." An owner who wants leads scored or ranked with no calendar blocks routes to lead-triage directly. Accepts optional count and date arguments.

日本語の概要は準備中です。原文の説明を表示しています。

Rapidly triage an incoming NDA and classify it as GREEN (standard approval), YELLOW (counsel review), or RED (full legal review). Use when a new NDA arrives from sales or business development, when screening for embedded non-solicits, non-competes, or missing carveouts, or when deciding whether an NDA can be signed under standard delegation.

日本語の概要は準備中です。原文の説明を表示しています。

Triage and prioritize a support ticket or customer issue. Use when a new ticket comes in and needs categorization, assigning P1-P4 priority, deciding which team should handle it, or checking whether it's a duplicate or known issue before routing.

日本語の概要は準備中です。原文の説明を表示しています。

First-contact triage for a GitHub issue

日本語の概要は準備中です。原文の説明を表示しています。

Triage a Factory work item's issue — trace history, understand architecture, diagnose root cause, then advance the stage

日本語の概要は準備中です。原文の説明を表示しています。

Gatekeep and review GitHub issues and pull requests for Qwen Code maintainers. Use for GitHub Action issue triage, PR admission checks, product-direction review, KISS-focused PR review, and staged bilingual GitHub comments.

日本語の概要は準備中です。原文の説明を表示しています。

Triage OpenSEO production errors in Cloudflare Workers Observability — verified query recipes, counting gotchas, and a known-noise filter list applied automatically. Use when asked to review Cloudflare logs/observability, count OOMs or worker errors, compare error rates between periods, or investigate a prod error spike.

日本語の概要は準備中です。原文の説明を表示しています。

Author, validate, test, and deploy YARA-L 2.0 detection rules and evaluate end-to-end detection coverage gaps in Google SecOps. Use when writing new detection rules, tuning existing rules, validating syntax, testing logic against historical telemetry, or evaluating detection coverage against threat intelligence blogs, CVE disclosures, and Threat Detection Opportunities (TDOs) using synthetic UDM events and long-running coverage analysis. Don't use for alert triage (use secops-triage), deep forensic event reconstruction on infected hosts (use secops-investigate), or case management operations (use secops-cases).

日本語の概要は準備中です。原文の説明を表示しています。

Expert guidance for proactive threat hunting in Google SecOps. Use when proactively hunting for threats, retroactively analyzing indicators of compromise (IoCs), performing prevalence searches across enterprise events, hunting for MITRE ATT&CK techniques, or detecting behavioral and statistical outliers using UDM queries. Don't use for incoming alert triage (use secops-triage), active incident response and timeline deep-dives on a known breach (use secops-investigate), or detection rule authoring (use secops-detection-engineering).

日本語の概要は準備中です。原文の説明を表示しています。

Expert guidance for deep security incident and entity investigations in Google SecOps. Use when investigating cases, analyzing entities (hosts, IPs, domains, hashes, users), extracting and searching UDM events, performing asset and user timeline analysis, and detecting lateral movement across enterprise networks. Don't use for detection rule authoring or YARA-L tuning (use secops-detection-engineering), proactive hypothesis-driven hunting (use secops-hunt), initial alert triage (use secops-triage), or basic case status updates (use secops-cases).

日本語の概要は準備中です。原文の説明を表示しています。

Expert guidance for security alert triage in Google SecOps. Use when investigating and triaging security alerts, determining false positives vs. true positives, assessing entity risk, adjusting alert severity or priority, and closing or escalating alerts and cases. Don't use for deep multi-hop incident investigations across host timelines (use secops-investigate), proactive threat hunting or retroactive IoC sweeps (use secops-hunt), or authoring new detection rules (use secops-detection-engineering).

日本語の概要は準備中です。原文の説明を表示しています。