skills.rest
SAZO-KR
SAZO-KROFFICIAL
Explore all skills by this author →
WebsiteGitHub

debug

Reproduce difficult bugs by writing external test scripts that interact with running applications.

Updated Jan 2, 2026
Search Tags:#debugging#logging#iteration#observability#test-scripts#reproducible-bugs#external-testing
One-click install
npx skills add https://github.com/SAZO-KR/sazo-toolkit --skill debug-sazo-kr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/SAZO-KR/sazo-toolkit/tree/main/packages/ai-harness/skills/debug
Command: npx skills add https://github.com/SAZO-KR/sazo-toolkit --skill debug-sazo-kr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging complex applications often requires external interaction, reproducible tests, and structured logging to identify root causes.

Core Features & Use Cases

  • Write and run external debug scripts that interact with the application through its public interfaces only.
  • Iteratively observe logs, reproduce failures, and refine test scripts until the root cause is found.
  • Use structured logging and test artifacts to build a reliable bug repro and verification workflow.

Quick Start

Write an external script that interacts with the application boundary, run it, review logs, and iteratively adjust the script until the bug is reproduced and understood.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I reproduce a difficult bug using external test scripts?▼

You can debug CLI tools, APIs, and services by writing external scripts that steer observable behavior via public interfaces, collecting structured logs, and iterating on test cases to drive diagnosis and verification.

What is the best way to debug an application boundary without internal access?▼

Debugging via external interfaces involves writing scripts that interact with the application boundary, collecting structured logs, and iteratively refining test cases to observe and reproduce failures without needing internal access.

How do I set up an iterative debugging workflow for reproducible bugs?▼

You establish an iterative debugging workflow by writing external scripts that interact with the application boundary, running them, reviewing structured logs, and adjusting the scripts until the reproducible bug is understood and verified with robust cleanup.

Does this external testing approach work for both CLI tools and APIs?▼

Yes, this external testing approach applies across CLI tools, APIs, and services by interacting with the application through its public interfaces where observable behavior can be steered and verified.

Why use structured logging when reproducing failures in a running application?▼

Structured logging is used when reproducing failures to collect test artifacts that build a reliable bug reproduction and verification workflow, enabling you to iteratively observe logs and accurately diagnose the root cause.

What are the limitations of debugging with external test scripts?▼

Debugging with external test scripts is limited to observable behavior via public interfaces, requiring robust cleanup and clear guardrails to safely manage the iterative test case refinement and verification process.

Related Skills

Explore More Software Engineering Skills→
qdzshqdzsh
12

tdd

Automates red-green-refactor cycles for vertical slices with failing tests first.

Community
Advanced
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
nghiahsgsnghiahsgs
32

debug-flight-recorder

Insert marker-based console logs to trace bug execution and revert changes.

Community
Advanced
ForgePlanForgePlan
3

diagnose

Automate bug diagnosis with reproduction, hypothesis testing, and regression testing.

Official
Advanced