New Event Source
aws/aws-lambda-dotnet
Add a new AWS event source attribute (e.g., Kinesis, Kafka, MQ) to the Lambda .NET Annotations framework, including the attribute class, source generator integration, CloudFormation writer, unit…
Write, fix, or review NeoServer unit tests using xUnit and FluentAssertions.
Install Unit Testing
$ npx skills add OpenCoreMMO/OpenCoreMMO --skill unit-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install OpenCoreMMO/OpenCoreMMO unit-testing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/OpenCoreMMO/OpenCoreMMO.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/unit-testing .claude/skills/unit-testing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "unit-testing" agent skill from https://github.com/OpenCoreMMO/OpenCoreMMO/tree/develop/.agents/skills/unit-testing into .claude/skills/unit-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-testing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/OpenCoreMMO/OpenCoreMMO/tree/develop/.agents/skills/unit-testingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add OpenCoreMMO/OpenCoreMMO --skill unit-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install OpenCoreMMO/OpenCoreMMO unit-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenCoreMMO/OpenCoreMMO.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/unit-testing .agents/skills/unit-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "unit-testing" agent skill from https://github.com/OpenCoreMMO/OpenCoreMMO/tree/develop/.agents/skills/unit-testing into .agents/skills/unit-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-testing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenCoreMMO/OpenCoreMMO --skill unit-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install OpenCoreMMO/OpenCoreMMO unit-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenCoreMMO/OpenCoreMMO.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/unit-testing .cursor/skills/unit-testing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "unit-testing" agent skill from https://github.com/OpenCoreMMO/OpenCoreMMO/tree/develop/.agents/skills/unit-testing into .cursor/skills/unit-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-testing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/OpenCoreMMO/OpenCoreMMO.git --path .agents/skills/unit-testing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add OpenCoreMMO/OpenCoreMMO --skill unit-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install OpenCoreMMO/OpenCoreMMO unit-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenCoreMMO/OpenCoreMMO.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/unit-testing .gemini/skills/unit-testing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "unit-testing" agent skill from https://github.com/OpenCoreMMO/OpenCoreMMO/tree/develop/.agents/skills/unit-testing into .gemini/skills/unit-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-testing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install OpenCoreMMO/OpenCoreMMO unit-testingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add OpenCoreMMO/OpenCoreMMO --skill unit-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/OpenCoreMMO/OpenCoreMMO.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/unit-testing .github/skills/unit-testing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "unit-testing" agent skill from https://github.com/OpenCoreMMO/OpenCoreMMO/tree/develop/.agents/skills/unit-testing into .github/skills/unit-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-testing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add OpenCoreMMO/OpenCoreMMO --skill unit-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install OpenCoreMMO/OpenCoreMMO unit-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/OpenCoreMMO/OpenCoreMMO.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/unit-testing .opencode/skills/unit-testing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "unit-testing" agent skill from https://github.com/OpenCoreMMO/OpenCoreMMO/tree/develop/.agents/skills/unit-testing into .opencode/skills/unit-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "unit-testing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
unit-testing- GitHub stars
- 481
- Token cost
- ~1.6k tokens
- SKILL.md length
- 430 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Write, fix, or review NeoServer unit tests using xUnit and FluentAssertions.
- The user wants to create new tests
- SKILL.md covers Quick Reference, Project-Specific Conventions, Helper Methods — Reusable… and Gotchas, plus 1 more section
- Calls dotnet
- Fix failing tests
What it does
Unit Testing is an agent skill from OpenCoreMMO/OpenCoreMMO. Write, fix, or review NeoServer unit tests using xUnit and FluentAssertions. Use this skill when the user wants to create new tests, fix failing tests, or review existing tests — even if they only say "add tests," "fix the test," or mention testing a domain entity (Player, Monster, Item, NPC, Tile), handler, game system, or server component. Covers test helpers, behavioral naming, xUnit traits, and the repository-only mocking policy.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires .NET 10 SDK and dotnet CLI. Designed for NeoServer project conventions.
It sits in Testing & QA, covering Unit testing. It works with .NET. The repository describes itself as: Modern MMORPG server emulator written in C. The licence is GPL-3.0.
When your agent uses it
- The user wants to create new tests
- Fix failing tests
- Review existing tests — even if they only say add tests
- Mention testing a domain entity (Player
Example prompts
- “add tests,”
- “fix the test,”
- “/unit-testing”
Requirements
- Compatibility (from SKILL.md): Requires .NET 10 SDK and dotnet CLI. Designed for NeoServer project conventions.
What it can do on your machine
Read from SKILL.md and the folder at commit 1d485f7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
dotnet
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires .NET 10 SDK and dotnet CLI. Designed for NeoServer project conventions.
From compatibility in the SKILL.md frontmatter.
Context cost
Unit Testing loads about 1.6k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 430 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from OpenCoreMMO/OpenCoreMMO at commit 1d485f7, republished under its GPL-3.0 licence (© OpenCoreMMO). 430 words, ~1,598 tokens.
Download SKILL.mdSave it as
.claude/skills/unit-testing/SKILL.md (or your agent's skills folder).- name
- unit-testing
- description
- Write, fix, or review NeoServer unit tests using xUnit and FluentAssertions. Use this skill when the user wants to create new tests, fix failing tests, or review existing tests — even if they only say "add tests," "fix the test," or mention testing a domain entity (Player, Monster, Item, NPC, Tile), handler, game system, or server component. Covers test helpers, behavioral naming, xUnit traits, and the repository-only mocking policy.
- compatibility
- Requires .NET 10 SDK and dotnet CLI. Designed for NeoServer project conventions.
Quick Reference
Workflow
- 1. Identify behavior — one behavior per test
- 2. Write the test using AAA structure with the template below
- 3. Use existing helpers (
PlayerTestDataBuilder,ItemTestDataBuilder,MapTestDataBuilder, etc.) instead of building from scratch - 4. Tag with trait:
[Trait("Category", "<value>")] - 5. Run:
dotnet test tests/<project> - 6. Fix any failures and re-run until green
Test Template
[Fact]
[Trait("Category", "<HappyPath|Validation|EdgeCase|ErrorCondition|Integration>")]
public void {Actor}_does_{something}_when_{condition}()
{
// Arrange
var player = PlayerTestDataBuilder.Build();
// ... use existing builders; mock only I*Repository
// Act
player.DoSomething();
// Assert
result.Should().Be(expected);
}Project-Specific Conventions
Test Framework & Mocking
- xUnit with FluentAssertions (
Should().BeTrue(),.BeEquivalentTo(), etc.) - Do NOT mock domain entities, services, or commands — use real implementations
- Only mock infrastructure interfaces:
I*Repository,IConnection,IEventAggregator - Use Moq for mocks when needed
Naming
{Actor}_does_{something}_when_{condition}Examples: Player_gets_disconnected_when_game_is_stopped, World_replaces_tile_when_new_tile_provided, Player_cannot_push_null_creature.
Test Isolation
Each [Fact] creates its own instances. Never share objects between tests — no static state, no class-level fixtures. Tests that need serialized execution use [ThreadBlocking].
Traits
Only [Trait("Category", "<value>")] is used. Valid values:
| Value | When to Use |
|---|---|
HappyPath | Core positive/expected behavior |
Validation | Input validation, null checks, rejection |
EdgeCase | Boundary conditions, corner cases |
ErrorCondition | Error state handling (login fails, etc.) |
Integration | Multi-component interaction (real objects, mock only repos) |
PathFinding | Pathfinding algorithm tests |
Proximity | Distance/proximity checks |
Tile | Tile occupation/state tests |
Custom Attributes
[SkipOnGitHubActionsFact]— skips test in CI (for tests needing real DB)[ThreadBlocking]— serializes test execution via semaphore
Helper Methods — Reusable Builders
All helpers live in tests/NeoServer.Domain.Tests/Helpers/ and use optional parameters with sensible defaults:
Core Builders
| Builder | Location | Key Method |
|---|---|---|
PlayerTestDataBuilder | Helpers/Player/ | Build(id, name, hp, mana, skills, inventoryMap, vocationType, ...) |
ItemTestDataBuilder | Helpers/ | CreateContainer(...), CreateCumulativeItem(...), CreateWeaponItem(...) (27 methods) |
MonsterTestDataBuilder | Helpers/ | Build(maxHealth, speed, isHostile, flags, ...) |
MapTestDataBuilder | Helpers/Map/ | Build(fromX, toX, fromY, toY, fromZ, toZ, ...) — rectangular grid |
NpcTestDataBuilder | Helpers/ | Build(name, npcType) |
InventoryTestDataBuilder | Helpers/Player/ | Build(player, inventoryMap, ...) |
PartyTestDataBuilder | Helpers/ | Build(partyInviteService, players) |
Show full SKILL.md (172 more words)Show less
Server Test Builders
Located in tests/NeoServer.Domain.Tests/Server/:
| Builder | Purpose |
|---|---|
GameServerTestBuilder | Creates IGameServer with map |
ItemTypeStoreTestBuilder | Creates ItemTypeStore from items |
ItemFactoryTestBuilder | Creates IItemFactory with type store |
DecayableItemManagerTestBuilder | Creates DecayableItemManager |
ScriptManagerTestBuilder | Creates IScriptManager |
ServerTestHelper | Starts game server threads |
TestSetup | Full DI container boot (in NeoServer.Server.Tests) |
Event Helpers
| Helper | Purpose |
|---|---|
EventAggregatorTestHelper | SetupEventAggregator<TEvent>(handler) — wires handler to fire on publish |
EventAssertHelper | Fluent extensions: WithArgs<T>(Expression) |
EventSubscriptionCleanUp | CleanUp<T>(eventName) — tears down subscriptions between tests |
Pattern
// Simple in-file helper
private static Location CreateLocation(ushort x = 100, ushort y = 100, byte z = 7)
=> new(x, y, z);
// Compose from existing builders
private static IPlayer CreatePlayerWithFullInventory()
{
var player = PlayerTestDataBuilder.Build();
var inventory = InventoryTestDataBuilder.Build(player);
return player;
}Gotchas
- Mock only infrastructure: Never mock domain entities (
IPlayer,IMonster,IItem), services, or commands — use real implementations. Only mockI*Repository,IConnection,IEventAggregator. - No shared state: Each
[Fact]must create everything from scratch. Static or class-level state causes test pollution. - One behavior per test: Multiple assertions for different behaviors belong in separate
[Fact]methods. - Always use FluentAssertions:
result.Should().BeTrue(), notAssert.True(result). - Handler null guards: Event handlers must guard with
if (@event is null) return;. - Builders are in Helpers/: Look in
tests/NeoServer.Domain.Tests/Helpers/for*TestDataBuilderclasses before writing new setup code. - Data-driven tests: Use
[InlineData]for simple cases,[MemberData]for complex parameter sets,[ClassData]for reusable data classes.
Running Tests
# All tests
dotnet test tests/
# Specific project
dotnet test tests/NeoServer.Domain.Tests
# Specific category
dotnet test tests/ --filter "Category=HappyPath"
# Code coverage
dotnet test tests/ --collect:"XPlat Code Coverage" --results-directory testresults
# Build before test
dotnet build src/Standalone --configuration Release© OpenCoreMMO, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/unit-testing of OpenCoreMMO/OpenCoreMMO.
Open the folder on GitHubat commit 1d485f7
Compare with similar skills
Unit Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Unit Testing this skillOpenCoreMMO/OpenCoreMMO | 481 | — | ~1.6k | Automated safety check: Pass | GPL-3.0 | |
| New Event Sourceaws/aws-lambda-dotnet | 1.7k | — | ~3k | Automated safety check: Pass | Apache-2.0 | |
| ScottPlot Test RunnerScottPlot/ScottPlot | 6.8k | — | ~308 | Automated safety check: Pass | MIT | |
| Aspire Integration TestingDevBetterCom/DevBetterWeb | 157 | 2 repos | ~2.3k | Automated safety check: Pass | None | |
| Vstest Build Testmicrosoft/vstest | 969 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Coverage Analysisrunceel/ReactiveProperty | 944 | — | ~5.9k | Automated safety check: Warn | MIT |
Similar skills
- Official
ScottPlot Test Runner
ScottPlot/ScottPlot
Run or add ScottPlot 5 tests. Use for unit-test and cookbook-test work; unless explicitly asked otherwise, restrict manual test execution to the Unit Tests…
Aspire Integration Testing
DevBetterCom/DevBetterWeb
Write integration tests using .NET Aspire's testing facilities with xUnit.
- Official
Vstest Build Test
microsoft/vstest
Build, test, and validate changes in the vstest repository. An agent skill from microsoft/vstest.
Coverage Analysis
runceel/ReactiveProperty
Automated, project-wide code coverage and CRAP (Change Risk Anti-Patterns) score analysis for .NET projects with existing unit tests.
Akka.NET Testing Patterns
Aaronontheweb/dotnet-skills
Shows how to test Akka.NET actors with Akka.Hosting.TestKit: swapping services for fakes, using TestProbes, and checking persistence, plus when the older TestKit still fits.
More from OpenCoreMMO/OpenCoreMMO
Functional Testing
OpenCoreMMO/OpenCoreMMO
Write, fix, or review NeoServer functional tests that start from the network handler and run against the real server stack.
Pull Request
OpenCoreMMO/OpenCoreMMO
Create a pull request for OpenCoreMMO following the project's PR template.
Code Review
OpenCoreMMO/OpenCoreMMO
Review pull requests and code changes for OpenCoreMMO against the project's architecture, conventions, and style defined in AGENTS.md.
Related
Works with
Categories
Questions about Unit Testing
What does Unit Testing do?
Write, fix, or review NeoServer unit tests using xUnit and FluentAssertions. Unit Testing is an agent skill from OpenCoreMMO/OpenCoreMMO. Write, fix, or review NeoServer unit tests using xUnit and FluentAssertions.
When should I use Unit Testing?
Unit Testing fits situations like: the user wants to create new tests; fix failing tests; review existing tests — even if they only say add tests; mention testing a domain entity (Player.
How do I install Unit Testing in Claude Code?
Run `npx skills add OpenCoreMMO/OpenCoreMMO --skill unit-testing -a claude-code`. Or copy the skill folder (.agents/skills/unit-testing in OpenCoreMMO/OpenCoreMMO) into .claude/skills/unit-testing in your project. Claude Code loads it when a task matches its description.
How do I install Unit Testing in Codex?
Run `npx skills add OpenCoreMMO/OpenCoreMMO --skill unit-testing -a codex`. Or copy the skill folder (.agents/skills/unit-testing in OpenCoreMMO/OpenCoreMMO) into .agents/skills/unit-testing in your project. Codex loads it when a task matches its description.
Can I use Unit Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OpenCoreMMO/OpenCoreMMO --skill unit-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/unit-testing, .gemini/skills/unit-testing, .github/skills/unit-testing and .opencode/skills/unit-testing in your project.
What does Unit Testing need to run?
Going by SKILL.md and its folder, Unit Testing needs the command-line tools its instructions call (dotnet). Compatibility (from SKILL.md): Requires .NET 10 SDK and dotnet CLI. Designed for NeoServer project conventions..
Does Unit Testing access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Unit Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Unit Testing use?
Unit Testing is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Unit Testing use?
About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Unit Testing?
Skills that share tags, products or a category with Unit Testing: New Event Source (aws/aws-lambda-dotnet, 1.7k stars), ScottPlot Test Runner (ScottPlot/ScottPlot, 6.8k stars), Aspire Integration Testing (DevBetterCom/DevBetterWeb, 157 stars) and Vstest Build Test (microsoft/vstest, 969 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Unit Testing?
OpenCoreMMO (a GitHub organization) maintains it in OpenCoreMMO/OpenCoreMMO, which has 481 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 22, 2026.
Source: OpenCoreMMO/OpenCoreMMO on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.