TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
Guide for writing local unit tests for PACX commands without relying on external services.
$ npx skills add neronotte/Greg.Xrm.Command --skill pacx-unit-test-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install neronotte/Greg.Xrm.Command pacx-unit-test-writer --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/neronotte/Greg.Xrm.Command.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/pacx-unit-test-writer .claude/skills/pacx-unit-test-writer && 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 "pacx-unit-test-writer" agent skill from https://github.com/neronotte/Greg.Xrm.Command/tree/master/.github/skills/pacx-unit-test-writer into .claude/skills/pacx-unit-test-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pacx-unit-test-writer", 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/neronotte/Greg.Xrm.Command/tree/master/.github/skills/pacx-unit-test-writerType 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 neronotte/Greg.Xrm.Command --skill pacx-unit-test-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install neronotte/Greg.Xrm.Command pacx-unit-test-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neronotte/Greg.Xrm.Command.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/pacx-unit-test-writer .agents/skills/pacx-unit-test-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pacx-unit-test-writer" agent skill from https://github.com/neronotte/Greg.Xrm.Command/tree/master/.github/skills/pacx-unit-test-writer into .agents/skills/pacx-unit-test-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pacx-unit-test-writer", 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 neronotte/Greg.Xrm.Command --skill pacx-unit-test-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install neronotte/Greg.Xrm.Command pacx-unit-test-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neronotte/Greg.Xrm.Command.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/pacx-unit-test-writer .cursor/skills/pacx-unit-test-writer && 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 "pacx-unit-test-writer" agent skill from https://github.com/neronotte/Greg.Xrm.Command/tree/master/.github/skills/pacx-unit-test-writer into .cursor/skills/pacx-unit-test-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pacx-unit-test-writer", 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/neronotte/Greg.Xrm.Command.git --path .github/skills/pacx-unit-test-writer--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 neronotte/Greg.Xrm.Command --skill pacx-unit-test-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install neronotte/Greg.Xrm.Command pacx-unit-test-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neronotte/Greg.Xrm.Command.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/pacx-unit-test-writer .gemini/skills/pacx-unit-test-writer && 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 "pacx-unit-test-writer" agent skill from https://github.com/neronotte/Greg.Xrm.Command/tree/master/.github/skills/pacx-unit-test-writer into .gemini/skills/pacx-unit-test-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pacx-unit-test-writer", 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 neronotte/Greg.Xrm.Command pacx-unit-test-writerInstalls 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 neronotte/Greg.Xrm.Command --skill pacx-unit-test-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/neronotte/Greg.Xrm.Command.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/pacx-unit-test-writer .github/skills/pacx-unit-test-writer && 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 "pacx-unit-test-writer" agent skill from https://github.com/neronotte/Greg.Xrm.Command/tree/master/.github/skills/pacx-unit-test-writer into .github/skills/pacx-unit-test-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pacx-unit-test-writer", 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 neronotte/Greg.Xrm.Command --skill pacx-unit-test-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install neronotte/Greg.Xrm.Command pacx-unit-test-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/neronotte/Greg.Xrm.Command.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/pacx-unit-test-writer .opencode/skills/pacx-unit-test-writer && 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 "pacx-unit-test-writer" agent skill from https://github.com/neronotte/Greg.Xrm.Command/tree/master/.github/skills/pacx-unit-test-writer into .opencode/skills/pacx-unit-test-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pacx-unit-test-writer", 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.
pacx-unit-test-writerGuide for writing local unit tests for PACX commands without relying on external services.
Pacx Unit Test Writer is an agent skill from neronotte/Greg.Xrm.Command. Guide for writing local unit tests for PACX commands without relying on external services. Use this skill when asked to write, generate, or add unit tests for a PACX command class or executor. Tests produced by this skill are fully local — they never connect to Dataverse or any other external service.
Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Unit testing. The repository describes itself as: Command Line utility for Dataverse. The licence is MIT.
Read from SKILL.md and the folder at commit 236875d. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
dotnetFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pacx Unit Test Writer loads about 3.6k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 461 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.
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.
The full file from neronotte/Greg.Xrm.Command at commit 236875d, republished under its MIT licence (© neronotte). 461 words, ~3,618 tokens.
.claude/skills/pacx-unit-test-writer/SKILL.md (or your agent's skills folder).All tests live in Greg.Xrm.Command.Core.TestSuite\Commands\<Domain>\ and mirror the source layout under Greg.Xrm.Command.Core\Commands\<Domain>\.
Every command needs two test files:
| File | Tests |
|---|---|
<Verb>CommandTest.cs | CLI argument parsing — no DI, no Dataverse |
<Verb>CommandExecutorTest.cs | Executor logic — all dependencies mocked |
GlobalUsings.cs already imports Microsoft.VisualStudio.TestTools.UnitTesting, Greg.Xrm.Command.Services.Output, and Moq. Do not add redundant using statements for those.
Utility.TestParseCommand<T>(params string[] args)Parses a CLI argument array into a typed command instance. Use this for all parser tests.
var command = Utility.TestParseCommand<DeleteCommand>("table", "delete", "--name", "my_table");OutputToMemoryA concrete, in-memory IOutput implementation. Captures everything written to it.
output.ToString() returns the full captured text.<Green>Done</Green> — you can search for substrings.var output = new OutputToMemory();
// ... run executor ...
StringAssert.Contains(output.ToString(), "Done");Mock<IOutput>Use instead of OutputToMemory when you need to verify specific IOutput calls with Moq's Verify.
var mockOutput = new Mock<IOutput>();
mockOutput.Setup(o => o.Write(It.IsAny<object>())).Returns(mockOutput.Object);
mockOutput.Setup(o => o.WriteLine(It.IsAny<object>(), It.IsAny<ConsoleColor>())).Returns(mockOutput.Object);
// ...
mockOutput.Verify(o => o.WriteLine(
It.Is<string>(s => s.Contains("Table not found")),
It.IsAny<ConsoleColor>()), Times.Once);Rule of thumb: prefer
OutputToMemoryfor most tests; switch toMock<IOutput>only when you need to assert that a specific message was (or was not) written.
<Verb>CommandTest.cs (parser tests)Test every [Option] with both its long name and its short name. Also assert that default values and null optionals are set correctly when options are omitted.
namespace Greg.Xrm.Command.Commands.<Domain>
{
[TestClass]
public class <Verb>CommandTest
{
// ── Long-name parsing ──────────────────────────────────────────────────
[TestMethod]
public void ParseWithLongNameShouldWork()
{
var command = Utility.TestParseCommand<<Verb>Command>(
"<noun>", "<verb>",
"--name", "TestValue");
Assert.AreEqual("TestValue", command.Name);
}
// ── Short-name parsing ─────────────────────────────────────────────────
[TestMethod]
public void ParseWithShortNameShouldWork()
{
var command = Utility.TestParseCommand<<Verb>Command>(
"<noun>", "<verb>",
"-n", "TestValue");
Assert.AreEqual("TestValue", command.Name);
}
// ── Default values ─────────────────────────────────────────────────────
// When options with DefaultValue are omitted, assert the expected default.
// When optional options are omitted, assert null.
[TestMethod]
public void DefaultValuesShouldBeSetCorrectly()
{
var command = Utility.TestParseCommand<<Verb>Command>(
"<noun>", "<verb>",
"--name", "TestValue");
Assert.AreEqual(ExpectedDefaultForSomeOption, command.SomeOption);
Assert.IsNull(command.OptionalOption);
Assert.IsNull(command.SolutionName);
}
// ── Enum options ───────────────────────────────────────────────────────
[TestMethod]
public void EnumOptionShouldBeParsedCorrectly()
{
var command = Utility.TestParseCommand<<Verb>Command>(
"<noun>", "<verb>",
"--name", "TestValue",
"--ownership", "Organization");
Assert.AreEqual(OwnershipTypes.OrgOwned, command.Ownership);
}
// ── Boolean flags ──────────────────────────────────────────────────────
[TestMethod]
public void BoolFlagShouldDefaultToFalse()
{
var command = Utility.TestParseCommand<<Verb>Command>("<noun>", "<verb>", "--name", "v");
Assert.IsFalse(command.SomeFlag);
}
[TestMethod]
public void BoolFlagShouldBeParsedWhenProvided()
{
var command = Utility.TestParseCommand<<Verb>Command>(
"<noun>", "<verb>",
"--name", "v",
"--someFlag");
Assert.IsTrue(command.SomeFlag);
}
// ── Parameterised (use [DataRow] for multiple input variants) ──────────
[TestMethod]
[DataRow("--name", "v1")]
[DataRow("--otherName", "v2")]
public void AllNameAliasesShouldMapToSameProperty(string optionKey, string optionValue)
{
var command = Utility.TestParseCommand<<Verb>Command>("<noun>", "<verb>", optionKey, optionValue);
Assert.IsNotNull(command.Name);
}
}
}<Verb>CommandExecutorTest.cs (executor unit tests)using Greg.Xrm.Command.Services.Connection;
using Microsoft.PowerPlatform.Dataverse.Client;
using Microsoft.Xrm.Sdk;
using Microsoft.Xrm.Sdk.Messages;
namespace Greg.Xrm.Command.Commands.<Domain>
{
[TestClass]
public class <Verb>CommandExecutorTest
{
// Helper: builds mocks wired together the same way as the real DI chain.
private static (
OutputToMemory output,
Mock<IOrganizationServiceRepository> repoMock,
Mock<IOrganizationServiceAsync2> crmMock)
CreateMocks()
{
var output = new OutputToMemory();
var crmMock = new Mock<IOrganizationServiceAsync2>();
var repoMock = new Mock<IOrganizationServiceRepository>();
repoMock
.Setup(r => r.GetCurrentConnectionAsync())
.ReturnsAsync(crmMock.Object);
return (output, repoMock, crmMock);
}
}
}[TestMethod]
public async Task ExecuteAsync_ShouldSucceed_WhenInputIsValid()
{
// Arrange
var (output, repoMock, crmMock) = CreateMocks();
OrganizationRequest? capturedRequest = null;
crmMock
.Setup(c => c.ExecuteAsync(It.IsAny<OrganizationRequest>()))
.Callback<OrganizationRequest>(r => capturedRequest = r)
.ReturnsAsync(new <ExpectedResponseType>()); // e.g. DeleteEntityResponse
var executor = new <Verb>CommandExecutor(output, repoMock.Object);
// Act
var result = await executor.ExecuteAsync(
new <Verb>Command { Name = "some_value" },
CancellationToken.None);
// Assert — result
Assert.IsTrue(result.IsSuccess, result.ErrorMessage);
// Assert — Dataverse was called
repoMock.Verify(r => r.GetCurrentConnectionAsync(), Times.Once);
crmMock.Verify(c => c.ExecuteAsync(It.IsAny<<ExpectedRequestType>>()), Times.Once);
// Assert — request content
Assert.IsNotNull(capturedRequest);
var typedRequest = capturedRequest as <ExpectedRequestType>;
Assert.IsNotNull(typedRequest);
Assert.AreEqual("some_value", typedRequest./* relevant property */);
}[TestMethod]
public async Task ExecuteAsync_ShouldFail_WhenDataverseThrows()
{
// Arrange
var (output, repoMock, crmMock) = CreateMocks();
crmMock
.Setup(c => c.ExecuteAsync(It.IsAny<OrganizationRequest>()))
.ThrowsAsync(new System.ServiceModel.FaultException<Microsoft.Xrm.Sdk.OrganizationServiceFault>(
new Microsoft.Xrm.Sdk.OrganizationServiceFault(),
"Simulated Dataverse fault"));
var executor = new <Verb>CommandExecutor(output, repoMock.Object);
// Act
var result = await executor.ExecuteAsync(
new <Verb>Command { Name = "some_value" },
CancellationToken.None);
// Assert
Assert.IsFalse(result.IsSuccess);
Assert.IsFalse(string.IsNullOrWhiteSpace(result.ErrorMessage));
}[TestMethod]
public async Task ExecuteAsync_ShouldFail_WhenSolutionDoesNotExist()
{
// Arrange
var (output, repoMock, crmMock) = CreateMocks();
// Simulate empty result set for the pre-flight query
crmMock
.Setup(c => c.RetrieveMultipleAsync(It.IsAny<Microsoft.Xrm.Sdk.Query.QueryBase>()))
.ReturnsAsync(new Microsoft.Xrm.Sdk.EntityCollection()); // empty
var executor = new <Verb>CommandExecutor(output, repoMock.Object);
// Act
var result = await executor.ExecuteAsync(
new <Verb>Command { Name = "v", SolutionName = "nonexistent" },
CancellationToken.None);
// Assert
Assert.IsFalse(result.IsSuccess);
// The main operation must NOT have been called
crmMock.Verify(c => c.ExecuteAsync(It.IsAny<OrganizationRequest>()), Times.Never);
}[TestMethod]
public async Task ExecuteAsync_ShouldFail_WhenNoSolutionProvidedAndNoDefault()
{
// Arrange
var (output, repoMock, crmMock) = CreateMocks();
repoMock
.Setup(r => r.GetCurrentDefaultSolutionAsync())
.ReturnsAsync((string?)null);
var executor = new <Verb>CommandExecutor(output, repoMock.Object);
// Act
var result = await executor.ExecuteAsync(
new <Verb>Command { Name = "some_value" /* SolutionName intentionally omitted */ },
CancellationToken.None);
// Assert
Assert.IsFalse(result.IsSuccess);
crmMock.Verify(c => c.ExecuteAsync(It.IsAny<OrganizationRequest>()), Times.Never);
}When the executor depends on more services beyond IOrganizationServiceRepository, mock and inject them the same way:
var mockPluralization = new Mock<IPluralizationFactory>();
mockPluralization
.Setup(p => p.CreateFor(It.IsAny<int>()))
.Returns(Mock.Of<IPluralizationStrategy>(s =>
s.GetPluralForAsync(It.IsAny<string>()) == Task.FromResult("Values")));
var executor = new <Verb>CommandExecutor(output, repoMock.Object, mockPluralization.Object);[DataRow]Use [DataRow] when several input combinations should all produce the same outcome:
[TestMethod]
[DataRow("value_a", true)]
[DataRow("value_b", true)]
[DataRow(null, false)]
public async Task ExecuteAsync_ShouldReturnExpectedResult(string? inputName, bool expectSuccess)
{
var (output, repoMock, crmMock) = CreateMocks();
crmMock
.Setup(c => c.ExecuteAsync(It.IsAny<OrganizationRequest>()))
.ReturnsAsync(new OrganizationResponse());
var executor = new <Verb>CommandExecutor(output, repoMock.Object);
var result = await executor.ExecuteAsync(
new <Verb>Command { Name = inputName },
CancellationToken.None);
Assert.AreEqual(expectSuccess, result.IsSuccess);
}IValidatableObject.Validate() directlyWhen a command implements IValidatableObject, test Validate() in isolation — no parsing, no executor.
[TestMethod]
public void Validate_ShouldFail_WhenMutuallyExclusiveOptionsAreProvided()
{
var command = new <Verb>Command
{
OptionA = "value",
OptionB = "also-value" // these two cannot coexist
};
var context = new System.ComponentModel.DataAnnotations.ValidationContext(command);
var results = command.Validate(context).ToList();
Assert.AreEqual(1, results.Count);
CollectionAssert.Contains(results[0].MemberNames.ToList(), nameof(<Verb>Command.OptionA));
}
[TestMethod]
public void Validate_ShouldPass_WhenOnlyOneOptionIsProvided()
{
var command = new <Verb>Command { OptionA = "value" };
var context = new System.ComponentModel.DataAnnotations.ValidationContext(command);
var results = command.Validate(context).ToList();
Assert.AreEqual(0, results.Count);
}| ❌ Avoid | ✅ Do instead |
|---|---|
new OrganizationServiceRepository(...) in a unit test | new Mock<IOrganizationServiceRepository>() |
[TestCategory("Integration")] on a local test | Omit the category entirely |
task.Wait() | await executor.ExecuteAsync(...) |
Asserting only Assert.IsNotNull(output.ToString()) | Assert on result.IsSuccess, mock .Verify(), and request content |
| Real file I/O or environment variables | Mock the service that reads them |
new OutputToConsole() | new OutputToMemory() or new Mock<IOutput>() |
<Verb>CommandTest.cs covers every [Option] with long name and short namenull optionals are asserted when options are omittedfalse) and present (true)[DataRow] used for options that have multiple meaningful input variants<Verb>CommandExecutorTest.cs has a happy-path testresult.IsSuccess, verifies Dataverse was called, and inspects the captured requestFaultException<OrganizationServiceFault>)GetCurrentDefaultSolutionAsync()IValidatableObject.Validate() tested directly if the command implements itOrganizationServiceRepository or connects to Dataverse[TestCategory("Integration")]dotnet test Greg.Xrm.Command.Core.TestSuite\Greg.Xrm.Command.Core.TestSuite.csproj passes© neronotte, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .github/skills/pacx-unit-test-writer of neronotte/Greg.Xrm.Command.
Open the folder on GitHubat commit 236875d
Pacx Unit Test Writer 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 |
|---|---|---|---|---|---|---|
| Pacx Unit Test Writer this skillneronotte/Greg.Xrm.Command | 151 | — | ~3.6k | Automated safety check: Pass | MIT | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None | |
| Testing OpenLogi UIAprilNEA/OpenLogi | 23k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Go Testingcxuu/golang-skills | 173 | 1 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Contractssamchon/nestia | 2.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Cohesion Over TestabilityEpicenterHQ/epicenter | 4.8k | — | ~2k | Automated safety check: Pass | Custom licence |
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
AprilNEA/OpenLogi
Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.
cxuu/golang-skills
A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.
samchon/nestia
Defines self-acknowledgments for production declarations and tests.
EpicenterHQ/epicenter
Collapse test-shaped production boundaries while preserving behavior and coverage.
liaohch3/claude-tap
Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.
neronotte/Greg.Xrm.Command
Guide for writing new PACX CLI commands (verbs) following established project conventions.
Categories
Guide for writing local unit tests for PACX commands without relying on external services. Command. Guide for writing local unit tests for PACX commands without relying on external services.
Pacx Unit Test Writer fits situations like: add unit tests for a PACX command class; tasks that involve Unit testing.
Run `npx skills add neronotte/Greg.Xrm.Command --skill pacx-unit-test-writer -a claude-code`. Or copy the skill folder (.github/skills/pacx-unit-test-writer in neronotte/Greg.Xrm.Command) into .claude/skills/pacx-unit-test-writer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add neronotte/Greg.Xrm.Command --skill pacx-unit-test-writer -a codex`. Or copy the skill folder (.github/skills/pacx-unit-test-writer in neronotte/Greg.Xrm.Command) into .agents/skills/pacx-unit-test-writer in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add neronotte/Greg.Xrm.Command --skill pacx-unit-test-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pacx-unit-test-writer, .gemini/skills/pacx-unit-test-writer, .github/skills/pacx-unit-test-writer and .opencode/skills/pacx-unit-test-writer in your project.
Going by SKILL.md and its folder, Pacx Unit Test Writer needs the command-line tools its instructions call (dotnet).
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.
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.
Pacx Unit Test Writer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pacx Unit Test Writer: TDD Workflow (hellangleZ/burn-in-cceverywhere-ralph, 112 stars), Testing OpenLogi UI (AprilNEA/OpenLogi, 23k stars), Go Testing (cxuu/golang-skills, 173 stars) and Contracts (samchon/nestia, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
neronotte (a GitHub user) maintains it in neronotte/Greg.Xrm.Command, which has 151 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 4, 2026.
Source: neronotte/Greg.Xrm.Command on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.