'triage' 검색 결과

Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.

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

Classify GitHub issues into the factory's live label queue and write an auditable snapshot. Use for backlog triage or a scheduled triage run.

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

Daily triage accuracy calibration — use during scheduled calibration runs to verify triage classification accuracy against few-shot examples and adjust confidence thresholds

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

Design ticket triage system -- routing rules, priority tags, queue structure, and first-response automation. Use when asked to "design our ticket routing", "how should we tag tickets", "set up our helpdesk", or "reduce time to first response".

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

Performs initial binary triage by surveying memory layout, strings, imports/exports, and functions to quickly understand what a binary does and identify suspicious behavior. Use when first examining a binary, when user asks to triage/survey/analyze a program, or wants an overview before deeper reverse engineering.

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

Triage a GitHub issue filed against skillsaw — classify it (bug, feature, docs, question, other), verify its claims against the codebase, enrich it with missing details, and post one structured triage comment. Use when triaging and labeling incoming issues, not to fix them.

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

Triage SDR replies and turn inbound responses into safe next actions, CRM handoff notes, suppression updates, objection responses, referrals, and meeting prep triggers. Use when "SDR reply", "triage replies", "outbound replies", "interested reply", "objection reply", "not interested", "unsubscribe", "wrong person", "bounce", "sales follow-up", "booked meeting", or any request to classify and respond to sales development replies.

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

Use when the user supplies or imports existing security findings, vulnerability reports, or security/vulnerability Jira/Linear tickets from scanners, advisories, GitHub, Atlassian Rovo, Linear, or similar backlog sources and wants static repo-impact triage. Do not use for discovery, duplicate-bug triage, validation, or fixes.

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

Use when the user dumps a batch of inputs at once — a pile of emails, a backlog of Slack/Teams messages, a list of asks, meeting action items, a notes brain-dump — and needs it sorted into action. Classifies each item, assigns owner + next step + priority, and flags which need a full /structure brief or a /decide call. Trigger on "/triage", "triage this", "process my inbox", "sort these asks", "clear my backlog", "what do I do with all this".

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

Use when evaluating whether a bug issue has sufficient detail and identifying missing reporter information. Not for non-bug issues or backlog triage: use github-backlog-triage.

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

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

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

End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue properly", or /gaia-issue-resolver. Works any gaia-research org repo — gaia-skill-tree, gaia-research, gaia-skill-heaven — while the issue itself lives on the headquarters tracker, gaia-research/gaia-skill-tree. Assumes the issue is already triaged and carries a P0–P4 label; if it does not, run /gaia-triage first.

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

Performs fast first-pass triage of an unknown file to decide depth of analysis: file type identification, hashing, reputation lookup, packing/entropy check, and string review. Activates for requests to triage, classify, or do initial assessment of an unknown or suspicious file.

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

Manage QA release gates - go/no-go decisions, release sign-off reports, defect triage, and release readiness communication. Use this skill whenever a QA lead or manager needs to formally assess whether a build is ready to ship. Trigger on phrases like "release sign-off", "go or no-go", "is this ready to release", "defect triage", "release gate", "approve the release", "block the release", "release readiness", "quality gate", "sign off on this build", "triage these bugs", or any request to make or document a formal release decision. Also trigger when a release manager or PM asks "what's the QA status?" or "can we ship this?".

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

Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.

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

Triage GitHub issues through a label-based state machine. 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.

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

Operational decision frameworks: triage, escalation, case management, billing ops. Use for 'how to handle X cases', 'build triage', 'escalation protocol'.

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

Sets up an `## Agent skills` block in AGENTS.md/CLAUDE.md and `docs/agents/` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.

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

Use this skill when a supplier has returned a security questionnaire, assurance report, certificate or trust pack and someone asks "review this vendor's answers", "is this supplier safe to use", "read their SOC report for us", "what should we ask the vendor next", "triage the vendor security assessment" or "does their certificate cover the service we buy". Checks report and certificate scope against the service in use, sorts answers into evidenced, asserted, contradicted and evasive, lists the obligations the report puts back on the customer, and writes a triage note with follow-up questions and a proposed decision for the owner.

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

Use this skill when something is happening now: an alert, a suspicious login, a ransomware note, data sent to the wrong customer, an outage that might be an attack, and someone asks "how bad is this", "classify this incident", "is this a SEV1", "who do we wake up", "is this a breach", "do we need to notify anyone" or "start the incident log". Classifies the incident on the company's own scale in minutes, decides who is called and how fast, flags any regulatory or contractual clock, lists the evidence to preserve, and starts a timestamped triage record that is revisited as facts change.

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

Triages GitHub issues and PRs into maintainer-facing cards: what each is, why it matters, author trust, risk, test and CI state, blockers, and next action. Use when the user says triage inside a repository or needs to work through an issue or PR queue.

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

Run an autonomous triage-resolve-review-merge loop to auto-pilot the GitHub issue backlog, resolving everything until done with zero prompts. Don't use for single-issue work (/issue-resolver), triage (/issue-triage), or PR review (/issue-pr-review).

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

spec-drift issue が起票され diff トリアージが必要なとき、C11 が再構成した issue 単位の完全 diff を hunk 化し name/type/required/enum/semantics 各軸の影響を before/after/evidence 付きで判定して triage-report を出したいときに使う。

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

- РАЗБОР ВХОДЯЩЕГО от живых людей: кто написал нам в Telegram (личка + упоминания в группах), WhatsApp и другие мессенджеры, сколько часов ждёт, кто он такой, сколько он стоит нашего внимания -- и… Триггеры: “/triage“, “/триаж“, “разбери входящие“, “разбери инбокс“, “кто нам написал“, “кто ждёт ответа“, “разбери личку“, “проверь сообщения“, “разбери телеграм“, “triage my inbox“, “who wrote to us“

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