ze-debug

Diagnose failing Ze repository tests and implement the smallest correct fix.

50|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/ze-software/ze --skill ze-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ze-debug
Source: https://github.com/ze-software/ze/tree/main/.codex/skills/ze-debug
Command: npx skills add https://github.com/ze-software/ze --skill ze-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers diagnose and fix failing tests in the Ze repository by guiding a structured, hypothesis-driven debugging workflow from initial failure output to a verified fix.

Core Features & Use Cases

  • Guided test-failure analysis: starts from the failing output, reads relevant code and tests, and formulates concrete hypotheses.
  • Smallest fix first: identifies the minimal change that resolves the failure and validates it with focused tests.
  • Verification workflow: re-runs unit, lint, and functional tests to confirm the fix and prevent regressions.

Quick Start

Provide the failing test output and I will guide you through isolating the cause and applying the smallest correct fix.

Frequently Asked Questions about ze-debug

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

FAQPage Schema
How do I debug failing unit tests in a CI pipeline?▼

Debug failing unit tests by providing the failing CI output to initiate a structured, hypothesis-driven investigation that reads relevant code paths and isolates the root cause. This workflow guides you from the initial failure output directly to a verified fix.

What is the best way to find the root cause of a flaky test regression?▼

Root cause analysis for a flaky test regression involves formulating concrete hypotheses based on failing outputs and reading the affected code paths. A structured investigation isolates the exact failure trigger before proposing any code modifications.

How do I fix test failures using the smallest correct change?▼

Fix test failures using the smallest correct change by identifying the minimal code modification that resolves the specific failure. Validate this minimal fix by re-running targeted unit tests before executing a full test suite to prevent regressions.

Can I use a hypothesis-driven workflow to resolve CI test failures?▼

You can use a hypothesis-driven workflow to resolve CI test failures by analyzing the failing output, reading the relevant tests, and formulating concrete hypotheses. This process systematically narrows down potential causes to implement a targeted fix.

How do I verify a test fix and prevent future unit test regressions?▼

Verify a test fix and prevent future unit test regressions by re-running unit, lint, and functional test suites after applying the change. This comprehensive verification workflow confirms the fix resolves the failure without introducing new issues.