finding-tests
Skill40 starsChanged 30 days agoApache-2.0View on GitHub
Locates existing tests for a given C# class and method using the test coverage data supplied by IDE. Triggers ONLY for C# production code (`.cs` files in a Rider .NET solution) when generating new tests, adding test coverage, finding existing tests, or when the user mentions uncovered lines, test files, or test suites. Must be used before writing or editing C# test code when finding already existing tests is necessary. Do NOT invoke for non-C# languages — the underlying tool only understands C# symbols and will not return useful results.
In this repository6 other files it gives its agents.
- debugging-codeSkill
- navigating-codeSkill
- refactoring-codeSkill
- ue-code-authoringSkill
- ue-live-debuggingSkill
- ue-test-authoringSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 3 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
If the production code in question is not C# - do not use this skill.
- Very specific: line 12
Always use the findTests tool via execute_tool to locate existing tests for a given C# class and method.
- Very specific: line 77
Every --param MUST be followed by a value (no bare flags)
- Distinctive: line 80
All file paths must be absolute
- Very specific: line 84
C# only: Before invoking findTests, verify the production file is .cs.
- Very specific: line 86
If findTests reports no tests exist, trust that result — do not retry with alternative search tools.
- Distinctive: line 87
After finding tests, read them to understand the project's testing conventions before making any changes.
- Very specific: line 92
If execute_tool is not available, inform the user and fall back to grep/glob only as a last resort.
- Very specific: line 95
If calling findTests via execute_tool times out, inform the user and fall back to your standard test discovery method.
- Very specific: line 99
If findTests returns empty results, trust the result.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Finding Existing Tests
Applies to: C# code only. If the production code in question is not C# - do not use this skill. Skip it silently and use the host's normal test-discovery approach. The underlying coverage tool only understands C# symbols.
Always use the findTests tool via execute_tool to locate existing tests for a given C# class and method. This tool queries the IDE code coverage data directly and is:
- Precise — returns exact test locations without false positives
- Token-efficient — no need for glob, grep, or directory listing guesses
- Fast — a single call replaces multiple rounds of searching
findTests
Find existing tests for a given production class and method. Supply the production code's class name, namespace, and file path — the tool returns the path of the single test file most relevant to the given method.
Syntax
execute_tool(command="findTests --className <value> --classNamespace <value> --filePath <value> [--methodName <value>] [--methodArguments <value>]")Parameters
| Parameter | Type | Required | Description |
--className | string | Yes | Name of the class |
--classNamespace | string | Yes | Namespace of the given class |
--filePath | string | Yes | Absolute file path to file with the given class |
--methodName | string | No | Name of the method |
--methodArguments | string | No | Names and types of the method arguments — use to target a specific overload (e.g. "TextReader reader, Type objectType") |
String parameters: Quote values containing spaces: --filePath '/Users/dev/MyProject/src/Services/OrderService.cs'
Examples
1. Class only — no method name
User says: "Find the tests for the JsonSerializer class"
{"tool":"execute_tool","arguments":{"command":"findTests --className JsonSerializer --classNamespace Newtonsoft.Json --filePath /projects/Newtonsoft.Json/Src/Newtonsoft.Json/JsonSerializer.cs"}}2. With method name
User says: "Find tests for the Deserialize method in JsonSerializer"
{"tool":"execute_tool","arguments":{"command":"findTests --className JsonSerializer --classNamespace Newtonsoft.Json --filePath /projects/Newtonsoft.Json/Src/Newtonsoft.Json/JsonSerializer.cs --methodName Deserialize"}}3. With method name and arg names — specific overload
User says: "Find tests for the Deserialize(TextReader reader, Type objectType) overload in JsonSerializer"
{"tool":"execute_tool","arguments":{"command":"findTests --className JsonSerializer --classNamespace Newtonsoft.Json --filePath /projects/Newtonsoft.Json/Src/Newtonsoft.Json/JsonSerializer.cs --methodName Deserialize --methodArguments 'TextReader reader, Type objectType'"}}4. Generic class and method
User says: "Find tests for the ReadJson<TResult> method in JsonConverter<T>"
{"tool":"execute_tool","arguments":{"command":"findTests --className 'JsonConverter<T>' --classNamespace Newtonsoft.Json --filePath /projects/Newtonsoft.Json/Src/Newtonsoft.Json/JsonConverter.cs --methodName 'ReadJson<TResult>'"}}5. Paths with spaces
{"tool":"execute_tool","arguments":{"command":"findTests --className DnsClient --classNamespace My.Network.Clients --filePath '/Users/dev/MyProject/src/Network Clients/DnsClient.cs' --methodName ResolveAsync"}}Pitfalls
- Every
--paramMUST be followed by a value (no bare flags) - Values with spaces must be quoted:
--filePath '/Users/dev/MyProject/my folder/file.cs' - Omit optional parameters entirely rather than passing empty strings
- All file paths must be absolute
Rules
- C# only. Before invoking
findTests, verify the production file is.cs. If it is any other language, do not invoke this skill or its tool — skip silently and fall back to standard test discovery. - Prefer
findTestsover glob, grep, or directory listing to find tests in C# code. These are wasteful and imprecise. Ifexecute_toolis unavailable, fall back to grep/glob as a last resort and inform the user. - If
findTestsreports no tests exist, trust that result — do not retry with alternative search tools. - After finding tests, read them to understand the project's testing conventions before making any changes.
Troubleshooting
execute_tool not available
If execute_tool is not available, inform the user and fall back to grep/glob only as a last resort.
findTests via execute_tool timeout
If calling findTests via execute_tool times out, inform the user and fall back to your standard test discovery method.
You may stop trying findTests if it timeouts for three times in a row.
No tests found
If findTests returns empty results, trust the result. Do not retry with alternative search methods.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

