bugfix

Fix bugs in C#, Python, or Flutter/Dart files using a test-driven workflow.

Updated Sep 13, 2025
One-click install
npx skills add https://github.com/nobelk/claude-tools --skill bugfix-nobelk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugfix
Source: https://github.com/nobelk/claude-tools/tree/main/skills/fix-bug
Command: npx skills add https://github.com/nobelk/claude-tools --skill bugfix-nobelk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fix a bug in a user-specified file using a test-driven approach. Claude writes failing unit tests that reproduce the bug, fixes the code, verifies the tests pass, runs the full test suite to catch regressions, then clears context and reviews all changes for accuracy and optimality. Supports C#, Python, and Flutter/Dart codebases. Use this skill whenever the user reports a bug, defect, or unexpected behavior in their code and wants it fixed — even if they don't explicitly say "bug." Also trigger when a user says things like "this isn't working," "I'm getting an error," "this test is failing," "something broke," or "can you fix this."

Core Features & Use Cases

  • Thorough bug reproduction via failing unit tests across supported languages (C#, Python, Flutter/Dart)
  • Minimal, correct code fixes with regression testing and final review
  • Guidance on triggering the workflow from user reports like "this isn't working" or "I've got an error"

Quick Start

Provide the buggy file path and run the project's tests to reproduce the failure, then request a fix.

Frequently Asked Questions about bugfix

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

FAQPage Schema
How do I fix a bug using a test-driven workflow in Python?

Yes, you can fix bugs in Flutter or Dart codebases using this approach by writing failing unit tests to reproduce the defect, applying minimal code fixes, and running the full test suite to verify the changes and prevent regressions.

What is the best way to fix a failing unit test without causing regressions?

The best way to fix a failing unit test without causing regressions is to first reproduce the bug with a targeted test, apply a minimal code correction, and then execute the entire test suite to verify no other functionality broke during the fix.

Do I need a functioning test framework to run a test-driven bugfix?

Yes, you need a functioning test framework and repository access to run a test-driven bugfix. The workflow requires executing unit tests to reproduce the original failure and validating end-to-end that your code changes resolve the issue safely.

Can I use this test-driven code fix approach for C# projects?

Yes, you can use this test-driven code fix approach for C# projects. The workflow supports C# codebases by generating failing unit tests to reproduce the bug, applying minimal corrections, and running regression tests to validate the final changes.

Why write failing unit tests before fixing the actual code defect?

Writing failing unit tests before fixing the code defect ensures you have accurately reproduced the bug. Once the code is corrected, the same test validates the fix, and running the full suite detects any unexpected regressions caused by the edit.