OpenParable
Skip to content
← Back to skills

Analyze Problem

Testing & Quality
analyze-problem

Analyze Problem is an Agent Skill for testing & quality published in the latitude-dev/latitude-llm repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Analyze a problem and provide a detailed explanation of the issue, root cause, proposed fix, and verification steps.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/latitude-dev/latitude-llm/blob/HEAD/.agents/skills/analyze-problem/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/analyze-problem, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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:

  1. What you believe the issue is (observable behavior + when it happens),
  2. Why you believe it is happening (root cause and the specific assumption/logic that breaks),
  3. How you would fix it (proposed approach and what behavior/logic should change),
  4. 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.