Debug issue

Skill JoaoAlavarse/cursor-config/skills/debug-issue

Configuração global do Cursor: user rules, agent skills, slash commands e hooks com scripts de instalação.

Install

npx -y skills add JoaoAlavarse/cursor-config --skill debug-issue

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

15 days oldThe repository was created 15 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Investigates bugs, failures or unexpected behavior by identifying the root cause before proposing or implementing a fix. Use when debugging errors, test failures, or unexpected behavior.

SKILL.md

2.7 KB, as published. Nobody here has run it

Objective

Investigate bugs, failures and unexpected behavior to identify the root cause before proposing or implementing a solution.

Focus on understanding why the issue occurs rather than immediately attempting to fix it.

Context

Before debugging:

If project rules are available, read and follow them.
Otherwise, infer the project's conventions from the existing codebase.
Respect the project's architecture, coding patterns, conventions and documented design decisions.
Do not assume the project follows current best practices.
Prefer explanations supported by evidence over intuition.

Investigation Process

Understand the reported issue.
Identify the expected behavior.
Identify the actual behavior.
Gather available evidence, including logs, stack traces, error messages and relevant code.
Trace the execution path that leads to the failure.
Identify possible root causes.
Eliminate hypotheses that are inconsistent with the available evidence.
Determine the most likely root cause.
Assess the impact and scope of the issue.

Do not assume the first plausible explanation is correct.

Investigation Guidelines

Base conclusions on observable evidence whenever possible.

Clearly distinguish facts, assumptions and hypotheses.

State uncertainty when evidence is insufficient.

Avoid speculative explanations.

Consider recent changes that may have introduced the issue.

Look for environmental, configuration, dependency and data-related causes in addition to code defects.

Prefer identifying the root cause over treating symptoms.

Continue investigating while multiple plausible root causes remain supported by the available evidence.

Recommend the smallest change that fully resolves the underlying problem.

Do not generate implementation code unless explicitly requested.

Output

Issue Summary

Briefly describe the reported problem.

Expected Behavior

Describe what should happen.

Actual Behavior

Describe what actually happens.

Evidence

Summarize the relevant evidence collected during the investigation.

Root Cause Analysis

Explain the reasoning that led to the identified root cause.

If the cause cannot be determined with confidence, explain why.

Recommended Fix

Describe the recommended solution without providing implementation code.

Risks

Identify potential side effects or related areas that should be validated.

Validation

Describe how to verify that the issue has been resolved.