「issue-triage」の検索結果

Scan open issues and discussions. Dedupe, prioritize, and propose labels. Updates issue-triage-state.md. L1 propose-only — never auto-label or close.

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

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.

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

Triage Paperclip inbox issues that are stale, blocked, in-review, or assigned-but-not-progressing, and decide a single next action per issue (resume, reassign, unblock, escalate, or close).

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

Triage complet RTK : exécute issue-triage + pr-triage en parallèle, puis croise les données pour détecter doubles couvertures, trous sécurité, P0 sans PR, et conflits internes. Sauvegarde dans claudedocs/RTK-YYYY-MM-DD.md. Args: "en"/"fr" pour la langue (défaut: fr), "save" pour forcer la sauvegarde.

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

Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.

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

Triage Linear or Jira backlogs and run bug sweeps via the Composio CLI. Bulk-fetch issues, dedupe, relabel, reassign, and post summaries — all from the shell without clicking through the UI.

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

Triage a GitHub issue into something actionable — reproduce the claim, find duplicates, judge severity, and apply labels, milestone, and assignee. Use when the user asks to triage an issue, sort the backlog, deal with new issues, check whether a bug is already reported, or says "what should we do with this issue".

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

Scan open issues and discussions, deduplicate, prioritize, and propose labels. Provides a clean actionable queue.

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

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

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

3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.

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

对照当前仓库契约、源码、Runtime、测试和安装行为，验证并分类 Comet GitHub Issue。用户询问 Issue 是否真实、可复现、重复、已实现、属于配置问题，或是否适合后续处理时使用。

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

Triage and categorize new GitHub issues on watched repos

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

GitHub Issue 处理协作流程。当用户收到 issue 需要分析和回复时使用。通过"诊断 → 定性 → 决策 → 回复"四步法，从一个 issue 产出准确的根因分析和得体的用户回复，避免误判问题类型或回复不专业。

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

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.

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

Triage a raw, vague issue or bug report into a structured document that names what is known, what is missing, and what to do next. Use when an incoming issue, bug report, or problem description is too vague or incomplete for investigation or planning, and recommend the right next han skill. Does not investigate root causes or trace code paths — use investigate for debugging, diagnosis, and root cause analysis. Does not plan features or build solutions — use plan-a-feature or plan-implementation for that.

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

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.

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

Use when a human invokes triage on a new configured Slack issue report. Not for triaging reports from other channels or posting more than one verdict.

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

Triage Linear or Jira backlogs and run bug sweeps via the Composio CLI. Bulk-fetch issues, deduplicate, relabel, reassign, and post summaries all from the shell.

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

GitHub project management via the gh CLI — create and triage issues, manage GitHub Projects v2 boards (add items, update status fields), manage labels and milestones, and generate handoff-status summaries. Use when "create a GitHub issue", "add to project board", "update sprint status", "create label/milestone", or "give me a handoff summary of open work". NOT for code review (see mk:review-pr); NOT for PR creation (see mk:ship); NOT for git operations (see mk:ship / mk:resolving-merge-conflicts).

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

Analyze one GitHub issue for root cause, complexity, and risk into .idd/analysis-N.json. Use when you need to analyze or scope issue #N. Don't use for creating issues (/issue-creator), triaging (/issue-triage), or resolving (/issue-resolver).

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

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

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

Scan open GitHub issues for dependencies, priority, parallel work, and staleness. Use to prioritize the backlog or pick what to do next. Don't use for one-issue analysis (/issue-analysis), resolving (/issue-resolver), or creating (/issue-creator).

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

Triage Linear or Jira backlogs and run bug sweeps via the Composio CLI. Bulk-fetch issues, dedupe, relabel, reassign, and post summaries — all from the shell without clicking through the UI.

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