cyrusagents/cyrus

debug

Full debugging workflow — reproduce the bug with a failing test, perform root cause analysis, then implement a minimal fix.

Trending #5147 Hot #5840 First seen Apr 4, 2026

Installation

$ npx skills add cyrusagents/cyrus --skill debug

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from cyrusagents/cyrus · top by installs.

npx skills add cyrusagents/cyrus

Browse all from cyrusagents/cyrus

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 796
License LICENSE
Default branch main
Open issues 48
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,343 B
  • docs SUMMARY.md 138 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 591 installs

SKILL.md

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 — Create a minimal failing test case that reproduces the exact error
  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 — Run the failing test to confirm it passes, then run the full test suite to check for regressions

Principles

  • Minimal changes — Fix the bug, nothing more
  • Targeted — Only touch affected code paths
  • Tested — The fix must make the failing test pass and not break existing tests
  • No unrelated improvements — Stay focused on the specific bug