task-fix-bug-back

Reproduce backend bugs with failing tests before applying minimal code fixes.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/FoxSilou/ConfigurationClaude --skill task-fix-bug-back
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-fix-bug-back
Source: https://github.com/FoxSilou/ConfigurationClaude/tree/main/backend/.claude/skills/task-fix-bug-back
Command: npx skills add https://github.com/FoxSilou/ConfigurationClaude --skill task-fix-bug-back

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps developers reliably reproduce backend bugs and enforce a test-first workflow so fixes are validated by failing and then passing tests, reducing regressions and guesswork.

Core Features & Use Cases

  • Delegates to a specialized fix-bug agent that guides E2E reproduction, test creation, and targeted code changes.
  • Enforces test-first discipline: produce an end-to-end failing scenario, write a failing test, implement a minimal fix, and validate with green tests.
  • Ideal for .NET backend services where deterministic reproduction and TDD-style bug fixes are required during feature development or bug triage.

Quick Start

Reproduce the described failing end-to-end scenario, write a failing test that demonstrates the bug, and propose a minimal code change that makes the test pass.

Frequently Asked Questions about task-fix-bug-back

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

FAQPage Schema
How do I fix backend bugs using a test-first approach in .NET?

To fix backend bugs using a test-first approach, you reproduce the failing end-to-end scenario, write a failing test that demonstrates the bug, apply a minimal code change, and validate by achieving green test runs in your .NET backend services.

What is the best way to reliably reproduce an E2E backend bug before changing code?

The best way to reliably reproduce an E2E backend bug is to isolate the failing scenario and write a focused failing test that consistently demonstrates the error, ensuring any subsequent minimal code fixes are validated against a deterministic reproduction.

How does TDD workflow apply to bug fixes in backend repositories?

TDD workflow applies to bug fixes by enforcing test-first discipline: you create an end-to-end failing scenario, write a failing test, implement a minimal code fix to make the test pass, and verify the green test runs to reduce regressions and guesswork.

Can I use this E2E reproduction workflow for non-.NET backend services?

This E2E reproduction and TDD bug-fix workflow is designed primarily for .NET backend services and repositories where deterministic test isolation is required, so using it for non-.NET environments may lack specialized guidance for those specific frameworks.

Why should I write a failing test before applying a minimal code fix to a backend bug?

You should write a failing test before applying a minimal code fix to validate that the bug is reliably reproduced and ensure the subsequent code change resolves the exact scenario, reducing regressions and guesswork during backend bug triage.