How do I install the Dotnet CLI Fix Loop skill?

Run npx skillmds add viktor-ferenczi/dotnet-cli-fix-loop in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Dotnet CLI Fix Loop skill do?

Iterates on a .NET CLI project buildable with `dotnet build` until it builds and runs without errors. It is listed under Coding & Dev Tools on SkillMD.

Is Dotnet CLI Fix Loop safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dotnet CLI Fix Loop?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dotnet CLI Fix Loop free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Dotnet CLI Fix Loop?

viktor-ferenczi (@viktor-ferenczi) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dotnet CLI Fix Loop by viktor-ferenczi

Name: Dotnet CLI Fix Loop
Rating: 4.5 (4 reviews)
Author: viktor-ferenczi

File contents

Iterate on the specified .NET project until it builds and runs successfully. If no project is specified, ask which project to work on in the current solution.

Safety

CRITICAL: REFUSE to use this skill if operating in a production environment.
CRITICAL: NEVER delete or disable any pre-existing tests.
Keep working in the current branch, do not switch between branches.

Steps

Build the project using dotnet build.
If the build fails, fix the first issue in the code. If the project is in a Git repository, commit the fix into the current branch. Then go to step 1.
Run the project using dotnet run.
If there is no error, then stop and provide a concise report of all fixes made.
Fix the first problem reported. If the project is in a Git repository, commit the fix into the current branch. Then go to step 1.

Remarks

Skip all Git commits if there is no Git repository in the same folder as the solution or project.
Focus on fixing one issue at a time to keep changes minimal and reviewable.
Use descriptive commit messages that explain what was fixed.
Do not introduce unnecessary changes beyond what is needed to fix each issue.

Frequently asked questions