Debug

Analyze application logs, SQLite databases, and git history to diagnose software issues.

8|1|Updated Jan 4, 2026

Search Tags:#git #testing #troubleshooting #database #logs #debug

Ready to run

npx skills add https://github.com/scooter-lacroix/Maestro --skill debug-scooter-lacroix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Debug
Source: https://github.com/scooter-lacroix/Maestro/tree/main/maestro/skills/meta/debug
Command: npx skills add https://github.com/scooter-lacroix/Maestro --skill debug-scooter-lacroix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose and understand issues encountered during manual testing or implementation by investigating logs, database state, and git history without altering files.

Core Features & Use Cases

Log Analysis: Quickly scan recent application logs for errors and warnings.
Database State Check: Inspect SQLite database contents to identify anomalies or incorrect states.
Git History Review: Examine recent commits and file status to understand changes related to an issue.
Use Case: You're testing a new feature and it crashes unexpectedly. This Skill can help you pinpoint the error by looking at the logs generated just before the crash, checking if a recent database entry is corrupted, or if a recent code commit introduced the bug.

Quick Start

Use the debug skill to investigate the current issue by examining logs, database, and git state.

Frequently Asked Questions about Debug

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

FAQPage Schema

How do I debug application errors using logs and git history?▼

Debug application crashes by scanning recent application logs for errors, inspecting SQLite database entries for corrupted state, and reviewing recent git commits to pinpoint the code changes that introduced the bug.

Can I inspect SQLite database state to troubleshoot software issues?▼

Yes, you can inspect SQLite database contents to troubleshoot software issues by identifying incorrect states or data anomalies without altering the database files during your testing or implementation phase.

Does this debugging approach work with manual testing workflows?▼

Yes, this debugging approach supports manual testing workflows by investigating errors, system states, and recent code changes encountered during testing without modifying the underlying application or database files.

What is the best way to find a bug introduced by a recent code commit?▼

Find a recently introduced bug by examining recent git commits and file status, then cross-referencing those code changes with application errors found in logs and database anomalies to isolate the root cause.

Do I need access to log files and git repositories to diagnose issues?▼

Yes, you need access to application log files, SQLite databases, and git repositories to perform comprehensive issue diagnosis and understand system states and recent code changes.