autonomous-loops

Resolve .NET build and test failures with bounded, progress-tracked iterations.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/shahdanish/vibepos --skill autonomous-loops-shahdanish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autonomous-loops
Source: https://github.com/shahdanish/vibepos/tree/main/skills/autonomous-loops
Command: npx skills add https://github.com/shahdanish/vibepos --skill autonomous-loops-shahdanish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps resolve .NET build and test failures, perform controlled refactors, and scaffold features without getting stuck in infinite or repetitive retry cycles.

Core Features & Use Cases

  • Bounded build-fix iterations: Iteratively run dotnet build, categorize compiler errors, apply targeted fixes, and stop on pass, no progress, regression, or max iterations.
  • Bounded test-fix iterations: Run dotnet test, diagnose each failure as test vs. production root cause, apply the appropriate fix, and stop on pass, no progress, infrastructure failure, or max iterations.
  • Verification-driven refactor and scaffold loops: Perform multi-step refactors with build+test verification after each target, and generate new features end-to-end with staged build and test verification.

Use Case: When a change causes multiple compiler errors in a Clean Architecture .NET solution, run a build-fix loop that applies error-specific remedies while ensuring progress and reverting on regressions until the solution builds cleanly.

Quick Start

Ask the AI to fix the build and make tests pass for your .NET solution using bounded autonomous loops with progress detection and safety exits.

Frequently Asked Questions about autonomous-loops

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

FAQPage Schema
How do I fix .NET build failures across multiple files without getting stuck in infinite loops?

Bounded build-fix iterations resolve .NET build failures by running dotnet build, categorizing compiler errors, and applying targeted fixes. The loop automatically stops upon passing, no progress detection, regression, or hitting a maximum iteration cap.

What is the best way to diagnose and fix failing .NET unit and integration tests iteratively?

Bounded test-fix iterations diagnose failing .NET tests by distinguishing test vs. production root causes and applying appropriate fixes. The loop stops on pass, no progress, infrastructure failure, or max iterations.

Can I use iterative loops to refactor a Clean Architecture .NET solution safely?

Verification-driven refactor loops perform multi-step refactors in .NET solutions with build and test verification after each target. They ensure progress and automatically revert changes upon detecting regressions.

How do I scaffold new .NET features end-to-end with staged compilation and test verification?

Verification-driven scaffold loops generate new .NET features end-to-end with staged build and test verification. This ensures each scaffolding step maintains compilation integrity and test validity.

When should I avoid using autonomous iteration loops for build and test repairs?

Avoid autonomous iteration loops during critical or cascading failures that trigger emergency stop conditions. They are also bounded by max-iteration caps and should not be used when infrastructure failures block test execution.