skills.rest
ARAVINDAN20
ARAVINDAN20COMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-debugging

Diagnose and fix syntax, runtime, and logical errors in experimental code.

4|1|Updated Apr 8, 2026
Search Tags:#debugging#reflection#root-cause#retry#error-analysis#state-machine#code-fix
One-click install
npx skills add https://github.com/ARAVINDAN20/Claude-Research-Paper-OS --skill code-debugging-aravindan20
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-debugging
Source: https://github.com/ARAVINDAN20/Claude-Research-Paper-OS/tree/main/.claude/skills/agent-research-skills/skills/code-debugging
Command: npx skills add https://github.com/ARAVINDAN20/Claude-Research-Paper-OS --skill code-debugging-aravindan20

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Debug experiment code with structured error analysis and targeted fixes, reducing iteration time and recurring issues.

Core Features & Use Cases

  • Error categorization and root-cause analysis to identify exact failure modes (syntax, runtime, logical).
  • Fix strategy with retries and a reflection step to prevent recurrence across runs.
  • State-machine workflow guiding step-by-step debugging from diagnosis to verification.

Quick Start

Provide the error message and optional code snippet to the code-debugging skill to start the structured debugging workflow.

Frequently Asked Questions about code-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug experimental code errors using structured root-cause analysis?▼

Debug experimental code by categorizing syntax, runtime, or logical failures, performing root-cause analysis, and applying a fix-strategy state machine to resolve errors. This structured approach identifies exact failure modes and reduces iteration time.

What is the best way to stop recurring runtime errors in research experiment code?▼

Stopping recurring runtime errors involves applying retry logic during fix execution and a post-fix reflection checklist after resolution. This reflection step prevents the same failure modes from appearing across subsequent experiment runs.

How do I fix logical failures in experiment code without causing new issues?▼

Fix logical failures by following a state-machine workflow that guides step-by-step debugging from initial diagnosis to final verification. This structured workflow applies targeted fix strategies with retries to ensure the logical error is fully resolved.

Can I diagnose syntax errors in research code using a state-machine debugging workflow?▼

Diagnosing syntax errors in research code is supported through a structured state-machine workflow. The process categorizes the syntax failure, analyzes the root cause, applies a targeted fix, and verifies the resolution to prevent recurrence.

What do I need to start structured error analysis on my experiment code?▼

Starting structured error analysis requires providing the error message and an optional code snippet. This input triggers the debugging workflow, which then categorizes the failure mode and initiates root-cause analysis for targeted fixes.

Related Skills

Explore More Software Engineering Skills→
djpTester44djpTester44

root-cause-analyst

Analyzes error messages and stack traces to isolate root causes of software failures.

Community
Advanced
d-o-hubd-o-hub
11

test-runner

Run Rust unit, integration, and doc tests with cargo test.

Community
Intermediate
TabithaFannyTabithaFanny

experiment-queue

Automate scheduling and execution of machine learning experiments on SSH remote GPUs.

Community
Advanced
zinohomezinohome
1

test-reporting-triage-skill

Categorize test failures and suggest owners from error messages.

Community
Advanced