agentleFS
Sign inStart free
emaraschioemaraschio/cursor-commands/.cursor/skill-contracts/debug-issue/SKILL.md

debug-issue

Skill9 starsChanged 3 months agoMITView on GitHub

Systematically debug a reported issue

17 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use explore-codebase, refactor-safely and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • srclightSkill

    explore-codebase

    This skill should be used when the user asks to "explore this codebase", "understand this project", "give me an overview", "how does this work", "onboard me", "walk me through the architecture", "map the codebase", or any request to understand a codebase's structure, architecture, or design.

    Also in 5 projects that use this

  • srclightSkill

    refactor-safely

    This skill should be used when the user asks to "refactor", "rename", "move", "change a function signature", "extract a method", "delete unused code", "clean up", or any modification that could break callers or dependents. Provides a pre-change safety checklist using srclight's graph tools to assess blast radius before touching code.

    Also in 5 projects that use this

  • DockerSkill

    review-changes

    Review uncommitted or recently committed documentation changes for correctness, coherence, and style compliance. Use before creating a PR to catch issues. "review my changes", "review the diff", "check the fix before submitting", "does this look right".

    Also in 4 projects that use this

  • xfstudioSkill

    reverse-engineer

    Expert reverse engineer specializing in binary analysis,

    Also in 3 projects that use this

  • SentrySkill

    create-pr

    Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.

    Also in 4 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add appropriate logging statements

    line 17
  2. Distinctive:

    Consider multiple solution approaches

    line 23
  3. Distinctive:

    Do not run destructive or production commands without explicit consent.

    line 47

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free