skills.rest
berlysia
berlysiaCOMMUNITY
Explore all skills by this author →
Website𝕏@berlysiaGitHub

bugfix

Reproduce bugs, write failing tests, and verify minimal fixes via TDD.

9|Updated Aug 20, 2018
Search Tags:#workflow#testing#tdd#debugging#bugfix#root-cause-analysis
One-click install
npx skills add https://github.com/berlysia/dotfiles --skill bugfix-berlysia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bugfix
Source: https://github.com/berlysia/dotfiles/tree/main/.skills/bugfix
Command: npx skills add https://github.com/berlysia/dotfiles --skill bugfix-berlysia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardized bug-fix workflow using a discipline of TDD (Red-Green-Refactor) to ensure root-cause analysis and minimal, validated changes.

Core Features & Use Cases

  • Enforces a repeatable, test-driven debugging process
  • Guides triage, reproduction, and minimal patch through automated checks
  • Applicable to ongoing maintenance, bug reports, and issue resolutions

Quick Start

Follow the Red-Green-Refactor workflow to reproduce the bug, write a failing test, implement a minimal fix, and verify with the full test suite.

Frequently Asked Questions about bugfix

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

FAQPage Schema
How do I fix bugs using a TDD workflow?▼

To fix bugs with a TDD workflow, you first reproduce the bug, write a failing test that captures the defect, implement a minimal code fix to make it pass, and then verify the entire test suite to prevent regressions.

What is the best way to standardize software maintenance and bug fixes?▼

Standardizing bug fixes requires enforcing a repeatable, test-driven debugging process that guides triage, reproduction, and minimal patch application through automated checks for consistent issue resolution.

How does root-cause analysis work during debugging?▼

Root-cause analysis during debugging works by requiring a failing test first, isolating the exact defect trigger, and validating that the minimal implemented fix addresses the underlying issue without introducing regressions.

Can I use this debugging workflow for ongoing maintenance and issue resolution?▼

Yes, you can use this debugging workflow for ongoing maintenance and issue resolution, as it applies the Red-Green-Refactor discipline to guide bug triage, reproduction, and validation across existing software projects.

Why should I write failing tests before implementing a bugfix?▼

Writing failing tests before a bugfix ensures you accurately reproduce the defect and perform root-cause analysis, enabling you to implement minimal validated changes and confirm the fix through regression testing.

What are the limitations of a TDD-based bugfix workflow?▼

A TDD-based bugfix workflow requires a complete test suite to validate changes, meaning bugs in untested legacy code or environments where automated regression testing is not possible cannot be effectively standardized or verified.

Related Skills

Explore More Software Engineering Skills→
Jamie-CuiJamie-Cui
28

test-driven-development

Encode Emacs Lisp behavior as ERT tests before coding.

Community
Intermediate
ano4lano4l

tdd-bug-fix

Automate a red-green-refactor bug-fix workflow with failing tests before fixes.

Community
Intermediate
chicanoandres702chicanoandres702

debugger

Diagnose software defects by capturing errors, isolating failures, and verifying fixes.

Community
Intermediate
u9401066u9401066
1

bug-fix

Enforce a structured bug-fixing workflow with regression tests and root-cause analysis.

Community
Advanced