write-bug-tests

Write failing xUnit tests that reproduce bug behavior in C# projects.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/IntelliTect/IntelliPlugins --skill write-bug-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-bug-tests
Source: https://github.com/IntelliTect/IntelliPlugins/tree/main/plugins/enterprise-bug-fixing/skills/write-bug-tests
Command: npx skills add https://github.com/IntelliTect/IntelliPlugins --skill write-bug-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write failing xUnit tests that precisely reproduce a bug's behavior, following the test-first methodology. Tests should fail before the fix and pass after it.

Core Features & Use Cases

  • Reproduce bugs with deterministic tests in C# projects using xUnit.
  • Enforce test-first workflow to guide fixes and prevent regressions.
  • Document expected vs. actual behavior for each bug scenario.

Quick Start

Create a failing xUnit test that reproduces the bug, then run the test suite to confirm it fails before the fix and passes after.

Frequently Asked Questions about write-bug-tests

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

FAQPage Schema
How do I write a failing xUnit test to reproduce a C# bug?

Writing a failing bug-repro test first means creating an xUnit test that captures the incorrect behavior before fixing it. This test-first approach documents expected versus actual behavior, ensuring the test fails initially and passes after the code is corrected.

What is the test-first approach for fixing regression bugs in C#?

A test-first bug-repro workflow in C# targets typical and edge-case scenarios in the affected class or method. It requires integrating clearly named xUnit tests into existing test projects to verify the targeted behavior remains correct after applying fixes.

Does this test-first bug reproduction method work with existing C# test projects?

Yes, the test-first bug reproduction method integrates directly with existing C# test projects. It ensures newly written xUnit tests for typical and edge-case scenarios align with current project structures to verify behavior accurately before and after applying fixes.

Why should I write a failing test before fixing a bug?

Writing a failing test before fixing a bug enforces a test-first workflow that precisely documents expected versus actual behavior. This practice confirms the bug exists, guides the specific code fix, and prevents future regressions by ensuring the test passes afterward.

How do I structure xUnit tests for bug reproduction?

Structure xUnit tests for bug reproduction using the Arrange-Act-Assert pattern. Ensure tests are clearly named to reflect the specific bug scenario, cover typical and edge-case behaviors, and integrate with existing test projects to verify behavior before and after fixes.