debug

Name: debug
Availability: InStock
Author: ogallotti

Investigate landing page issues by collecting symptoms and testing hypotheses.

1|Updated Apr 6, 2026

Search Tags:#investigation #troubleshooting #qa #debug #web-development #hypotheses #landing-page

Ready to run

npx skills add https://github.com/ogallotti/metodo-zero --skill debug-ogallotti

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables a systematic approach to debugging landing pages by guiding the user to collect symptoms, form hypotheses, test ideas, and implement fixes, reducing guesswork and accelerating resolution.

Core Features & Use Cases

Structured Investigative Steps: Collect symptoms, verify assumptions, test hypotheses, and confirm fixes with clear evidence.
Documentation & Prevention: Deliver a root-cause explanation and preventive actions to avoid recurrence across future releases.
Use Case: A developer or QA engineer encounters a mobile rendering issue and uses the investigative sequence to identify a DOM/CSS problem and implement a fix.

Quick Start

Start by describing the observed symptom and the environment, then follow the documented investigative steps to identify and resolve the issue.

Frequently Asked Questions about debug

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

FAQPage Schema

What is the best way to systematically debug landing-page issues?▼

Debugging landing-page visual inconsistencies involves collecting symptoms, verifying assumptions, testing hypotheses, and implementing fixes with documented evidence to ensure accurate root-cause resolution.

How do I troubleshoot a mobile rendering issue on my web page?▼

To troubleshoot a mobile rendering issue, start by describing the observed symptom and environment, then follow the investigative sequence to identify the DOM or CSS problem and implement a fix.

Can I use a structured investigation process for performance problems?▼

Yes, a structured investigation process applies to landing-page performance problems by guiding you to gather logs, reproduce errors, test hypotheses, and implement a documented fix.

Does this debugging approach help prevent future landing-page issues?▼

Yes, this debugging approach delivers a root-cause explanation and documents preventive actions to avoid recurrence of landing-page issues across future releases.

How do I investigate visual inconsistencies across different browsers?▼

Investigating visual inconsistencies across browsers requires collecting symptom data, forming and testing hypotheses systematically, and delivering a documented fix along with prevention steps.