mcpField
D
debug

debug

github.com/cyrusagentsDevelopment879834 installsUpdated 1d ago
Repository

About debug

A debugging skill for developers that structures work from reproducing a reported issue through root-cause analysis and a focused fix. It favors minimal changes and verifies the fix by repeating the reproduction and relevant checks.

Key features

  1. 01Analyze symptoms and error messages
  2. 02Trace errors through the codebase
  3. 03Reproduce and document the failure
  4. 04Implement a targeted minimal fix
  5. 05Recheck reproduction and relevant tests

Use cases

  1. 01Investigating a reported software bug
  2. 02Finding the source of an error path
  3. 03Confirming a fix against a minimal reproduction
  4. 04Deciding whether a regression test is warranted

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cyrusagents/cyrus --skill debug

After installing, type/debugin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported