debugging-checklist

Generate a prioritized debugging checklist for junior developers.

5|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill debugging-checklist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-checklist
Source: https://github.com/lidge-jun/cli-jaw-skills/tree/main/debugging-checklist
Command: npx skills add https://github.com/lidge-jun/cli-jaw-skills --skill debugging-checklist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, step-by-step approach to debugging issues, preventing junior developers from getting stuck and promoting efficient problem-solving.

Core Features & Use Cases

  • Structured Approach: Offers a clear, ordered checklist to follow when encountering a bug.
  • Information Gathering: Guides the user on what essential information to collect for effective debugging.
  • Use Case: A junior developer is facing an intermittent bug in a new feature. They can use this skill to systematically go through potential causes, starting with the most likely and least intrusive checks.

Quick Start

Use the debugging-checklist skill to get a structured approach for troubleshooting.

Frequently Asked Questions about debugging-checklist

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

FAQPage Schema
What is a systematic debugging checklist for problem solving?

A systematic debugging checklist provides a structured, step-by-step approach to troubleshooting issues, guiding junior developers through information gathering and ordered checks to prevent getting stuck and promote efficient problem-solving.

How do I troubleshoot an intermittent bug in a new feature?

Troubleshoot an intermittent bug by using a structured checklist to systematically go through potential causes, starting with reproducing the problem, checking environmental factors, and implementing targeted logging or breakpoints for efficient, low-risk resolution.

What is the best way to resolve issues without causing new bugs?

The best way to resolve issues without causing new bugs is to follow a prioritized list of checks designed for low-risk problem resolution, starting with the most likely and least intrusive debugging steps before making changes.

What essential information do I need to gather for effective debugging?

For effective debugging, you need to gather information by reproducing the problem, checking environmental factors, and implementing targeted logging or breakpoints to systematically identify and isolate the root cause.

Is this systematic debugging approach suitable for junior developers?

Yes, this systematic debugging approach is specifically designed for junior developers encountering issues, offering a clear, ordered checklist that guides information gathering and targeted checks to prevent getting stuck during troubleshooting.