dotnet-test
Skill3 starsChanged 2 months agoMITView on GitHub
Test a .NET solution from the project root without `cd`, logging output to a single file that gets read once instead of piped through repeated Bash calls.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- landim32/awesome-ai-skillstheir own version, first seen Nov 1, 2026
- codebeltnet/agentictheir own version, first seen Oct 3, 2026
- emaginebr/AvaBottheir own version, first seen Apr 8, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- codebeltnet/agentic★ 3same name
- emaginebr/AvaBot★ 2same name
- landim32/awesome-ai-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/issue-clarification-questions.mdcCursor rule
- .cursor/rules/reset-font-assets.mdcCursor rule
- .cursor/rules/src-dotnet-build-release.mdcCursor rule
- .cursor/rules/unity-plugins-before-work.mdcCursor rule
- codex-issueSkill
- commitSkill
- complete-prdSkill
- dependency-docsSkill
- dotnet-buildSkill
- dotnet-testSkill
- generate-imageSkill
- implementSkill
- meeting-joinSkill
- meeting-scheduleSkill
- meeting-startSkill
- plan-reviewSkill
- planSkill
- prSkill
- specifySkill
- unity-e2e-runSkill
- unity-pluginsSkill
- add-terminal-commandSkill
- dependency-docsSkill
- dotnet-benchmarkSkill
- dotnet-buildSkill
- end-game-score-calibrationSkill
- flag-assetsSkill
- github-issue-automationSkill
- image-generationSkill
- localizationSkill
- meeting-joinSkill
- meeting-scheduleSkill
- meeting-startSkill
- milestone-completeSkill
- province-config-generatorSkill
- unity-e2e-runSkill
- unity-pluginsSkill
- unity-prefabsSkill
- unity-scenesSkill
- update-branchSkill
- cursor-meeting-joinSkill
- cursor-meeting-startSkill
- unity-pluginsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Log to one file, read it once: Don't pipe through tail/grep as a second Bash call.
- Very specific: line 35
Run, in a single Bash tool call, with dangerouslyDisableSandbox: true (per this project's dotnet-command convention — no permission prompt …
- Very specific: line 48
Read .tmp/dotnet-test.log with the Read tool.
- Distinctive: line 53
Delete the log when done with it, as a separate Bash call, per the temp-scripts run-then-delete convention.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
dotnet test
Runs dotnet test against a solution, avoiding the two habits that cause unnecessary
permission prompts and wasted turns:
- Never prefix the command with
cd. The Bash tool's working directory is already the project root for every call — a leadingcdis redundant and (per this project's shell rule) triggers an extra permission prompt for no benefit. - Log to one file, read it once. Don't pipe through
tail/grepas a second Bash call. Redirect stdout+stderr to a single log file, then use theReadtool on that file (withoffset/limitif it's long) instead of issuing more shell commands.
Args
/dotnet-test [solution-path] [Configuration] [--filter <expr>]
- solution-path (optional): path to the
.sln, relative to project root. Defaults tosrc/GlobalStrategy.Core.slnfor this repo. - Configuration (optional): defaults to
Debug. - --filter (optional): forwarded verbatim to
dotnet test --filterto scope to a subset of tests (e.g. a single class while iterating).
Any additional flags the caller needs should be appended to the command line as given — this skill only fixes how the command is invoked, not what it is.
Steps
- Pick the log path:
.tmp/dotnet-test.log(gitignored, per.claude/rules/temp_scripts.md). Run, in a single Bash tool call, with
dangerouslyDisableSandbox: true(per this project's dotnet-command convention — no permission prompt needed as long as there's nocd):dotnet test <solution-path> -c <Configuration> [--filter <expr>] > .tmp/dotnet-test.log 2>&1Default:
dotnet test src/GlobalStrategy.Core.sln -c Debug > .tmp/dotnet-test.log 2>&1- Read
.tmp/dotnet-test.logwith theReadtool. Useoffsetfrom the end (or a largelimit) for heavy output — don't re-run the command to see more, and don't add a second Bash call to filter it. - Report pass/fail/skip counts from what you read, and quote any failing test names and assertion messages.
- Delete the log when done with it, as a separate Bash call, per the temp-scripts run-then-delete convention.
Notes
- This applies to any solution/project, not just one repo — the log-file + single-Read pattern is the reusable part. The default solution path above is specific to GlobalStrategy; adjust it per-project.
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.

