Debugging Code

Use for debugger-driven runtime root-cause analysis in Rider-supported solutions and projects, including .NET/C#, F#, VB, C++, Unity, Unreal Engine, and other GameDev or mixed-language projects. Trigger when runtime state or control-flow evidence is needed — actual values, branch taken, call order, thread context, whether execution reaches a chosen line — and cannot be derived confidently from source or logs; when pinning the relevant path would otherwise mean reading many files or tracing a deep call chain; or on an explicit request to debug, set breakpoints, step, or inspect runtime values.

398 stars 35 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add JetBrains/skills --skill debugging-code
Manual install
git clone --depth 1 https://github.com/JetBrains/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/debugging-code ~/.claude/skills/debugging-code

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Code Debugging

Debugger-first runtime root-cause analysis for solutions opened in Rider, including C#, C++, F#, VB, Unreal Engine, and other GameDev projects.

Invoke every tool through `execute_tool(command="<tool> --arg value ...")`. Do not call the underlying handles directly. Read `reference/tools.md` only for the specific tool you are about to call; do not pre-load the whole tree.

## Goal
Use debugger evidence to answer concrete runtime questions when static code reading is not enough, or to confirm ideas or results from static analysis — including whether execution reaches or does not reach an agent-selected code location via a breakpoint or tracepoint.

## When To Use This Skill
Use this skill when at least one of the following is true:
- runtime state or control-flow evidence is needed (actual values, branch taken, call order, thread context, or whether execution reaches a chosen location), and it cannot be derived confidently from source/logs;
- finding the relevant path would otherwise require reading many files or tracing a long call chain manually;
- the user explicitly asks to use the debugger (breakpoints, stepping, inspect values, debugger session).

If the user manually activates or refers to this skill, treat that as an explicit request to launch and use the debugger when the required tools are available; do not reduce it to a conceptual discussion.

Skip the debugger when any of these holds (use static analysis or log inspection):
Read the full skill on GitHub

Details

Skill name
debugging-code
Path
debugging-code/SKILL.md
Repo updated
21 October 2026

FAQ

What does the Debugging Code skill do?

Use for debugger-driven runtime root-cause analysis in Rider-supported solutions and projects, including .NET/C#, F#, VB, C++, Unity, Unreal Engine, and other GameDev or mixed-language projects. Trigger when runtime state or control-flow evidence is needed — actual values, branch taken, call order, thread context, whether execution reaches a chosen line — and cannot be derived confidently from source or logs; when pinning the relevant path would otherwise mean reading many files or tracing a deep call chain; or on an explicit request to debug, set breakpoints, step, or inspect runtime values.

How do I install the Debugging Code skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add JetBrains/skills --skill debugging-code. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Debugging Code popular?

It lives in JetBrains/skills, which has 398 GitHub stars and 35 forks.

Related skills

Deploy to Vercel

398

JetBrains/skills

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

DevOps & CloudIn 2 lists35

Vercel React Native Skills

398

JetBrains/skills

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

Mobile DevelopmentIn 2 lists35

Vitest

398

JetBrains/skills

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

Testing & QA35

Domain Decomposition API Design Advisor

398

JetBrains/skills

Decompose business scope into bounded contexts, module or service boundaries, workflows, and API contracts before implementation begins. Use when shaping a new feature, service, or major redesign; when requirements are underspecified; when consistency, idempotency, and integration boundaries must be made explicit; or when ADR-quality tradeoff reasoning is needed for Kotlin plus Spring systems.

Software Development35

Cricket Data

271

machina-sports/sports-skills

Cricket data via ESPN public endpoints and Cricsheet open data — live-ish series scoreboards, standings, match summaries and news (ESPN), plus historical ball-by-ball, player stats, and player registry (Cricsheet, ODC-BY 1.0). Zero config, no API keys. Use when: user asks about cricket scores, IPL/BBL/PSL/international series, points tables, match details, cricket news, ball-by-ball history, or player career stats. Don't use when: user asks about other sports — use football-data (soccer), nfl-data (NFL), nba-data (NBA), wnba-data (WNBA), nhl-data (NHL), mlb-data (MLB), tennis-data (tennis), go

Software Development39

Espn API

271

machina-sports/sports-skills

Raw reference for ESPN's undocumented public JSON endpoints, for a league or operation that no dedicated sports-skills skill covers, or when a developer explicitly asks for raw ESPN endpoints. Prompt-only: endpoint catalog, league slugs, response shapes, pitfalls, fetch helpers. Output is provider-native ESPN JSON, not normalized or canonical. Use when: no dedicated skill covers the league or operation (e.g. MMA, rugby, NCAA volleyball), or the user explicitly asks to write, debug, or inspect ESPN endpoint code. Don't use when: a dedicated skill covers it — nba-data, wnba-data, nfl-data, nhl-d

Software Development39

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.