Skip to content

About

Claude command that finds high risk untested methods, write mutation-validated xUnit test, reviews it, commits, opens PR.

Resources

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

51 Commits

Folders and files

Repository files navigation

NimblePros Claude Code Plugins

A marketplace of Claude Code plugins authored, curated, and/or edited by the NimblePros team. Add the marketplace once, then install only the plugins you want.

claude plugin marketplace add NimblePros/claude-plugins
claude plugin install dotnet-testing@nimblepros

Plugins

Plugin Install What you get
dotnet claude plugin install dotnet@nimblepros C#/.NET practice: coding standards, package management, Options/DI patterns, OpenTelemetry, NuGet publishing
dotnet-testing claude plugin install dotnet-testing@nimblepros The /dotnet-testing:add-coverage pipeline, CRAP analysis, Stryker.NET mutation testing, xUnit conventions, Aspire integration testing
playwright-testing claude plugin install playwright-testing@nimblepros Playwright E2E test authoring, design review, issue-repro reports, and refactoring generated .NET Playwright tests
architecture claude plugin install architecture@nimblepros ADR writing and technical documentation
workflow claude plugin install workflow@nimblepros Issue → spec → implementation → review → PR, over the gh CLI
presenting claude plugin install presenting@nimblepros Technical presentations: planning, storytelling, humor, code/diagram visuals, live demos, CFP abstracts, and reveal.js decks

Each plugin's README documents its skills, agents, commands, and requirements.


Installation

Option A — Claude Code plugin install (recommended)

claude plugin marketplace add NimblePros/claude-plugins
claude plugin install <plugin>@nimblepros

This installs that plugin's commands, agents, and skills into your global Claude Code configuration so they are available in every project you use on the current machine.

Option B — Per-project install via .claude/settings.json

Add the marketplace and the plugins you want to your project's .claude/settings.json so all collaborators get them when they trust the folder:

{
  "extraKnownMarketplaces": {
    "nimblepros": {
      "source": {
        "source": "github",
        "repo": "NimblePros/claude-plugins"
      }
    }
  },
  "enabledPlugins": {
    "dotnet-testing@nimblepros": true,
    "workflow@nimblepros": true
  }
}

Option C — Manual copy (standalone, no marketplace)

Copy a single plugin's contents into your project's .claude/ directory. Skills and commands are then available without namespacing (/add-coverage instead of /dotnet-testing:add-coverage):

# From your project root
gh repo clone NimblePros/claude-plugins /tmp/nimblepros-plugins
mkdir -p .claude
cp -r /tmp/nimblepros-plugins/plugins/dotnet-testing/commands .claude/
cp -r /tmp/nimblepros-plugins/plugins/dotnet-testing/agents .claude/
cp -r /tmp/nimblepros-plugins/plugins/dotnet-testing/skills .claude/

Commit the .claude/ directory so the whole team gets it.


Usage

When installed as a plugin, commands and skills are namespaced by the plugin name:

/dotnet-testing:add-coverage [optional: namespace or class name]
/workflow:review
/workflow:commit

When installed via Option C (standalone copy into .claude/), use the short form (/add-coverage, /review, /commit).


Migrating from the single nimblepros plugin

This repository previously published one plugin containing everything, installed as nimblepros@nimblepros. That plugin no longer exists. Claude Code v2.1.193 and later migrate automatically — the marketplace records the removal in its renames map, so the stale entry is dropped from your settings with a one-line notice. On earlier versions, or to pick your replacements explicitly:

claude plugin uninstall nimblepros@nimblepros
claude plugin marketplace update nimblepros
claude plugin install dotnet-testing@nimblepros   # plus any others you want

/nimblepros:add-coverage is now /dotnet-testing:add-coverage. The marketplace name is unchanged, so the marketplace itself does not need to be re-added. The rationale for the split is recorded in ADR 0001.


Repository layout

.
├── .claude-plugin/
│   └── marketplace.json          # catalog of the plugins below
├── plugins/
│   ├── dotnet/
│   │   ├── .claude-plugin/plugin.json
│   │   ├── README.md
│   │   ├── skills/
│   │   └── agents/
│   ├── dotnet-testing/
│   │   ├── .claude-plugin/plugin.json
│   │   ├── README.md
│   │   ├── commands/
│   │   ├── agents/
│   │   └── skills/
│   ├── playwright-testing/
│   ├── architecture/
│   ├── presenting/
│   └── workflow/
├── devdocs/
│   └── ADRs/                     # architecture decision records
├── scripts/
│   ├── ValidateMarketplace.cs    # structural validation (dotnet run scripts/ValidateMarketplace.cs)
│   └── validate_skills.py        # Agent Skills spec validation (needs skills-ref)
├── .github/workflows/
│   └── validate.yml              # runs every validator on push and PR
└── README.md

Contributing

  • New content goes in the plugin matching the capability it serves — not in a plugin grouped by artifact type. Skills, agents, and commands that work together ship together.
  • Language-specific guidance stays out of language-agnostic plugins, and vice versa.
  • A skill must ship in the same plugin as any agent or command that loads it; no plugin here depends on another being installed.
  • Keep each SKILL.md under ~500 lines, moving detail into supporting files so agents can skip loading what they don't need.
  • Structural decisions get an ADR in devdocs/ADRs/.

Validation

.github/workflows/validate.yml runs every validator below on each push and pull request. To get the same answer before opening a PR:

claude plugin validate . --strict                      # marketplace manifest schema
for p in plugins/*/; do claude plugin validate "$p" --strict; done
python scripts/validate_skills.py                      # every SKILL.md vs. the Agent Skills spec
dotnet run scripts/ValidateMarketplace.cs              # repository structure (needs the .NET 10 SDK)

Each covers a different layer: claude plugin validate checks manifest and frontmatter schema against the Claude Code runtime, validate_skills.py checks skills against the portable Agent Skills spec, and ValidateMarketplace.cs checks that the catalog, the manifests, and the on-disk layout agree.

validate_skills.py needs the reference validator, which is not on PyPI:

pip install "git+https://github.com/agentskills/agentskills.git#subdirectory=skills-ref"

ValidateMarketplace.cs is a file-based app — no project file, no restore, just run it.

About

Claude command that finds high risk untested methods, write mutation-validated xUnit test, reviews it, commits, opens PR.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages