debug

Analyze logs, database state, and git history to identify root causes.

3|Updated Feb 20, 2026

Search Tags:#git #investigation #troubleshooting #database #logs #debug #root-cause

Ready to run

npx skills add https://github.com/theomonfort/theomonfort --skill debug-theomonfort

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/theomonfort/theomonfort/tree/main/.github/skills/debug
Command: npx skills add https://github.com/theomonfort/theomonfort --skill debug-theomonfort

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps debug issues during manual testing or implementation by examining logs, database state, code, and git history without editing files.

Core Features & Use Cases

Investigate recent logs: Find errors and warnings around the issue timeframe.
Check database state: Inspect schema, data integrity, and anomalies.
Review code and git history: See recent changes, branches, and commits to identify potential causes.
Coordinated investigation workflow: Spawn parallel tasks to examine logs, DB, and git state for faster root-cause analysis.

Quick Start

Describe the problem in detail and I will begin by inspecting logs, database, and recent git changes to identify the root cause.

Frequently Asked Questions about debug

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

FAQPage Schema

How do I investigate the root cause of an error during manual testing?▼

To investigate the root cause during manual testing, you can analyze recent logs, database state, and git history without editing files. Providing contextual data like current branch and recent commits enables actionable guidance for diagnosing the issue.

What is the best way to troubleshoot issues by analyzing logs and database state?▼

Troubleshooting issues by analyzing logs and database state involves inspecting schema, data integrity, and recent errors around the issue timeframe. Coordinated parallel tasks can examine logs, DB, and git state to accelerate root-cause identification.

Can I check recent git commits and code changes to identify potential causes of a bug?▼

Yes, you can identify potential causes of a bug by reviewing recent git commits, branches, and code changes. Examining this history alongside logs and database anomalies helps pinpoint the exact root cause without modifying any files.

Do I need to provide ticket details and current branch information to debug an issue?▼

Yes, providing contextual data such as plan or ticket details, current branch, and recent commits is required to debug an issue effectively. This context allows the investigation to deliver actionable root-cause guidance across logs, DB, and git history.

Does this debugging approach modify my code or database files during the investigation?▼

No, this debugging approach does not modify your code or database files during the investigation. It strictly examines logs, database state, code, and git history in a read-only manner to identify the root cause safely.

How do I inspect database anomalies and schema integrity when diagnosing a problem?▼

To inspect database anomalies and schema integrity when diagnosing a problem, you analyze the database state alongside recent logs and git changes. This coordinated workflow spawns parallel tasks to examine logs and DB for faster root-cause analysis.