Analyze logs, database state, and git history to identify root causes.
npx skills add https://github.com/theomonfort/theomonfort --skill debug-theomonfort
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
This skill helps debug issues during manual testing or implementation by examining logs, database state, code, and git history without editing files.
Describe the problem in detail and I will begin by inspecting logs, database, and recent git changes to identify the root cause.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
mostafa-drzAggregate git history, branch state, and Linear ticket context into a markdown briefing.
gtheysInvestigate minikube pod logs, PostgreSQL nonprod state, and git history.
allexcdDiagnose, reproduce, and fix code defects from bug reports or error logs.
tfunk1030Identify software issue root causes by analyzing logs, database state, and git history.
