「investigate」の検索結果

Deep autonomous diagnosis of a failed flow run. Provide environment, flow, and run IDs. Use when the user asks to diagnose or deeply investigate a specific failed flow run.

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

Investigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced. Use for diagnosis and repair; follow incident authority for live mitigation.

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

Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug, build error, broken, not working, why is X failing, check this code, security check, PR review, audit code, refactor. Also triggers when investigating 4xx or 5xx errors, deploy failures, environment variable issues, and CMS integration problems.

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

Systematic root-cause debugging. Iron Law: no fixes without root cause investigation first. Four phases: Root Cause Investigation, Pattern Analysis (6 known patterns), Hypothesis Testing (3-strike rule), Implementation. Structured debug report output.

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

Diagnostic-only skill for Slurm scheduler and node-daemon issues on Amazon SageMaker HyperPod Slurm clusters. Scope mirrors the HyperPod troubleshooting guide. Invoke when the user reports a Slurm node stuck in down/drain, "Node unexpectedly rebooted" after auto-repair, slurmd not running, jobs stuck PENDING with REASON=Resources while sinfo shows idle nodes, jobs stuck COMPLETING after node replacement, GRES/GPU counts wrong, scontrol ping failing, slurmctld unresponsive, an Action:Reboot/Replace request that did not trigger HyperPod auto-recovery, or auto-resume not restarting a job. Also triggers on "drain before reboot", "diagnose a Slurm node", "investigate stuck jobs."

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

Generate comprehensive issue reports from HyperPod clusters (EKS and Slurm) by collecting diagnostic logs and configurations for troubleshooting and AWS Support cases. Use when users need to collect diagnostics from HyperPod cluster nodes, generate issue reports for AWS Support, investigate node failures or performance problems, document cluster state, or create diagnostic snapshots. Triggers on requests involving issue reports, diagnostic collection, support case preparation, or cluster troubleshooting that requires gathering logs and system information from multiple nodes.

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

When you want multi-source, multi-step research on a topic — competitor research before a sales call, market research for a new business idea, positioning angles, due diligence on a partnership or podcast guest, tech decision research (which DB, which auth), or any "I need to actually understand X." Combines web search, URL fetch, agent-browser, last30days (Reddit/X/YouTube/HN/web recency), memory, and Notion. Outputs a structured brief with citations, contradictions, gaps, and recommended next steps. Archives every research run to ~/.config/makerskills/deep-research/archive/ so past work is searchable. Triggers on "/deep-research," "research X," "investigate X," "do a deep dive on X," "look into X," "what's actually happening with X," "due diligence on X," "validate this market." Differs from a one-shot web search: this is multi-pass with verification.

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

Forensic financial analysis for A-share companies. Identifies discrepancies, potential irregularities, and earnings quality issues in Chinese financial statements. Adapted from the original break-trace skill for CAS accounting and Chinese market red flags. Triggers on "A股财务核查", "财务异常", "forensic analysis China", "财务舞弊", "earnings quality China", or "investigate [company] financials".

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

Forensic financial analysis for A-share fund holdings and portfolio companies. Adapts the original break-trace skill for fund administration context and Chinese market standards. Triggers on "基金持仓核查", "持仓异常", "forensic fund analysis China", "持仓质量分析", or "investigate [fund] holdings".

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

This package enables the interpretation and analysis of results from a gene set enrichment analysis using network-based and text-mining approaches. Most enrichment analyses result in large lists of significant gene sets that are difficult to interpret. Tools in this package help build a similarity-based network of significant gene sets from a gene set enrichment analysis that can then be investigated for their biological function using text-mining approaches.

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

InterCellar is implemented as an R/Bioconductor Package containing a Shiny app that allows users to interactively analyze cell-cell communication from scRNA-seq data. Starting from precomputed ligand-receptor interactions, InterCellar provides filtering options, annotations and multiple visualizations to explore clusters, genes and functions. Finally, based on functional annotation from Gene Ontology and pathway databases, InterCellar implements data-driven analyses to investigate cell-cell comm

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

R generic interface to Hi-C contact matrices in `.(m)cool`, `.hic` or HiC-Pro derived formats, as well as other Hi-C processed file formats. Contact matrices can be partially parsed using a random access method, allowing a memory-efficient representation of Hi-C data in R. The `HiCExperiment` class stores the Hi-C contacts parsed from local contact matrix files. `HiCExperiment` instances can be further investigated in R using the `HiContacts` analysis package.

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

Evaluate and plan Amazon marketplace expansion across countries and regions. Use when a seller asks which Amazon marketplace to enter, how to compare international demand and economics, what tax, product-compliance, logistics, localization, account, or launch workstreams to investigate, or how to build a gated global-selling roadmap. Do not use as legal, tax, customs, or certification advice.

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

Use multiple Claude agents to investigate and fix independent problems concurrently

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

Detect and investigate bulk registration abuse on SaaS platforms. Given access to a user database (or exported CSV/JSON), run a multi-dimensional anomaly analysis — email domain clustering, registration tempo, UA fingerprinting, session structure, usage patterns, and credit consumption — to produce a scored abuse report with actionable recommendations. Use when investigating suspicious sign-up spikes, credit fraud, free-tier abuse, or account farming.

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

Use the official Sentry CLI to investigate issues, events, traces, and logs for Vibe Remote without committing Sentry credentials into the repository.

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

Scaffolds a structured investigation in scratch/ for empirical research and documentation. Use when the user says "start an investigation" or wants to: trace code paths or data flow ("trace from X to Y", "what touches X", "follow the wiring"), document system architecture comprehensively ("document how the system works", "archeology"), investigate bugs ("figure out why X happens"), explore technical feasibility ("can we do X?"), or explore design options ("explore the API", "gather context", "design alternatives"). Creates dated folder with README. NOT for simple code questions or single-file searches.

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

Handle SLEAP GitHub support workflow for issues and discussions. Use when the user says "support", provides a GitHub issue/discussion number like "#2512", or asks to investigate a user report from talmolab/sleap. Scaffolds investigation folders, downloads posts with images, analyzes problems, and drafts friendly responses.

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

Investigate questions using high-trust primary sources and traceable citations. Use when the user asks for research, current documentation or API facts, source verification, or evidence-backed comparison.

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

Use when you want phase research without planning: to investigate before deciding a phase is feasible, or to re-research after a plan already exists. Standalone command; most workflows should use /gsd-plan-phase instead.

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

Investigate requirements via atomic AC decomposition, actor/permission matrices, and truth-table edge cases; enforce User Story standards (scope fences, platform tags, toggles). Use when writing/reviewing Stories or AC with multi-condition logic, feature toggles, or market variants (VN/MY/SG).

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

Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /phx-review or /phx-investigate.

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

Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /skill:phx-review or /skill:phx-investigate.

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

Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (/phx-investigate).

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