dotnet-build
Skill3 starsChanged 2 months agoMITView on GitHub
Build 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.
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-testSkill
- 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. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 36
Run, in a single Bash tool call, with dangerouslyDisableSandbox: true (per this project's dotnet-command convention — no permission prompt …
- Very specific: line 49
Read .tmp/dotnet-build.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 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
dotnet build
Runs dotnet build 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-build [solution-path] [Configuration]
- solution-path (optional): path to the
.sln, relative to project root. Defaults tosrc/GlobalStrategy.Core.slnfor this repo. - Configuration (optional): defaults to
Debug. PassReleaseexplicitly when needed (e.g. aftersrc/changes so Unity plugin DLLs underAssets/Plugins/Core/are current — see.claude/rules/unity/plugins.md; do not commit those DLLs).
Any additional flags the caller needs (e.g. --no-restore) 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-build.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 build <solution-path> -c <Configuration> > .tmp/dotnet-build.log 2>&1Default:
dotnet build src/GlobalStrategy.Core.sln -c Debug > .tmp/dotnet-build.log 2>&1- Read
.tmp/dotnet-build.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 the error/warning count from what you read.
- 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.

