skills.rest
gil-kapel
gil-kapelCOMMUNITY
Explore all skills by this author →
GitHub

debug

Collects logs, environment details, and code changes to diagnose issues during manual testing or implementation scenarios.

2|1|Updated Apr 1, 2026
Search Tags:#git#debugging#logs#environment#issue resolution
One-click install
npx skills add https://github.com/gil-kapel/cursor-course-2026 --skill debug-gil-kapel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/gil-kapel/cursor-course-2026/tree/main/course/he_course/module-02-skills-and-agents/lesson-2.12-debug-agent/bundled-skills/_to-improve/debug
Command: npx skills add https://github.com/gil-kapel/cursor-course-2026 --skill debug-gil-kapel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Troubleshooting technical issues can be time-consuming and complex, requiring gathering detailed error reports, logs, environment data, and recent code changes to identify root causes.

Core Features & Use Cases

  • Evidence Ritual: Guides users in collecting full error traces, logs, environment details, and repro steps for accurate diagnostics.
  • Investigative Workflow: Provides structured steps to analyze logs, database states, and recent git changes.
  • Use Case: During manual testing, a developer encounters a bug; this Skill assists in systematically gathering and analyzing data to resolve the issue efficiently.

Quick Start

When a problem occurs, describe the issue clearly, then ask the AI for step-by-step investigation guidance to identify root causes.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I collect the right logs and environment details for issue resolution?▼

Effective issue resolution requires gathering full error traces, environment details, and repro steps. This Skill guides you through an evidence ritual to systematically collect logs and code changes for accurate diagnostics.

What is the best way to analyze recent git changes to find a bug?▼

Analyzing recent git changes is best handled through a structured investigative workflow. This Skill provides step-by-step guidance to correlate logs and database states with your recent code modifications to identify root causes.

Can I use this for troubleshooting issues found during manual testing?▼

Yes, you can use this for troubleshooting during manual testing. When you encounter a bug, it assists by systematically gathering and analyzing error traces and environment data to help you resolve the issue efficiently.

How do I systematically debug a problem when I only have a vague error description?▼

To debug a vague error, you should first describe the issue clearly, then ask for step-by-step investigation guidance. This Skill facilitates debugging by structuring your data collection to pinpoint root causes accurately.

What limitations exist when debugging with only logs and git changes?▼

Debugging with only logs and git changes may not reveal issues hidden in runtime database states or environment configurations. This Skill mitigates limitations by enforcing an evidence ritual that collects environment details and repro steps alongside logs.

Related Skills

Explore More Software Engineering Skills→
nsuberinsuberi

tech-diagnosis-exercise

Generate interactive diagnostic exercises from git commit pairs and problem descriptions.

Community
Advanced
dmae97dmae97
130

omk-flow-bugfix

Guide bug resolution from reproduction evidence to root-cause analysis and minimal code changes.

Community
Intermediate
dadbodgeoffdadbodgeoff
783

logging-observability

Implement structured JSON logging with correlation IDs for Python and TypeScript applications.

Community
Advanced
FrekiManagarmFrekiManagarm

error-tracking-node

Configure PostHog exception tracking for Node.js applications with source maps.

Community
Intermediate