aibdd.auto.csharp.it.refactor

Automate C# IT refactoring across test and production code with green test gates.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/zenbuapps/zenbu-powers --skill aibdd-auto-csharp-it-refactor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aibdd.auto.csharp.it.refactor
Source: https://github.com/zenbuapps/zenbu-powers/tree/main/skills/aibdd.auto.csharp.it.refactor
Command: npx skills add https://github.com/zenbuapps/zenbu-powers --skill aibdd-auto-csharp-it-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

C# IT Stage 4: refactor phase guidance to improve testability and production quality while strictly following /aibdd.auto.csharp.code-quality standards.

Core Features & Use Cases

  • Phase A focuses on refactoring test code (Steps/Hooks/Helpers) and ensuring tests pass after every change.
  • Phase B focuses on refactoring production code (Models, Repositories, Services, Controllers, DTOs) with a green test gate after each step.
  • Enforces consistency with /aibdd.auto.csharp.code-quality and standard formatting.

Quick Start

Specify the target feature path and run Phase A then Phase B, ensuring all tests remain green.

Frequently Asked Questions about aibdd.auto.csharp.it.refactor

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

FAQPage Schema
How do I refactor C# code while ensuring tests stay green?▼

This Skill automates a disciplined C# refactoring workflow that improves testability by running Phase A for test code and Phase B for production code. It enforces a green test gate by running dotnet test after every change.

What is the best way to improve testability in a .NET project?▼

Improving testability in a .NET project involves restructuring production code like Models, Repositories, and Services. This workflow handles it in Phase B, ensuring maintainability while keeping tests green after each step.

Can I use dotnet format and dotnet build with an automated refactor workflow?▼

Yes, you can use dotnet format and dotnet build within this workflow. It supports these commands alongside dotnet test and applies guardrails to ensure outputs meet code-quality constraints.

Does C# refactoring require separating test code changes from production code changes?▼

Yes, separating test code from production code changes is required. The workflow uses Phase A to refactor test code first, ensuring tests pass before starting Phase B for production code refactoring.

What limitations exist when enforcing code-quality constraints during dotnet refactoring?▼

Limitations include strict adherence to /aibdd.auto.csharp.code-quality standards and a mandatory green test gate after each step. The refactoring process halts if dotnet test fails or quality constraints are violated.

Why do I need a green test gate for C# production code refactoring?▼

A green test gate is needed during C# production code refactoring to prevent regressions. It verifies that modifications to Models, Repositories, and Services maintain existing functionality before proceeding.