debug

Route legacy debug skill references to the canonical implementation.

3|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/ShalomObongo/nanoclaw --skill debug-shalomobongo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/ShalomObongo/nanoclaw/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/ShalomObongo/nanoclaw --skill debug-shalomobongo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy compatibility wrapper that delegates to the canonical debug skill.

Core Features & Use Cases

  • Ensures backward compatibility for legacy skill references by routing to .codex/skills/debug/SKILL.md.
  • Simplifies maintenance by centralizing logic in the canonical skill.
  • Use Case: You have an old workflow that calls .claude/skills/debug; the wrapper automatically executes the canonical implementation.

Quick Start

Invoke the legacy wrapper to execute the canonical debug skill.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I maintain legacy skill references without breaking old workflows?

A legacy compatibility wrapper maintains backward compatibility for old workflows by automatically routing legacy skill references to the canonical implementation, preventing workflow breakage without updating old calls.

What is a compatibility wrapper for legacy debug skills?

A compatibility wrapper is a routing layer that intercepts legacy debug skill references and delegates execution to the canonical debug skill located at .codex/skills/debug/SKILL.md.

Do I need external dependencies to run a legacy debug wrapper?

No external dependencies are required to run the legacy debug wrapper, as it simply forwards commands directly to the canonical implementation without needing additional packages.

How do I route execution from a legacy skill path to a canonical skill?

Invoke the legacy wrapper to automatically route execution from the old skill path to the canonical debug skill, centralizing logic and simplifying maintenance across legacy references.

Can I simplify maintenance by centralizing logic in a canonical debug skill?

Yes, centralizing logic in the canonical debug skill simplifies maintenance because the wrapper delegates all legacy references to a single source of truth.

Does the legacy debug wrapper work with old workflow paths?

Yes, the wrapper works with old workflow paths by catching legacy references and automatically executing the canonical implementation without requiring modifications to existing workflows.