claude

dotnet-test-creator-v4

Polyglot unit-test generation as a Kiro workflow (kiro-cli 2.26.0+, KAS engine) built on the current dotnet-test plugin: test-engineer entry agent, then Research → Plan → repeat[Implement, Validate] gated on a verdict file, handing off through .git/testagent/ so nothing is ever stageable. Ships the vendored dotnet-test skills.

1 on GitHubupdated 7 days ago
/

Plugin dotnet-test-creator-v4 from marketplace kiro-starter-kit in dwalleck/kiro-starter-kit. Commands read from the repo's manifest — 6 days ago.

What it installs

Skills (11)

  • assertion-quality

    Analyze assertion quality, depth, variety, and false confidence in existing tests. ALWAYS USE when asked about weak, shallow, trivial, always-true, self-referential, assertion-free, presence/truthiness-only, or insufficiently diverse assertions, including MSTest, Jest, pytest, and Go. DO NOT USE for

  • code-testing-extensions

    Provides file paths to language-specific extension files for the code-testing pipeline. Read this reference-only catalog for extension guidance files (e.g., dotnet.md for .NET, cpp.md for C++). Agents and skills read its bundled files directly; do not invoke this catalog through the model's skill to

  • code-testing

    ALWAYS USE for test work that requires changes: write, add, generate, repair, or strengthen tests for existing code in xUnit, MSTest, NUnit, pytest, Vitest/Jest, Go, or another framework. Includes regression cases, failing or flaky tests, coverage-driven additions, and audit-then-fix requests. Focus

  • find-untested-sources

    MANDATORY for static source-to-test pairing: find or list source files/modules without corresponding tests, or suggest test locations from repository structure. Invoke even for a tiny package; do not substitute manual globbing. Uses Roslyn for C#/.NET and tree-sitter for Python, TS/JS, Go, Java, Rus

  • scaffold-dotnet-test-project

    MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI

  • test-analysis-extensions

    Provides file paths to language-specific reference files for the test ANALYSIS skills (assertion-quality, test-anti-patterns, test-gap-analysis, test-smell-detection, test-tagging). Read this catalog to discover available extension files (e.g., dotnet.md for .NET/MSTest/xUnit/NUnit/TUnit, python.md

  • test-anti-patterns

    Audit a test file or suite; produce a severity-ranked diagnostic report. ALWAYS USE for tests that verify nothing, missing/tautological assertions, swallowed/broad exceptions, flaky/order-dependent tests, duplication, or magic values. Polyglot. DO NOT USE for direct edits: writing-mstest-tests owns

  • test-gap-analysis

    Pseudo-mutation analysis ONLY: answer whether tests would catch a bug if production code changed, which meaningful changes would still pass, or which caller-visible mutations existing assertions would miss; verify candidates when requested, then optionally close verified gaps. Includes explicit read

  • tunit-mocking

    TUnit's source-generated, AOT-compatible mocking framework — TUnit.Mocks. Use whenever the user is mocking dependencies in TUnit tests, references Mock.Of<T>(), `.Mock()` extension methods, `Any()`, `Is<T>(...)`, `WasCalled(Times.Once)`, or asks how to stub HttpClient/ILogger/ILogger<T> in TUnit. Al

  • writing-mstest-tests

    ALWAYS USE when asked to fix, rewrite, update, improve, modernize, show corrected code for, or explain existing MSTest tests or MSTest-specific configuration. Use for "review" when corrected code or edits are wanted, even for one pasted assertion or passing tests with bad failure output. Covers expe

  • writing-tunit-tests

    Best practices for writing TUnit unit and integration tests. Use whenever the user is writing, fixing, reviewing, or modernizing TUnit tests, or asks about [Test], [Arguments], [Before(Test)]/[After(Test)], [MethodDataSource], [ClassDataSource], [MatrixDataSource], hooks, lifecycle, parallelism, tim

Subagents (6)

  • code-testing-implementer

    Implement step of the dotnet-test-generation workflow's validation loop. Writes test files from .git/testagent/plan.md (first pass) or from the gaps in .git/testagent/validation.json (later passes), builds, tests, and fixes inline, verifies harness discovery, and appends .git/testagent/status.md. Wr

  • code-testing-planner

    Plan step of the dotnet-test-generation workflow. Reads .git/testagent/research.md and writes a phased .git/testagent/plan.md that maps every requirement to a concrete planned test or an explicit blocker. No shell; writes only under .git/testagent/.

  • code-testing-researcher

    Research step of the dotnet-test-generation workflow. Analyzes the bounded test-generation scope (structure, language, test framework, build/test commands, API surface, source-to-test pairing, requirement checklist) and writes .git/testagent/research.md. Runs read-only analysis plus the find-unteste

  • code-testing-setup

    Setup step of the dotnet-test-generation workflow. Checks that the workspace is a normal Git checkout, archives a previous .git/testagent/ run to .git/testagent-prev-<timestamp>, and creates a fresh empty .git/testagent/. Shell only (git rev-parse, mv, mkdir); every file-tool write is denied. Projec

  • code-testing-validator

    Validate step of the dotnet-test-generation workflow's loop. Runs the bounded build, a fresh test run, harness discovery, requirement-to-test mapping, the coverage-gap check, and the quality audit (test-gap-analysis, assertion-quality, test-anti-patterns) on the generated tests, then writes .git/tes

  • test-engineer

    Entry point for test generation in this workspace. Writes focused tests directly (one function, class, or file) and launches the dotnet-test-generation workflow (Research -> Plan -> Implement/Validate loop) for anything broader, then relays its Requirement | Evidence result. Also repairs failing tes

View source on GitHub

More from dwalleck/kiro-starter-kit

All 6 plugins →

Polyglot unit-test generation via an orchestrated Research → Plan → Implement → Validate agent pipeline, with deep .NET test-framework skills (MSTest/TUnit authoring, migrations, CRAP scores).

28 skills · 4 agents

1

Max-effort, recall-mode code review as a Kiro workflow for native Windows with no Python: eight parallel finder angles, per-candidate verification, a gap sweep, re-votes on unstable verdicts, then ranked findings and postable Conventional Comments.

4 agents

1

Builds features via an engine-enforced Spec → Probe → Design → Plan → Build → Validate pipeline that refuses to advance on a vague spec or disproven understanding, and loops when built code drifts from the plan.

1

Orchestrated PR code review agents for the Kiro CLI: an orchestrator plus six specialists (code-reviewer, code-simplifier, comment-analyzer, pr-test-analyzer, silent-failure-hunter, type-design-analyzer).

1

Orchestrated PR code review agents for the Kiro CLI: an orchestrator plus six specialists (code-reviewer, code-simplifier, comment-analyzer, pr-test-analyzer, silent-failure-hunter, type-design-analyzer).

1

Maintain dotnet-test-creator-v4?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins6 plugins