Skip to content
Back to skills

Codex Debug

ASecurity

Use for systematic debugging and root cause analysis with Codex. Triggers on "codex debug", "codex root cause", "have codex investigate this bug", "codex find the issue".

  • 666 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 8, 2026
researchdebuggingperformance

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill codex-debug --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Codex Debug?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Codex Debug
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-codex-debug/badge)](https://www.skillsdirectory.com/skills/majiayu000-codex-debug)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: codex-debug
description: Use for systematic debugging and root cause analysis with Codex. Triggers on "codex debug", "codex root cause", "have codex investigate this bug", "codex find the issue".
---

# Codex Debug Skill

Systematic debugging and root cause analysis with Codex (gpt-5.2).

## When to Use

- Debugging complex bugs
- Finding root causes of issues
- Investigating mysterious errors
- Performance issue diagnosis
- Race conditions or timing issues

## Reasoning Level

**xhigh** (debugging requires deep analysis)

## Execution

1. Gather all relevant information:
   - Error messages
   - Stack traces
   - Relevant code files
   - Reproduction steps
2. Formulate a debugging prompt:
   ```
   Debug this issue systematically.

   Issue: <description>

   Error/Symptoms:
   <error messages, behavior>

   Relevant Code:
   <file contents>

   Please:
   1. Identify possible causes
   2. Analyze each potential root cause
   3. Determine the most likely cause
   4. Suggest a fix
   ```
3. Run: `codex exec -c model_reasoning_effort="xhigh" "<prompt>"`
4. Return the debugging analysis with fix recommendation

## Response Format

```
**Codex Debug Analysis:**

**Issue Summary:**
[What's happening]

**Root Cause Investigation:**
[Step-by-step analysis of potential causes]

**Most Likely Cause:**
[Primary hypothesis with evidence]

**Recommended Fix:**
[Specific fix with code if applicable]

**Session ID:** [id]
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.