1천건 · 관련도순
Investigate a Sandcastle GitHub issue, classify the report, check for duplicates or existing fixes, and attempt reproduction with Docker. Return a minimal reproduction script, observed results, and a likely cause, noting any environment limitations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review recent unread Gmail messages and sort them into urgent, reply soon, waiting, and FYI groups. Each entry includes a reason and suggested next action, with reply drafts created only when requested.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Group bug reports by their underlying cause and plan shared fixes. This skill guides reproduction, checks for unnecessary complexity, and requires named test evidence before treating related issues as resolved.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize open GitHub issues and pull requests using the gh CLI, GitHub's command-line tool. Identifies resolved issues and pending fixes, estimates priorities and change sizes locally, and proposes closures, links, reviews, or merges for approval.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Evaluate supplied security findings against repository code and security policy without running the software. Classify each claim as confirmed, not actionable, or needing review, then rank relevant findings by exploitability and explain evidence gaps and next steps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review code changes and pull requests, assess release readiness, or triage issues using project rules and current evidence. Reports identify concrete triggers and verification gaps, while authorized shipping tasks include checks of the resulting delivery state.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Organize open pull requests by size, automated check results, inactivity, and overlapping files. Review selected changes in depth, prepare comments for approval, and optionally create separate local working directories for hands-on review.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use this skill to triage ONE microsoft/apm pull request already selected by autopilot-pr-triage-scheduler. Covers community PRs that fix an issue and PRs opened without an issue. Return one advisory recommendation, never human approval, never a diff review, never merge. Not a queue manager and not autopilot-pr-review-worker.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Queue open microsoft/apm pull requests (community fixes, PRs without an issue, or PRs that close an issue) and fan them out through an isolated pool (default 2) of autopilot-pr-triage-worker sessions. Advisory only. Never merges, never assigns, never requests reviewers, never runs autopilot-pr-review-worker. Activate on a mixed PR list or queue-open when the job is PR triage. Works in a local session, Copilot App automation, Cloud Agent, Remote Agent, or Agentic Workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to triage ONE microsoft/apm issue already selected by autopilot-issue-triage-scheduler. Return one advisory recommendation and a proposed scope brief, never human approval. Do not implement the issue, manage the backlog, or list the queue.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Queue open microsoft/apm issues and fan them out through an isolated pool (default 2) of autopilot-issue-triage-worker sessions. Advisory only. Never implements, never assigns, never requests reviewers. Activate on a mixed issue list or queue-all when the job is triage. Works in a local session, Copilot App automation, Cloud Agent, Remote Agent, or Agentic Workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "triage our comments, DMs, and mentions", "draft replies to this thread", "can we repost this fan post", or "set up inbox SLAs and an escalation path"; produces a ranked triage queue with register detection (sincere / ironic / performative / parasocial, sentiment-inversion table included — "this is so bad" under a comedy register is praise), a commenter taxonomy (troll monitor-only / rager / misguided / unhappy-customer / advocate) with a response-tier ladder and per-channel SLAs, an escalation matrix ending at the crisis path, a moderation ladder plus house rules for owned spaces, and a UGC curation-and-rights mode whose dated permission entries route to the channel registry — every reply is a ranked DRAFT a human posts; nothing is ever auto-sent. Not for launch-window feedback triage — use launch-feedback-synthesizer. 评论私信提及分诊/语域识别/回复草稿/UGC授权
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action for each (draft reply, calendar hold, scaffold a project, snooze). Use when user says "triage my inbox", "check my academic email", "what needs my attention this week", "go through my mail", or when run as a scheduled routine. NEVER auto-sends or auto-accepts anything.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage a raw bug report into something a team can act on — clean repro steps, a defensible severity/priority, environment, likely area/owner, and duplicate check. Use when asked to triage this bug, set severity and priority, is this a P1, or clean up this bug report for the backlog. Produces the normalized repro, a severity and priority with the reasoning (impact × frequency × workaround), the environment/metadata, a suspected component and owner queue, and a duplicate/related-issue check — flagging when info is missing rather than guessing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Collecting and synthesizing user feedback across channels (support tickets, NPS, in-app feedback, sales calls, social mentions, customer councils) into a continuous signal that informs product decisions. The triage discipline that distinguishes loudest-voice (whoever complains most wins) from averaged-noise (every signal weighted equally) from triaged-synthesis (signal weighted by source quality, frequency, and decision relevance). Triggers on user feedback, customer feedback aggregation, NPS, support ticket analysis, customer councils, feedback synthesis, voice of customer, feedback triage, in-app feedback. Also triggers when feedback channels overflow with volume that does not produce decisions, when the loudest-voice problem is steering roadmap, or when continuous feedback streams need synthesis discipline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fast 15-25 minute triage for preliminary EU AI Act classification and compliance assessment. This skill should be used when the user asks to "do a quick AI Act assessment", "check if the AI Act applies to us", "run a preliminary classification", "do an AI Act triage", "quick check", "preliminary assessment", "Schnellprüfung", "Ersteinschätzung", or needs a fast initial assessment before committing to full analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When you want to manage projects across your businesses using a kanban + Eisenhower methodology. One kanban per business (whatever portfolio of businesses, projects, or initiatives you run). Tool-agnostic — connects via API/MCP to whatever PM tool each business uses (Notion, GitHub Projects, Plane, Linear, Obsidian file-based, or manual mode). Async-first output. Six modes — setup (scaffold a new board for a business), triage (Eisenhower-sort the backlog), next (pick the next thing to work on, single board or across all), status (paste-ready async snapshot), unblock (diagnose Review/Blocked column), weekly (Friday pulse + week planning). Triggers on "/pm," "/pm setup," "/pm triage," "/pm next," "/pm status," "/pm unblock," "/pm weekly," "what should I work on next," "kanban status," "Eisenhower this," "triage my backlog," "what's blocked."
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage and categorize GitHub issues with priority labels. Use when user says "triage issues", "check issues", "review open issues", or during regular maintenance of GitHub issue backlog.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used only when the user explicitly asks to use `$ralph-specum-triage`, or explicitly asks Ralph Specum in Codex to triage a large effort into multiple specs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage a single security finding — from a scanner, audit, advisory, or report — to a defensible disposition with a mitigation plan, false-positive justification, or accepted-risk writeup. Use when the user mentions 'triage this finding,' 'is this a real vulnerability,' 'mitigation plan,' 'false positive,' 'accept this risk,' 'compensating controls,' 'risk justification,' 'security ticket,' 'CVSS this,' 'should we fix this,' 'disposition,' 'sign off on,' or has a single security finding and needs to decide what to do.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide rapid triage and initial response to security incidents following NIST SP 800-61 methodology. Use when the user mentions 'incident response,' 'security incident,' 'triage,' 'we've been hacked,' 'breach,' 'compromised,' 'malware detected,' 'suspicious activity,' 'IOC,' 'indicators of compromise,' or needs help handling a security event.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.