skills.rest
tfunk1030
tfunk1030COMMUNITY
Explore all skills by this author →
GitHub

debug

Identify software issue root causes by analyzing logs, database state, and git history.

1|Updated Jan 2, 2026
Search Tags:#git#debugging#troubleshooting#database#logs#devtools#incident-response
One-click install
npx skills add https://github.com/tfunk1030/vibe --skill debug-tfunk1030
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/tfunk1030/vibe/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/tfunk1030/vibe --skill debug-tfunk1030

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debug tasks by quickly identifying root causes of issues through inspection of logs, database state, and git history, without requiring code edits.

Core Features & Use Cases

  • Inspect application logs to surface errors and warnings with context
  • Query and inspect database state to verify data integrity and track recent changes
  • Review git history, current branch, and recent commits to understand regression risks
  • Provide a guided, step-by-step debugging plan for incident response and manual testing

Quick Start

Describe your issue and I will start a guided debugging session by examining logs, DB state, and git history.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I trace software issues by analyzing logs, database state, and git history?▼

To trace software issues, this Skill coordinates a read-only exploration flow that inspects application logs, queries database state, and reviews git history to identify root causes without editing code.

What is the best way to debug incident response issues locally and in CI environments?▼

For debugging incident response issues, it provides a guided step-by-step plan that retrieves logs, checks database integrity, and reviews recent commits across local development and CI environments.

Can I identify regression risks by checking git history and database state during troubleshooting?▼

Yes, you can identify regression risks during troubleshooting by reviewing current branch changes and recent commits in git history alongside verifying data integrity by querying database state.

Does this debugging approach modify code or require edits to inspect application logs and errors?▼

No, this debugging approach is strictly read-only and does not modify code, applying a guided exploration flow to surface errors and warnings from logs without requiring any code edits.

How do I start a guided debugging session for QA checks and manual testing?▼

To start a guided debugging session for QA checks and manual testing, describe your issue and the Skill will coordinate log retrieval, DB queries, and git state checks to locate the root cause.

Related Skills

Explore More Software Engineering Skills→
enowdevenowdev
13

stripe-dispute

Collect Stripe dispute evidence and generate counter-dispute rebuttal packages.

Community
Advanced
tabgabtabgab

opp-repl-troubleshooting

Map opp_repl error messages to root causes and remedies for OMNeT++ simulations.

Community
Advanced
NagyViktNagyVikt
2

observability

Configure structured logging, tracing, and performance monitoring for Vercel-hosted applications.

Community
Advanced
giosuetedeschi-specgiosuetedeschi-spec

Wireshark Network Traffic Analysis

Capture, filter, and examine packets in PCAP files to identify security threats.

Community
Advanced