「triage」の検索結果

Prepare the NemoClaw morning maintainer plan: triage the backlog, select a target version, and identify release candidates and stragglers.

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

Reproduce stale NemoClaw bug reports on the reported and newest releases, then propose evidence-backed triage. Never auto-closes issues.

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

Answer NemoClaw maintainer policy questions about triage, labels, Project fields, releases, or competing contributions. Read-only.

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

Triage, diagnose, debug, or fix failing or flaky NemoClaw E2E tests. Trace every assertion and downstream gate before a repair push or rerun. Excludes status-only and dispatch-only requests.

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

Propose and apply authorized Issue Type, Project fields, and labels for NemoClaw issues or PRs, individually or in a batch.

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

Queries and retrieves active security findings, external exposures, toxic combinations, vulnerabilities, threats, and sensitive data risks from Security Command Center on Google Cloud. Use when retrieving details for a security finding by its name, validating finding scope (e.g., verifying findingClass is TOXIC_COMBINATION, VULNERABILITY, EXTERNAL_EXPOSURE, or THREAT), or fetching finding details for triage. Don't use to draft remediations, apply patches, or execute configurations.

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

The phishing-report triage runbook — how to check headers, links, and attachments on a reported email against {{report_query}}, classify the risk, and post a verdict with a recommended action to {{security_channel}}. Analyze and recommend only; never block, delete, or remediate.

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

Daily reusable-session flaky-test triage for {{target_repo}}. Pulls CI run history from GitHub, scores each test's non-determinism against a persistent per-test ledger, and once a test reaches {{quarantine_threshold}} opens a quarantine PR (skip + reason, never delete) plus a running tracking issue, and posts a summary to {{alert_channel}}. Never merges.

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

Triage loop for inbound HR policy questions. Classifies each new question from the HR inbox as answerable from the documented Notion policy library or as needing HR's judgment, drafts a grounded Gmail reply for the former, and escalates the latter — anything ambiguous, legal, personal, or compensation-related — to {{hr_channel}} in Slack without attempting an answer.

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

Diagnose Sentry issues without copy-pasting stack traces. Uses the Composio CLI to pull issue details, events, breadcrumbs, and suspect commits, then maps the frames to local source so the agent can propose a fix directly.

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

Assess community issues, validate technical claims, request missing evidence, and prepare valid work for human disposition.

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

Validate and monitor OpenShell GitHub issues and PRs using the gator:* state machine. Use when asked to triage issues/PRs for project validity, gate PRs, run gator, validate submissions, or monitor PRs toward merge readiness.

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

Diagnose a failing GitHub Actions run — find the first real error in the logs, tell a flake apart from a genuine failure, and identify the commit that broke it. Use when checks are red on a PR, a workflow failed, the build is broken, CI is flaky, or the user asks why a run failed or whether a failure is real.

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

Draft a reply, a follow-up, or a new email in Superhuman in the user's own voice — read the whole thread first, reuse an existing draft instead of adding a second one, keep the right people on the thread, and leave sending to the user unless they asked for it. Use when the user says reply to, answer, follow up with, draft an email to, or send, or when a triage turned up threads that need a response.

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

Help clarify human bug reports, search for duplicates, and gather diagnostic evidence separately from a concise issue draft.

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

Read loop-constraints.md at the start of every run and enforce every rule. This skill runs BEFORE triage or any action skill. Constraints are binding.

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

Scan package manifests and lockfiles for outdated packages and known CVEs. Groups updates by risk (patch, minor, major). Use in dependency sweeper loops.

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

Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.

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

Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.

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

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

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

Scan package manifests and lockfiles for outdated and vulnerable dependencies. Classify by severity and update type.

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

Parse CI failures, identify failing job/step, classify as flake, regression, env, or config. Use in CI sweeper loops before any fix attempt.

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

Triage and review open GitHub issues and PRs against project templates and contribution guidelines.

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

Shallow (quick) ensemble bug-finding review using 6 specialist agents in parallel. Each specialist reviews the same patch through a different lens: Logic & Types, Boundaries & I/O, Concurrency & State, Resources & Serialization, Absence Analysis, and API Completeness. Findings are merged and deduplicated. Best for: quick first-pass review of patches, triage of diffs, broad surface-level bug scan. For deeper file-focused review with full pattern catalogs and codebase investigation, use the deep-review skill instead.

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