Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Analyze a problem and provide a detailed explanation of the issue, root cause, proposed fix, and verification steps.
Install Analyze Problem
$ npx skills add latitude-dev/latitude-llm --skill analyze-problem -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install latitude-dev/latitude-llm analyze-problem --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/latitude-dev/latitude-llm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/analyze-problem .claude/skills/analyze-problem && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "analyze-problem" agent skill from https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/analyze-problem into .claude/skills/analyze-problem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-problem", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/analyze-problemType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add latitude-dev/latitude-llm --skill analyze-problem -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install latitude-dev/latitude-llm analyze-problem --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/latitude-dev/latitude-llm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/analyze-problem .agents/skills/analyze-problem && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analyze-problem" agent skill from https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/analyze-problem into .agents/skills/analyze-problem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-problem", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add latitude-dev/latitude-llm --skill analyze-problem -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install latitude-dev/latitude-llm analyze-problem --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/latitude-dev/latitude-llm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/analyze-problem .cursor/skills/analyze-problem && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "analyze-problem" agent skill from https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/analyze-problem into .cursor/skills/analyze-problem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-problem", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/latitude-dev/latitude-llm.git --path .agents/skills/analyze-problem--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add latitude-dev/latitude-llm --skill analyze-problem -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install latitude-dev/latitude-llm analyze-problem --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/latitude-dev/latitude-llm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/analyze-problem .gemini/skills/analyze-problem && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "analyze-problem" agent skill from https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/analyze-problem into .gemini/skills/analyze-problem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-problem", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install latitude-dev/latitude-llm analyze-problemInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add latitude-dev/latitude-llm --skill analyze-problem -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/latitude-dev/latitude-llm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/analyze-problem .github/skills/analyze-problem && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "analyze-problem" agent skill from https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/analyze-problem into .github/skills/analyze-problem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-problem", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add latitude-dev/latitude-llm --skill analyze-problem -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install latitude-dev/latitude-llm analyze-problem --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/latitude-dev/latitude-llm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/analyze-problem .opencode/skills/analyze-problem && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "analyze-problem" agent skill from https://github.com/latitude-dev/latitude-llm/tree/development/.agents/skills/analyze-problem into .opencode/skills/analyze-problem/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-problem", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
analyze-problem- GitHub stars
- 4.7k
- Token cost
- ~398 tokens
- SKILL.md length
- 196 words
- Files
- 1
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyze a problem and provide a detailed explanation of the issue, root cause, proposed fix, and verification steps.
- Works in 4 steps: What you believe the issue is… → Why you believe it is happening (root… → How you would fix it (proposed approach… → …
- Tasks that involve Root cause analysis
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Analyze Problem is an agent skill from latitude-dev/latitude-llm. Analyze a problem and provide a detailed explanation of the issue, root cause, proposed fix, and verification steps.
Its SKILL.md is about 400 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Root cause analysis. The repository describes itself as: Open-source observability for AI agents. Find where your agents fail, dispatch your coding agent to fix it, and verify the fix against real traces. The licence is MIT.
When your agent uses it
- Tasks that involve Root cause analysis
Example prompts
- “/analyze-problem”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- 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).
What it can do on your machine
Read from SKILL.md and the folder at commit 87e8aa0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Analyze Problem loads about 398 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 196 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from latitude-dev/latitude-llm at commit 87e8aa0, republished under its MIT licence (© latitude-dev). 196 words, ~398 tokens.
Download SKILL.mdSave it as
.claude/skills/analyze-problem/SKILL.md (or your agent's skills folder).- 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.
© latitude-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/analyze-problem of latitude-dev/latitude-llm.
Open the folder on GitHubat commit 87e8aa0
Compare with similar skills
Analyze Problem next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Analyze Problem this skilllatitude-dev/latitude-llm | 4.7k | — | ~398 | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Bug Finder for daisyUIsaadeghi/daisyui | 43k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Root Cause Debugginggarrytan/gstack | 136k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Graph-Based Bug Tracingtirth8205/code-review-graph | 32k | 1 repos | ~287 | Automated safety check: Pass | MIT |
Similar skills
- Official
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Bug Finder for daisyUI
saadeghi/daisyui
Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.
Root Cause Debugging
garrytan/gstack
Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.
Graph-Based Bug Tracing
tirth8205/code-review-graph
Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.
Om Auto Fix Issue
go-musicfox/go-musicfox
Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain…
More from latitude-dev/latitude-llm
All 28 skills in this repoBetter Auth Best Practices
latitude-dev/latitude-llm
Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables.
Artifact Designer
latitude-dev/latitude-llm
Create, validate, preview, and publish self-contained HTML artifacts.
CI Watchdog
latitude-dev/latitude-llm
Continuously monitor GitHub PR CI checks and automatically fix failures until all checks pass.
Temporal Developer
latitude-dev/latitude-llm
This skill should be used when the user asks to "create a Temporal workflow", "write a Temporal activity", "debug stuck workflow", "fix non-determinism error", "Temporal Python", "Temporal…
Docs
latitude-dev/latitude-llm
Review the current conversation context and git changes, then persist durable repository knowledge into dev-docs/.md by domain and into AGENTS.md for cross-cutting repo rules.
Managing Maintenance Windows
latitude-dev/latitude-llm
Enables or disables Latitude production maintenance mode by redirecting all publicly exposed production services to the Better Stack status page.
Related
Categories
Questions about Analyze Problem
What does Analyze Problem do?
Analyze a problem and provide a detailed explanation of the issue, root cause, proposed fix, and verification steps. Analyze Problem is an agent skill from latitude-dev/latitude-llm. Analyze a problem and provide a detailed explanation of the issue, root cause, proposed fix, and verification steps.
When should I use Analyze Problem?
Analyze Problem fits situations like: tasks that involve Root cause analysis.
How do I install Analyze Problem in Claude Code?
Run `npx skills add latitude-dev/latitude-llm --skill analyze-problem -a claude-code`. Or copy the skill folder (.agents/skills/analyze-problem in latitude-dev/latitude-llm) into .claude/skills/analyze-problem in your project. Claude Code loads it when a task matches its description.
How do I install Analyze Problem in Codex?
Run `npx skills add latitude-dev/latitude-llm --skill analyze-problem -a codex`. Or copy the skill folder (.agents/skills/analyze-problem in latitude-dev/latitude-llm) into .agents/skills/analyze-problem in your project. Codex loads it when a task matches its description.
Can I use Analyze Problem in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add latitude-dev/latitude-llm --skill analyze-problem -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze-problem, .gemini/skills/analyze-problem, .github/skills/analyze-problem and .opencode/skills/analyze-problem in your project.
What does Analyze Problem need to run?
SKILL.md names no scripts, command-line tools or credentials: Analyze Problem is instructions for the agent only.
Does Analyze Problem access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Analyze Problem safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Analyze Problem use?
Analyze Problem is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Analyze Problem use?
About 398 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Analyze Problem?
Skills that share tags, products or a category with Analyze Problem: Code Design Rationale Investigator (cursor/plugins, 10k stars), OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars) and Root Cause Debugging (garrytan/gstack, 136k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analyze Problem?
latitude-dev (a GitHub organization) maintains it in latitude-dev/latitude-llm, which has 4,712 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 6, 2026.
Source: latitude-dev/latitude-llm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.