analyze-problem

Agent Skills › latitude-dev/latitude-llm › analyze-problem

analyze-problem

GitHub

分析 Bug 报告，通过追踪代码执行路径、数据流及对比预期行为，定位根因并提供修复方案与验证步骤。不自动修改代码，旨在提供详尽的问题诊断与解决建议。

.agents/skills/analyze-problem/SKILL.md latitude-dev/latitude-llm

触发场景

收到 Bug 报告或 Issue 需要深入排查代码缺陷

安装

npx skills add latitude-dev/latitude-llm --skill analyze-problem -g -y

更多选项

非标准路径

npx skills add https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/analyze-problem -g -y

不安装直接使用

npx skills use latitude-dev/latitude-llm@analyze-problem

指定 Agent (Claude Code)

npx skills add latitude-dev/latitude-llm --skill analyze-problem -a claude-code -g -y

安装 repo 全部 skill

npx skills add latitude-dev/latitude-llm --all -g -y

预览 repo 内 skill

npx skills add latitude-dev/latitude-llm --list

SKILL.md

Frontmatter

{
    "name": "analyze-problem",
    "description": "Analyze a problem and provide a detailed explanation of the issue, root cause, proposed fix, and verification steps."
}

Read the provided bug report/issue/task.

Then thoroughly investigate the codebase to understand the relevant context:

Find the entry points involved (routes/handlers/jobs/commands) and trace the execution path that leads to the reported behavior.
Identify the data flow and state involved (inputs, validation, persistence, caching, permissions, feature flags, side effects).
Locate the expected behavior (specs/tests/docs) and compare it to the actual behavior in code.
If the report includes steps to reproduce, map each step to the corresponding code path and decision points.
Consider common edge cases (null/empty values, timing/race conditions, retries, idempotency, pagination, timezones, auth, stale cache).

Deliverable: Explain, in your own words:

What you believe the issue is (observable behavior + when it happens),
Why you believe it is happening (root cause and the specific assumption/logic that breaks),
How you would fix it (proposed approach and what behavior/logic should change),
What you would verify (minimal set of checks/tests/logs to confirm the fix and prevent regressions).

Constraints:

Do not apply any changes automatically.
Avoid listing files/components/services unless strictly necessary to support the explanation.
If the codebase does not contain enough context to be confident, explicitly say what’s missing and what evidence would confirm the hypothesis.