agentleFS
ceedaragentsceedaragents/cyrus/skills/debug/SKILL.md

debug

Skill888 starsChanged 53 days agoApache-2.0View on GitHub

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

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-discord, add-slack and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • +10 more from microsoft

The file

Files
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 — 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.