「triage」の検索結果

Read a liarjs fingerprint report and attribute each failing check to the component that produced it - what the check id measures, whether the signal comes from the launch configuration, the page-modifying layer, the network path or the machine image, and which failures are inherent to headless or datacenter environments. Use when a fingerprint scan came back with a low score, or when a check id such as webdriver, worker-consistency, gpu-triad, native-integrity or tz needs explaining.

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

Detects and removes contamination in genome assemblies via two disjoint workflows - foreign-sequence screening of a single-organism (eukaryote/isolate) assembly with NCBI FCS-GX (GenBank-submission-mandatory), FCS-adaptor, and BlobToolKit blob plots; and MAG/bin quality assessment with CheckM2 plus GUNC (chimerism) plus GTDB-Tk taxonomy, judged against MIMAG. Covers why CheckM2 alone is blind to disjoint-marker chimeras, the FCS-GX RAM wall, organelle/NUMT triage, strain heterogeneity, and the HGT-vs-contamination (tardigrade) trap. Use when screening an assembly for foreign contamination before GenBank submission, assessing MAG completeness/contamination/chimerism, deciding which contigs to remove, or distinguishing real HGT from contaminant contigs.

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

Assigns isolate identity at the right resolution for the question -- ANI / Mash species triage, 7-locus MLST historical comparability, cgMLST / wgMLST outbreak resolution (chewBBACA, BIGSdb, Ridom SeqSphere, EnteroBase HierCC), in-silico serotyping (SISTR, SeqSero2 for Salmonella; SerotypeFinder for E. coli; Kaptive K/O for Klebsiella; SeroBA for pneumococcus; spa + SCCmec for S. aureus), and lineage callers (TB-Profiler / Mykrobe Coll-Napier barcode for MTBC, Pangolin + Nextclade for SARS-CoV-2, PopPUNK GPSC for S. pneumoniae). Use when typing bacterial isolates for surveillance or outbreak investigation, choosing between cgMLST allele distance and core-SNP distance for cluster definition, harmonising calls across schemas / database versions (chewBBACA vs Ridom vs EnteroBase), assigning MTBC lineage with the Napier 2020 90-SNP barcode, calling Salmonella serovar via SISTR with monophasic Typhimurium awareness, running Pangolin UShER mode with explicit pangolin-data version pinning, or selecting a typing resolution to match the surveillance question.

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

Classify a request into type, risk, and the destination CodeConductor command.

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

Weekly sweep of ALL transcript-bearing spoken events (earnings calls, conference firesides, CMDs, investor days, AGMs, investor updates) for every active thesis, via the Quartr watchlist. Produces a triage digest in Daily Intel/ flagging thesis-touching mentions and recommending deep reads. Use when user says "event sweep", "what did my companies say this week", "conference sweep", or on the weekly schedule. Also `--setup` (build/rebuild the Quartr watchlist from active theses) and `[N]` (window override in days, default 8).

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

GitHub issue の実装難易度を tier(S / M / L / XL)として判定する。判定は TypeSafe AI(Jev)で行い、不通時は Claude が同じ基準で代行する。/dev がステップのモデル・effort・スキップを決めるために呼ぶ。

Triage defects with independent severity and priority, reproducible evidence, preserved attempt history, and explicit resolution retesting.

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

Record a reproducible defect, independent triage, immutable attempts, and evidence-backed retest state.

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

Tickets, triagem, followups, solução, usuários, grupos, ativos, projetos e base de conhecimento no GLPI via MCP glpi.

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

Conduz investigação de incidente — triagem, hipótese, mitigação, RCA e postmortem. Use quando o usuário disser "está fora do ar", "incidente", "caiu", "usuários reclamando", "erro em produção", "postmortem", "RCA", "o que aconteceu". Durante incidente, a pressa causa o segundo incidente.

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

Respond to production incidents systematically with triage, investigation, resolution, and post-mortem analysis to minimize downtime and prevent recurrence. Use when handling production outages, triaging incidents, investigating critical bugs, coordinating incident response, implementing hotfixes, conducting post-mortems, or establishing incident response procedures.

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

Review, repair and steward the nightly Codex debt-sweep PR (branch codex/daily-debt/<date>). Judges every commit GOOD / REPAIR / REVERT, triages the bot review findings through /fix, lands one round-1 commit, files follow-up issues, then stewards the PR itself with a 3-round ceiling. Run by the 08:00 UTC cloud routine; also '/debt-review', '/debt-review 1789'.

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

Adversarial triage of open review findings on a PR. Every finding (Codex, Claude bot, Gemini) is a hostile hypothesis to REFUTE — fix only what is proven real, reachable, in the PR's scope, and above the round's severity bar. The bar rises every review round. Everything else is declined or filed as an issue. Use for 'fix the PR findings', '/fix', '/fix 123', or before any fix commit in a review loop.

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

Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".

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

Investigate and triage runtime incidents involving the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM as a Cloud Service environments only, using runtime-backed MCP evidence.

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

Triage AEM Workflow issues on AEM as a Cloud Service by classifying symptoms, gathering the right logs and metrics, and mapping to runbooks or Splunk searches. Use when the user asks for workflow activity/errors on a Cloud Service host, needs to classify a Jira ticket, or wants to know what to collect for workflow debugging.

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

Build a "product description" repo for a software product — a set of prose documents describing, from the outside in, what the user sees, what they can do, and exactly what happens when they do it, written from the code and tests, then verified against the running product and triaged into a bug list. Works for any product with a user (canvas editors, web apps, CLIs, chat products, mobile apps). Use when the user asks to "write a product description for X", "describe the user experience of X", "document how X behaves for the user", "make a behavior-spec repo", or wants a feature-by-feature, event-by-event account of an app's behavior rather than API docs. Also use to resume or extend an existing product description repo.

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

Decompose multi-step work into a revisable subgoal plan with stable step IDs, checkpointing, and plan-ahead execution. Load when a task needs explicit planning before action, subgoal decomposition, plan checkpointing, or ReCAP-style plan-ahead execution. Also triggers on "structured plan", "plan with steps", "subgoal graph", "revise the plan", "checkpoint plan", or multi-step tasks where naive one-shot execution would be fragile. Skips trivial single-step tasks. Pairs with dynamic-routing on failure. Distinct from process-decomposer (registry/triage) and problem-to-plan (doc deliverables).

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

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.

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

Detects and removes contamination in genome assemblies via two disjoint workflows - foreign-sequence screening of a single-organism (eukaryote/isolate) assembly with NCBI FCS-GX (GenBank-submission-mandatory), FCS-adaptor, and BlobToolKit blob plots; and MAG/bin quality assessment with CheckM2 plus GUNC (chimerism) plus GTDB-Tk taxonomy, judged against MIMAG. Covers why CheckM2 alone is blind to disjoint-marker chimeras, the FCS-GX RAM wall, organelle/NUMT triage, strain heterogeneity, and the HGT-vs-contamination (tardigrade) trap. Use when screening an assembly for foreign contamination before GenBank submission, assessing MAG completeness/contamination/chimerism, deciding which contigs to remove, or distinguishing real HGT from contaminant contigs.

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

Assigns isolate identity at the right resolution for the question -- ANI / Mash species triage, 7-locus MLST historical comparability, cgMLST / wgMLST outbreak resolution (chewBBACA, BIGSdb, Ridom SeqSphere, EnteroBase HierCC), in-silico serotyping (SISTR, SeqSero2 for Salmonella; SerotypeFinder for E. coli; Kaptive K/O for Klebsiella; SeroBA for pneumococcus; spa + SCCmec for S. aureus), and lineage callers (TB-Profiler / Mykrobe Coll-Napier barcode for MTBC, Pangolin + Nextclade for SARS-CoV-2, PopPUNK GPSC for S. pneumoniae). Use when typing bacterial isolates for surveillance or outbreak investigation, choosing between cgMLST allele distance and core-SNP distance for cluster definition, harmonising calls across schemas / database versions (chewBBACA vs Ridom vs EnteroBase), assigning MTBC lineage with the Napier 2020 90-SNP barcode, calling Salmonella serovar via SISTR with monophasic Typhimurium awareness, running Pangolin UShER mode with explicit pangolin-data version pinning, or selecting a typing resolution to match the surveillance question.

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

Production error → triaged, root-caused, repaired, and certified (tsc + rehearsal + reproduce-then-gone) fix PR for a human to merge — then confirm the error stops recurring. Never auto-merges.

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

open な issue 一覧を取得し、内容を分析して status ラベルを付与する

Runs the morning maintainer standup for NemoClaw. Triages the backlog, determines the day's target version, labels selected items, surfaces stragglers from previous versions, and outputs the daily plan. Use at the start of the workday. Trigger keywords - morning, standup, start of day, daily plan, what are we shipping today.

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