「root」の検索結果

Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.

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

Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.

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

Design an error analysis protocol to diagnose the root cause of student mistakes and misconceptions. Use when error patterns appear in student work and targeted feedback is needed.

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

Fetch GitHub CI failure information, analyze root causes, reproduce locally, and propose a fix plan. Use `/fix-ci` for current branch or `/fix-ci <run-id>` for a specific run.

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

Autonomous cloud-cost analyst across Neon, Vercel, Railway and GitHub Actions - pulls per-object usage, attributes it to the biggest drivers, root-causes each, and emits recommendations ranked by real signal (idle %, over-allowance, failure rate) with dollar figures only where the billing API returns real ones (and, armed, applies safe cost levers).

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

Return rate reduction — root cause analysis, listing accuracy, packaging improvements, size guides

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

Configure or change the approved worker models for codex-on-crack, inspect available models and compatibility, preview role files, or undo a setup. The user selects the lead in Codex. Setup preserves root settings, credentials, unrelated agents, and config.toml.

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

Systematically trace bugs backward through call stack to find original trigger

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

Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.

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

Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.

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

Manage capa CLI configuration — `capabilities.yaml` / `capabilities.json`, skills, MCP servers, tools, hooks, sub-agents, rules, plugins, AGENTS.md / CLAUDE.md, security options, tool exposure modes, `capa wrap` shadow workspaces, `--passthrough` native writes, registries (including Claude marketplaces), activity traces, and the local Web UI. Use whenever the user edits the capabilities file, runs any `capa` command (init, install, add, wrap, clean, sh, start/stop/restart/status, auth, upgrade, cache, registry), wires up an MCP server, adds a skill from GitHub / GitLab / a registry / a remote URL / a local path, configures secrets via `${VarName}` placeholders, installs lifecycle hooks, defines sub-agents, or troubleshoots a failed install. Use even when the user only names a fragment ("add a skill", "wire up brave search", "wrap cursor", "block this phrase in skills") without saying "capa" — if a `capabilities.yaml` or `capabilities.json` lives at the project root, this is almost certainly the right skill. If the project does NOT yet have a capabilities file, point at the `bootstrap` skill instead.

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

ComfyUI Lumi Batcher 项目知识库根节点。导航时机：了解项目整体架构、查找功能所在模块、代码库概览。关键词：comfyui, lumi-batcher, 批量处理, 插件。

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

Review dimensions and scoring for root cause analysis quality assessment

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

Bug fix workflow: root cause analysis → user review → regression test + fix via TDD

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

Monthly, and on its first run it is the whole setup, launched by hand. It discovers what the member actually runs by walking their code roots and reading the registrar, the host, and the hosted database, then writes the inventory, the domains file, the starting budgets, and the opening safe fix rules, seeds the board, builds the dashboard, and registers one scheduled job per routine. It creates no account, buys nothing, and provisions nothing.

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

Dung khi so lieu marketing dang xau va can biet TAI SAO — chan doan theo 5 lop tu tracking, delivery, creative, landing den chat luong audience, roi ra action plan 48h. Kich hoat khi user nhac 'so dang xau', 'CPMess cao qua', 'ROAS thap', 'chan doan root cause', 'tai sao khong ra don', 'ads dot tien'. Khong dung cho — audit CAU HINH tai khoan ads va cham Health Score thi dung skill 21-audit-ads-performance; viet bao cao cho nguoi khac doc thi dung skill 07-bao-cao-marketing; chan doan rieng mot trang thi dung skill 68-cro-audit-trang.

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

Use when marketing numbers look bad and the user needs to know WHY — layered root-cause diagnosis across tracking, delivery, creative, landing page, offer, and audience quality, 5-Whys, regional benchmarks for US, EU, SEA, and LATAM, and a 48-hour action plan. Covers dropshipping ROAS and BE-ROAS. Trigger on 'why is CPA so high', 'my ads are not converting', 'ROAS dropped', 'we are burning budget', 'performance is bad this month', 'diagnose the funnel'. Also use when the user pastes a screenshot of numbers with no question attached. Not for — auditing account configuration and scoring health, see `21-ads-audit-global`; writing a report someone else reads, see `07-marketing-report-global`; turning a raw export into insight, see `13-data-analysis-global`.

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

Use when raw data exists — Meta, Google, TikTok, GA4, Shopify, a CRM export, or a spreadsheet — and has to become insight and decisions: descriptive, diagnostic, predictive, and prescriptive layers, cuts by channel, campaign, creative, audience, and time, cohorts, and a decision log. Trigger on 'analyze this data', 'read these numbers for me', 'what does this export say', 'pull insight from GA4', 'cohort analysis', 'here is the spreadsheet'. Also use when the user pastes a table and asks what it means. Not for — diagnosing ad root cause, see `03-performance-eval-global`; writing the report a stakeholder reads, see `07-marketing-report-global`; auditing account setup, see `21-ads-audit-global`.

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

Use when the user asks which GSD workspaces exist, or where their isolated work lives. Scans the workspaces root for WORKSPACE.md manifests and prints name, path, repo count, strategy and project status.

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

Use when a GSD run failed, stalled, or produced the wrong result and the cause is unclear. Reads git history and .planning/ state and phase artifacts to diagnose root cause, then writes a report to .planning/forensics/.

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

Persistent project goal that survives across sessions and tools, with continuous-execution loop semantics. Use when someone asks to "set a goal", "what is my goal", "goal status", "keep working on X until done", "resume the goal", or wants work to continue across sessions until an objective is achieved. File-backed (.goal.md at project root); shared by every Coco-installed tool working in that repository.

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

Quarantines an intermittently failing test behind a ticket with an owner and expiry, assigns a root-cause bucket from isolated reruns, and defines when the test leaves quarantine. Use when a test is a QUARANTINE_CANDIDATE or fails without a code change; not for deterministic failures.

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

Secure Flutter token/PII storage, build-time secrets, network trust, and release hardening using OWASP Mobile practices. Use for secure storage, secret injection, certificate pinning, jailbreak/root risk, or release builds—not generic form validation, API error handling, auth-provider setup, or tests of existing security services.

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

Investigate Elixir/Phoenix bugs root-cause first. Reproduce failures, cite evidence, and use optional native DeepSeek Harness subagents only when useful.

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