agentleFS
AterDevAterDev/Perigon.CLI/.agents/skills/test/SKILL.md

test

Skill54 starsChanged 2 months agoApache-2.0View on GitHub

Use for .NET test design and validation with xUnit v3, Moq, focused regression tests, command tests, service/manager tests, code generation tests, Roslyn helper tests, MiniDb isolation, HTTP stubs, temp directories, and deciding whether to run targeted tests or builds.

179 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 154 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use xUnit v3 [Fact], [Theory], and [InlineData].

    line 19
  2. Distinctive:

    Use Moq when simple stubs are not enough.

    line 20
  3. Very specific:

    Use unique temp directories for file-system tests and restore current directory in finally.

    line 22
  4. Distinctive:

    Keep tests focused on observable behavior and regression risk.

    line 24
  5. Distinctive:

    Avoid full solution builds unless the user asks or risk justifies the time.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 154 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Test And Validation

Test Placement

  • CLI behavior: tests/StudioMod.Tests/Commands
  • Core services: tests/StudioMod.Tests/Services
  • Managers and MiniDb behavior: tests/StudioMod.Tests/Managers
  • Code generation and OpenAPI/request clients: tests/StudioMod.Tests/Generate
  • Roslyn, parsing, conversion, assembly, and utilities: tests/StudioMod.Tests/Helper
  • Shared model behavior: tests/StudioMod.Tests/Models

Conventions

  • Use xUnit v3 [Fact], [Theory], and [InlineData].
  • Use Moq when simple stubs are not enough.
  • Stub HTTP with local HttpMessageHandler; tests must not hit live endpoints.
  • Use unique temp directories for file-system tests and restore current directory in finally.
  • Isolate MiniDb paths and avoid shared persistent state.
  • Keep tests focused on observable behavior and regression risk.
  • For generated code, assert meaningful snippets or structural markers instead of large snapshots unless exact text is the contract.

Validation Policy

  • Metadata-only changes usually need path/frontmatter inspection, not a build.
  • Narrow behavior changes should get targeted tests for the affected area.
  • Broad cross-layer changes may justify targeted tests plus diagnostics or a build.
  • Avoid full solution builds unless the user asks or risk justifies the time.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.