skills.rest
OzeroHAX
OzeroHAXCOMMUNITY
Explore all skills by this author →
GitHub

coder-rules-debug-requirements

Guide coding agents through systematic debugging with reproducible examples and regression tests.

32|7|Updated Jan 28, 2026
Search Tags:#code quality#debugging#troubleshooting#bug fixing#verification#regression testing
One-click install
npx skills add https://github.com/OzeroHAX/AssistAgents --skill coder-rules-debug-requirements
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coder-rules-debug-requirements
Source: https://github.com/OzeroHAX/AssistAgents/tree/main/templates/skills/coder/rules/debug-requirements
Command: npx skills add https://github.com/OzeroHAX/AssistAgents --skill coder-rules-debug-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured protocol for debugging functional bugs, crashes, and regressions, ensuring a systematic approach from issue identification to verified fix and regression protection.

Core Features & Use Cases

  • Structured Debugging: Guides the coding agent through a clear, step-by-step debugging workflow.
  • Reproducibility Focus: Emphasizes creating minimal reproducible examples and verifying fixes against them.
  • Regression Prevention: Ensures that fixes include regression tests to prevent future occurrences.
  • Use Case: When a critical bug is reported in production, this Skill ensures the agent follows a rigorous process to identify the root cause, implement a fix, verify it thoroughly, and add a test to prevent recurrence.

Quick Start

Use the coder-rules-debug-requirements skill to debug the reported crash with the provided error logs and reproduction steps.

Frequently Asked Questions about coder-rules-debug-requirements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to debug functional bugs and crashes systematically?▼

Systematic debugging mandates creating minimal reproducible examples, localizing failing layers, stating testable hypotheses, applying root-cause fixes, and verifying against acceptance criteria to ensure confirmed fixes.

How do I fix a regression bug without breaking existing functionality?▼

Fixing a regression bug requires applying a root-cause fix, verifying against acceptance criteria, and adding regression tests to prevent future occurrences while providing evidence of reproducibility.

Why do I need a minimal reproducible example for troubleshooting code?▼

A minimal reproducible example is required for troubleshooting to localize failing layers and provide evidence of reproducibility, enabling you to state testable hypotheses and verify root-cause fixes.

Can I use a structured debugging workflow for production crash reports?▼

Yes, a structured debugging workflow processes production crash reports by guiding issue identification, root-cause implementation, and regression prevention, mandating verification against acceptance criteria for confirmed fixes.

What should I do if my bug fixing verification is not working?▼

If bug fixing verification fails, ensure you have created a minimal reproducible example and localized the failing layers, as the debugging process requires evidence of reproducibility and verification against acceptance criteria for confirmed fixes.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
vinvcnvinvcn
23

debugging-and-error-recovery

Diagnose software defects through structured triage and root-cause analysis.

Community
Advanced
519lab519lab
2

requesting-code-review

Run automated code review with security scans and static analysis before commit.

Official
Advanced
qazz92qazz92

tmux-real-user-testing

Simulate and log user interactions in a tmux environment for TUI testing.

Community
Intermediate