Can I use this with custom test arguments?

Yes, the skill allows you to pass optional arguments through to the dotnet test command or override the default command entirely via environment variables.

Where are the failure reports saved?

Failure reports and filters are saved in the artifacts/codex/ directory as test-failures.md and test-filter.txt.

Does this work with flaky test detection?

While it doesn't automatically detect flakes, it provides recommended commands for using --blame and --blame-hang to help you investigate and isolate unstable tests.

How does this skill help with large .NET solutions?

It saves time by identifying exactly which tests failed and providing a pre-formatted filter string, allowing you to rerun only the problematic tests instead of the entire suite.

DotNet Test Triage

Name: DotNet Test Triage
Author: bravellian

bybravellian

Security & Testing

Automates .NET test failure analysis by capturing failing cases and generating optimized rerun filters.

About

The dotnet-test-triage skill streamlines the debugging process for .NET developers by wrapping standard test execution with intelligent reporting. When test runs fail, it automatically extracts failed test cases to produce a markdown summary and a specific filter string. This allows developers to immediately rerun only the failing tests with various diagnostic flags, significantly reducing the feedback loop during troubleshooting and CI/CD debugging sessions.

Key Features

Generation of ready-to-use dotnet test filter strings
0 GitHub stars
Compact markdown failure summaries with error snippets
Automated failure capture from TRX logs
Recommended diagnostic commands for blame and parallelization control
Support for custom dotnet test arguments and command overrides

Use Cases

Quickly isolating and rerunning failed unit tests in large .NET solutions
Debugging flaky tests using specialized flags like --blame and --blame-hang
Generating readable failure reports for documentation or team communication

About

Key Features

Generation of ready-to-use dotnet test filter strings
0 GitHub stars
Compact markdown failure summaries with error snippets
Automated failure capture from TRX logs
Recommended diagnostic commands for blame and parallelization control
Support for custom dotnet test arguments and command overrides

Use Cases

Quickly isolating and rerunning failed unit tests in large .NET solutions
Debugging flaky tests using specialized flags like --blame and --blame-hang
Generating readable failure reports for documentation or team communication