Skip to main content
affpapa.org
RU EN
skill CX Codex

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

Works through a reported bug from reproduction to a minimal fix. Use it when you need to trace an error and verify the result.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add cyrusagents/cyrus --skill debug -a claude-code
Open on GitHub

What debug does

This skill takes a bug report from symptoms and error messages to the source of failure. It searches the codebase for occurrence patterns, follows data flow, checks edge cases, and reproduces the issue with the smallest useful check: a command, dry run, manual flow, or automated test. It records the cause and reproduction steps.

It then plans a fix against similar changes in the repository and changes only affected code paths. The skill repeats the reproduction and runs relevant existing checks. A new test file is not mandatory; it adds a regression test when the specific failure needs durable coverage, so unrelated cleanup stays out of the patch.

What it helps with

  • reproduce a reported error with a focused check
  • trace an error from symptom to source
  • find a root cause through data flow analysis
  • verify a targeted fix against the original failure

Example prompts for the agent

  • Debug the failure in checkout, reproduce it, and identify the root cause.
  • Use the debug workflow for this error report, then make the smallest fix and verify it.
  • Trace why this error message appears without making unrelated changes.

How to install debug

1Skills CLI (Vercel)

npx skills add cyrusagents/cyrus --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/

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 cyrusagents/cyrus --skill debug -a claude-code, then run npx skills add cyrusagents/cyrus --skill debug -a claude-code again. The skill file is at ~/.claude/skills/debug/SKILL.md.

What does debug do?

The skill investigates a bug report, reproduces the failure, identifies its root cause, and applies a minimal fix. It then repeats the reproduction and runs relevant existing checks.

Does debug always add a regression test?

No. A new test file is not mandatory; the skill adds a regression test when the concrete failure warrants durable coverage.

Source text

SKILL.md · Apache-2.0 
---
name: debug
description: Full debugging workflow — reproduce the bug with a focused check, perform root cause analysis, then implement a minimal fix.
---

# Debug

Debug a reported issue using a structured reproduction-then-fix approach.

## Phase 1: Reproduction & Root Cause Analysis

1. **Investigate** — Analyze the bug report for key symptoms and error messages
2. **Trace** — Search the codebase for error occurrence patterns, trace from symptom to source
3. **Root cause** — Identify the root cause through data flow analysis and edge case checking
4. **Reproduce** — Reproduce the exact error with the smallest useful check (a command, dry run, manual flow, or automated test)
5. **Document** — Clearly document the root cause and reproduction steps

## Phase 2: Fix Implementation

1. **Plan** — Analyze the optimal fix approach based on root cause, check for similar fixes in the codebase
2. **Implement** — Make the minimal, targeted fix that addresses the root cause
3. **Verify** — Repeat the reproduction to confirm the fix and run relevant existing checks. Follow `verify-and-ship` for proportionate scope; add a regression test only when the concrete failure warrants durable coverage

## Principles

- **Minimal changes** — Fix the bug, nothing more
- **Targeted** — Only touch affected code paths
- **Verified** — Confirm the reproduction succeeds after the fix and preserve relevant existing safeguards; a new test file is not mandatory
- **No unrelated improvements** — Stay focused on the specific bug

© cyrusagents · Apache-2.0 · cyrusagents/cyrus

Similar skills

All skills for Testing and QA →

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 634installs 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 pproenca The debug skill gives your agent a fixed order for bug work: reproduce, test hypotheses, find the root cause. Useful when a stack trace or a failing test lands on you. CX Codex +1 436installs Debug Mode Instructions official github A GitHub Copilot subagent that walks debugging in phases: reproduce the bug, find the root cause, patch it, verify. Useful when a failure is flaky and you don't know where to start. ★ 40,418repo stars ce-debug EveryInc Finds the root cause of a bug from trigger to symptom and applies a test-first fix. Useful when investigating broken behavior or failing CI logs. CX Codex +1 3,500installs vibe-debug KhazP A skill that walks an agent through a reproducible failure in an existing project: crashes, broken behavior, failing checks. Not for greenfield planning. CX Codex +1 ★ 3,183repo stars debug-my-harness zernie Reads the local .vigiles/runs.jsonl ledger to explain why an agent harness misbehaved. Use it when a skill stopped firing, a hook let something through, or a subagent broke its tool contract. CX Codex +1 1,500installs debug-issue tirth8205 This skill traces bugs through a code graph before source inspection, then checks call paths and change impact. Use it when an issue needs a narrower debugging scope. CX Codex +1 1,000installs why NeoLabHQ Conducts iterative Five Whys root cause analysis for technical bugs and incidents. Helps uncover process and system gaps instead of settling for superficial patches. CX Codex +1 1,200installs

From the same set19

summarize Formats a structured completion summary for Linear agent sessions. Useful when an agent finishes a task and needs to present clear results directly in Linear. CX Codex +1 886installs investigate Researches your repository files and functions, gathers context, and writes answers in Linear Markdown format. Helps when triaging tasks. CX Codex +1 863installs implementation Guides the agent to write production-ready code following existing patterns, handle errors, and avoid scope creep before verification. CX Codex +1 850installs verify-and-ship This skill takes finished changes through acceptance checks, tests, changelog updates, commit, push and pull request creation. CX Codex +1 843installs release This skill walks a Cyrus CLI release through trusted publishing: prepare, verify, publish, finish. Useful when a version has to ship without touching packages by hand. CX Codex +1 829installs f1-test-drive Checks whether a change needs F1 validation, then tests the affected product workflow or F1 harness end to end. CX Codex +1 804installs cyrus-setup-gitlab Configures glab and your git identity so Cyrus can open branches, commits and merge requests in your repo. CX Codex +1 785installs release-core-test Publishes cyrus-core as a -test.N prerelease under the npm test dist-tag so a hosted GUI can install an unreleased build without touching latest. CX Codex +1 712installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor