skill CX Codex

debug · ldayton — Claude Code skill: what it does, how to install

Q: How do I install debug in Claude Code?

Run `npx skills add ldayton/Dippy --skill debug -a claude-code`. The skill file is available at `~/.claude/skills/debug/SKILL.md`.

Q: Which checks does debug run?

It uses `just test` to confirm the new test catches the bug, then reruns the tests after the fix. It also formats and checks the code, and requires `just check` to pass.

This skill investigates cases where Dippy approves or blocks a command incorrectly, then guides the agent through a test-led fix.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓

npx skills add ldayton/Dippy --skill debug -a claude-code

Open on GitHub

What debug does

Give the agent the command Dippy handled incorrectly, the expected and actual results, and any relevant logs or error messages. The skill directs it to locate the related handler or pattern and create a test that reproduces the problem before changing the code.

The agent runs just test, makes a targeted fix, and reruns the tests. After they pass, it runs uv run ruff check --fix && uv run ruff format; just check must also pass before the work is done. Changes must stay limited to files tied to the bug. Refactoring unrelated code and creating a commit or PR are off limits. This workflow is for Dippy behavior bugs, not unrelated failures.

What it helps with

trace a command that Dippy approved incorrectly
reproduce a faulty decision with a failing test
fix a command that Dippy blocks by mistake
check the fix with tests and just check

Example prompts for the agent

Investigate why Dippy approved this command; here are the expected result, what happened, and the logs.
Find why Dippy blocks this command, write a failing test first, then fix the bug.
Check this Dippy decision: the command should be blocked, but it currently goes through.

How to install debug

1Skills CLI (Vercel)

npx skills add ldayton/Dippy --skill debug -a claude-code

2Manually: put the files in place

~/.claude/skills/debug/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/debug/

1Skills CLI (Vercel)

npx skills add ldayton/Dippy --skill debug -a codex

2Manually: put the files in place

.agents/skills/debug/SKILL.md

For all projects use ~/.agents/skills/

1Skills CLI (Vercel)

npx skills add ldayton/Dippy --skill debug -a cursor

2Manually: put the files in place

.cursor/skills/debug/SKILL.md

Cursor also reads .agents/skills/ and .claude/skills/

1GitHub CLI

gh skill install ldayton/Dippy debug

2Manually: put the files in place

.github/skills/debug/SKILL.md

1Skills CLI (Vercel)

npx skills add ldayton/Dippy --skill debug -a gemini-cli

2Platform CLI

gemini skills install https://github.com/ldayton/Dippy --path .claude/skills/debug

Manually: put the files in place

.devin/skills/debug/SKILL.md

The legacy .windsurf/skills/ path still works

Skills CLI (Vercel)

npx skills add ldayton/Dippy --skill debug -a opencode

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about debug

How do I install debug in Claude Code?

Run npx skills add ldayton/Dippy --skill debug -a claude-code. The skill file is available at ~/.claude/skills/debug/SKILL.md.

What does the debug skill do?

It investigates incorrect command approvals or blocks in Dippy, locates the relevant code, and guides a test-first fix.

Which checks does debug run?

It uses just test to confirm the new test catches the bug, then reruns the tests after the fix. It also formats and checks the code, and requires just check to pass.

Source text

SKILL.md · MIT

---
name: debug
description: Debug incorrect Dippy approval or block behavior
disable-model-invocation: true
---

Debug a Dippy issue based on user-provided context.

The user will provide:
- The command that was incorrectly approved or blocked
- Expected vs actual behavior
- Any relevant error messages or logs

## Process

1. Understand the bug from the provided context
2. Search the codebase to find the relevant handler or pattern
3. Write a failing test FIRST in the appropriate test file
4. Run `just test` and verify the test fails as expected
5. Fix the bug in the handler or pattern
6. Run `just test` until the test passes

## Finish

When tests pass:
```
uv run ruff check --fix && uv run ruff format
```

`just check` MUST pass before you're done.

## Restrictions

- ONLY modify files directly related to the bug
- Make minimal, targeted fixes
- Do NOT refactor or "improve" unrelated code
- Do NOT create a git commit or PR

debug by other authors comes first.

debug official anthropics This skill takes a bug from reproduction to root cause, a fix, and regression coverage. Use it when the symptom is clear but the cause is not. CX Codex +1 5,900installs debug Yeachan-Heo Diagnoses broken OMC sessions, workflow failures, and repo state issues using traces and targeted reproduction. CX Codex +1 639installs debug jsmastery-pro Runs a structured investigation loop to find a bug's root cause, applies the minimal fix, and prepares a regression test. CX Codex +1 4,400installs debug parcadei Investigates application logs, SQLite database state, and git history without editing source files. Useful for pinpointing issues during manual testing. CX Codex +1 507installs debug cyrusagents Works through a reported bug from reproduction to a minimal fix. Use it when you need to trace an error and verify the result. CX Codex +1 826installs improve-codebase-architecture Matt Pocock This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review. 1,163,035installs tdd Matt Pocock Guides the red-green TDD loop: ensures tests are written first, keep them at public interfaces, and avoid coupling to implementation details. 1,141,062installs triage Matt Pocock This skill moves issues and external PRs through triage states, verification, and agent briefs. It fits maintainers managing an issue queue. 990,453installs codebase-design Matt Pocock This skill helps design modules with small interfaces and hidden complexity. Use it when refactoring code, choosing a seam, or making tests easier to write. 850,344installs code-review Matt Pocock Reviews changes from a chosen reference point against repository standards and the originating spec. Use it for a branch, PR, or work in progress. 789,521installs implement Matt Pocock Implements work from a specification or tickets, following a test-driven flow and ending with review and a commit. Use it when a coding task needs a defined delivery routine. 774,700installs

From the same set5

verify-counts This skill compares numeric claims in documentation against the real values and flags the outdated ones. Handy when a README still promises 14,000+ tests. CX Codex +1 ★ 242repo stars release Prepares a release pull request with version bumps, dependency sync, and user-facing release notes. Helpful for structured project publishing. CX Codex +1 ★ 242repo stars check-coverage This skill inspects a CLI handler and its test file, spots the gaps and writes the missing cases. Handy when you add a command or audit old coverage. CX Codex +1 ★ 242repo stars add-command Guides the step-by-step addition of new CLI commands into Dippy. It separates read-only tools from subcommands that require custom flag parsing. CX Codex +1 ★ 242repo stars