agentsclimarketplace

Debug issue

Skill emaraschio/cursor-commands/plugin/.cursor/skill-contracts/debug-issue

Production-grade Cursor slash commands with paired skill contracts, behavioral evals, and ship-gate CI. Install as a user plugin.

Install
npx -y skills add emaraschio/cursor-commands --skill debug-issue

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

One thing to look at

  • 9 stars9 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

Systematically debug a reported issue

SKILL.md

1.6 KB, 314 tokens by cl100k_base, as published. Nobody here has run it

Overview

Help debug the current issue in the code by walking through the debugging process systematically and providing clear, actionable solutions.

Steps

  1. Problem Analysis
    • Identify the specific problem or error
    • Understand the expected vs actual behavior
    • Trace the execution flow to find the root cause
  2. Debugging Strategy
    • Add appropriate logging statements
    • Suggest debugging tools and techniques
    • Identify key variables and states to monitor
    • Recommend breakpoint locations
  3. Solution Approach
    • Propose potential fixes with explanations
    • Consider multiple solution approaches
    • Evaluate trade-offs of different approaches
    • Provide step-by-step resolution plan
  4. Prevention
    • Suggest ways to prevent similar issues
    • Recommend additional tests or checks
    • Identify code patterns that could be improved

Debug Issue Checklist

  • Identified the specific problem or error
  • Understood expected vs actual behavior
  • Traced execution flow to find root cause
  • Added appropriate logging statements
  • Proposed potential fixes with explanations
  • Evaluated trade-offs of different approaches
  • Provided step-by-step resolution plan
  • Suggested ways to prevent similar issues
  • Recommended additional tests or checks

Guardrails

  • Reproduce and trace to the root cause before changing code.
  • Change only the reported fault; do not touch unrelated code.
  • Do not run destructive or production commands without explicit consent.

Gives 0 of the 12 instructions most debug triage skills give in 314 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07

  • investigate root cause before proposing any fixin 102 of 839, across 67 files
  • read error messages completelyin 89 of 839, across 49 files
  • create a failing test case before fixingin 84 of 839, across 46 files
  • reproduce the issue consistentlyin 82 of 839, across 41 files
  • change one variable at a timein 82 of 839, across 42 files
  • check recent changesin 74 of 839, across 36 files
  • write the regression test before fixingin 74 of 839, across 40 files
  • fix the root cause not the symptomin 60 of 839, across 45 files
  • implement a single fix at a timein 59 of 839, across 20 files
  • trace data flow backward to the sourcein 50 of 839, across 20 files
  • remove all debug instrumentationin 49 of 839, across 13 files
  • form a single hypothesisin 48 of 839, across 18 files

Said here and by no other author read

  • Add appropriate logging statements
  • Propose potential fixes with explanations
  • Evaluate trade-offs of multiple approaches
  • Recommend additional tests or checks

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.