Dotnet unit test generator
Skill brunovgprado/engineering-agent-skills/dotnet/dotnet-unit-test-generator
A collection of reusable AI Agent Skills for software engineering, architecture, code review, performance analysis, DevOps, cloud, and developer productivity.
npx -y skills add brunovgprado/engineering-agent-skills --skill dotnet-unit-test-generatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generates standardized Xunit and Moq unit tests for .NET/C# solutions by mirroring existing architecture, directory layout, naming, mock patterns, and coverage conventions. Use only when the user explicitly invokes this skill via slash command or attaches it. Triggers include .NET solutions, C# unit tests, Xunit, Moq, a single named class, repository-wide test gap analysis, and test project scaffolding.
SKILL.md
3.6 KB, as published. Nobody here has run it
.NET Unit Test Generator
Generates unit tests for .NET/C# solutions using Xunit and Moq, aligned with what the solution already does — never invent parallel conventions.
Quick start
- Confirm
.sln/project, scope mode, and report destination → references/scope-mode.md. - Read existing patterns → references/discovery.md.
- Coverage plan (explore mode only) → references/coverage-plan.md.
- Generate tests → references/generation.md.
- Report → references/report.md + assets/report-template.md.
Stack: Xunit + Moq by default; if the solution uses NUnit, FakeItEasy, etc., follow what is already there.
Communication and code
Always interact with the user in English. Generated test code must stay in English, following standard .NET ecosystem conventions.
Use progressive disclosure:
- share only what is needed at each step;
- keep responses concise;
- advance based on context you have already gathered;
- ask focused questions only when necessary.
Workflow
Complete one step per response. Do not jump ahead to later steps.
Progress:
- [ ] Step 1 — Context (solution, scope mode, class OR explore, report)
- [ ] Step 2 — Discovery
- [ ] Step 3 — Plan (explore) or skip (specific class)
- [ ] Step 4 — Generation
- [ ] Step 5 — Report
| Step | Details |
|---|---|
| 1 | references/scope-mode.md |
| 2 | references/discovery.md |
| 3 | references/coverage-plan.md |
| 4 | references/generation.md |
| 5 | references/report.md |
Step 1 — Scope
- Specific class — only that class gets tests.
- Explore repository — map classes lacking coverage using this skill’s criteria.
Resources (progressive disclosure)
Read only what you need. All links are one level from this SKILL.md.
| Resource | When |
|---|---|
| references/scope-mode.md | Step 1 |
| references/discovery.md | Step 2 |
| references/coverage-plan.md | Step 3 (explore) |
| references/relevance.md | Relevance; [ExcludeFromCodeCoverage] |
| references/generation.md | Step 4 |
| references/report.md | Step 5 |
| assets/report-template.md | Writing the report |
| references/xunit-moq.md | Solution lacks test examples |
| examples/examples.md | Unclear modes or expected output |
Final checklist
- Scope mode honored
- Specific class: no other classes; ignore
[ExcludeFromCodeCoverage]on the requested class - Explore: do not test
[ExcludeFromCodeCoverage]types; list them under Important Skipped Classes - Relevance (High/Medium/Low) recorded for every tested class
- Test code in English; report per references/report.md