skills.rest
withzombies
withzombiesCOMMUNITY
Explore all skills by this author →
Website𝕏@withzombiesGitHub

fixing-bugs

Automate bug fixing from issue creation through regression testing and closure.

80|17|Updated Oct 27, 2025
Search Tags:#debugging#TDD#verification#bd#bug#regression-test
One-click install
npx skills add https://github.com/withzombies/hyperpowers --skill fixing-bugs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fixing-bugs
Source: https://github.com/withzombies/hyperpowers/tree/main/skills/fixing-bugs
Command: npx skills add https://github.com/withzombies/hyperpowers --skill fixing-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies a complete bug-fix workflow: reproduce, track in a bug-tracking system, debug systematically, write a failing test, implement the fix, verify, and close. Every bug gets a BD issue and regression test.

Core Features & Use Cases

  • Track: Create a bug issue and document reproduction steps.
  • Debug: Systematic investigation with debugging tools.
  • Test (RED): Write a failing regression test to reproduce the bug.
  • Fix (GREEN): Implement the root-cause fix with minimal changes.
  • Verify: Run the full test suite to confirm the fix.
  • Close: Update the bug issue and close it with a regression note.

Quick Start

Reproduce the issue, create a BD bug, run debugging-with-tools for root-cause analysis, write a regression test with hyperpowers:test-driven-development, implement the fix, verify with the test suite, and finally close the BD issue.

Frequently Asked Questions about fixing-bugs

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

FAQPage Schema
How do I set up a complete bug-fix workflow from discovery to closure?▼

A bug-fix workflow systematically reproduces the issue, tracks it in a bug-tracking system, debugs the root cause with tools, writes a failing regression test, implements the fix, verifies with a full test suite, and closes the issue. This Skill automates that entire sequence to ensure every bug gets tracked and tested.

What's the best way to prevent regression bugs after fixing a bug?▼

Write a failing regression test that reproduces the bug before implementing the fix. This test-driven approach ensures the bug stays fixed across iterations and catches similar issues early. Verify the complete test suite passes after the fix is applied.

How do I debug bugs systematically with tools?▼

Systematic debugging with tools involves investigating the root cause methodically rather than applying surface-level patches. This workflow enforces debugging as a tracked step between issue creation and fix implementation, ensuring minimal changes target the actual problem.

Do I need to create a bug issue for every fix I make?▼

Yes. This workflow requires creating a bug issue to document reproduction steps and track the fix. A bug issue provides traceability, links the regression test, and ensures closure includes notes on the fix and prevention measures.

What's the difference between writing a test before vs. after fixing a bug?▼

Writing a failing test before the fix (test-driven development) verifies the bug exists and ensures the fix actually solves it. This approach prevents false fixes and creates a permanent regression test that catches the bug if it reoccurs.

Related Skills

Explore More Software Engineering Skills→
bearcovebearcove
29

subtest-isolation

Create minimal reproduction subtests to isolate and debug failing tests.

Official
Advanced
sQVesQVe

fix-bug

Automate end-to-end bug fixing with test-driven development and regression tests.

Community
Advanced
unclehowellunclehowell

test-driven-development

Enforce a test-first workflow requiring failing tests before production code.

Community
Intermediate
anorthamanortham
2

bug-hunt

Guides users through bug reproduction, root-cause identification, and regression testing.

Community
Advanced