dotnet-walls
Walls for a .NET change in a repository without its own quality gates — pinned, ephemeral analyzer, format, clone and scanner commands for the verify step, their identity ratchet, and the build traps. Use during a walls preflight, or when a worker's verify step needs .NET quality gates.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- dotnet-walls
- description
- Walls for a .NET change in a repository without its own quality gates — pinned, ephemeral analyzer, format, clone and scanner commands for the verify step, their identity ratchet, and the build traps. Use during a walls preflight, or when a worker's verify step needs .NET quality gates.
03 SKILL.md 正文
.NET walls
Defaults; the coordinator may change them with a recorded reason. Run every wall on the base first and gate only findings that are new by identity, never by line number. A repository that names its own analyzer configuration, clone gate or slop scanner in its agent instructions uses those instead.
| Wall | Command | Identity ratchet |
|---|---|---|
| Analyzers | dotnet build -warnaserror -p:EnforceCodeStyleInBuild=true -p:AnalysisLevel=latest-recommended (with -warnaserror off on the base run, to collect the base set) |
compare (diagnostic id, file, message) from the binary or text log; a repository without its own analyzer set produces hundreds of findings on the base, so the ratchet is mandatory |
| Format | dotnet format --verify-no-changes on the touched files |
new violations only |
| Clones | a clone detector with C# support, for example npx -y jscpd@5.4.1 --format csharp |
base clone set |
| Other scanners | through .NET 10's ephemeral tool runner, dnx <package>@<version> (confirm the syntax on the installed SDK), pinned |
per tool |
Traps
- Run verify commands and workers with
DOTNET_CLI_USE_MSBUILD_SERVER=0. A long-lived MSBuild server keeps the environment of the session that started it, so a restore can ignore the task's temp folder (seen: NuGet scratch hit a full per-user/tmpquota). Run one build per working tree at a time (CS2012). - Keep
DOTNET_CLI_HOMEwhere it is: each new CLI home can append a tools folder to the user's registryPATHon Windows. Give workersDOTNET_ADD_GLOBAL_TOOLS_TO_PATH=false. dotnet test --nologocan make a test platform report zero tests with a non-zero exit;total: 0is never a pass.- A
-p:property on the command line is global and replaces each project's own value.-p:NoWarn=...wipes the projects' NoWarn lists, including documented experimental-API opt-ins, and breaks the build. Pass extra warning settings through an environment variable the projects append to.
04 同仓库更多 Skills
writing-tunit-tests
Write tests in TUnit — the attributes, the async assertion model, data-driven cases, lifecycle hooks, and the parallelism rules. USE FOR writing or fixing a test in a TUnit project, translating a test idea into TUnit syntax, or reviewing TUnit test code for API mistakes. DO NOT USE FOR deciding what to test, judging whether a test is any good, or running tests.
dotnet-walls
Walls for a .NET change in a repository without its own quality gates — pinned, ephemeral analyzer, format, clone and scanner commands for the verify step, their identity ratchet, and the build traps. Use during a walls preflight, or when a worker's verify step needs .NET quality gates.
csharp-15
Write, review and modernize C# 15 (.NET 11) code correctly. Covers every C# 15 feature - collection expression arguments (`[with(...), ...]`), union types (`union`, `[Union]`, `IUnion`, custom unions), closed class hierarchies (`closed`), extension indexers, labeled `break`/`continue`, non-virtual static interface members on runtimes without default interface methods, and the preview memory-safety model (`unsafe(expr)`, `safe`, requires-unsafe members). Use when code targets net11.0 or LangVersion 15/preview, when the user mentions any of these features, when replacing marker interfaces, OneOf-style results, `goto`/flag loop exits or capacity/comparer boilerplate, or when the build reports CS8121, CS8509, CS8655, CS8510, CS0121/CS0411 on a `with(...)` element, CS9370, CS9380 or CS9363.
verified-waves
Run one task as verified multi-agent waves. Plans the fan-out, sends findings to fresh skeptics, keeps a ledger, and reports N of M done; small tasks stay solo.
harness
The bundled dispatch harness, which runs a task file on worker models through OpenCode or Codex, fences their writes, escalates their asks to the operator, settles each result from git and its verify commands, and records every step in a ledger. Its commands, task file, modes and write fence, configuration, runs and their recovery, ledger and exit codes.
delegating-to-worker-models
Use when you hand off implementation, a plan, research a decision will rely on, or a review, and you brief the worker and check what comes back. A subagent that searches, reads in parallel, or keeps your context small is ordinary tool use. Covers what stays with you, the mechanism, assigning work by strength, the walls preflight, prompts without contradictions, the worker contract and model profiles, evidence from your own run, review, and the fix-up loop.