shironigun/claude-marketplace

A Claude Code **plugin marketplace** — a curated set of
QA- and release-engineering plugins (skills, agents, and MCP servers) you can install into Claude Code in
the terminal, the Claude desktop app, or the VS Code extension.
The flagship is **qa-engineering**: one AI orchestrator for the whole QA
loop — analyze a story → author & approve test cases → publish them to a Test Plan/Suite → generate API + UI
automation → turn a failing run into a filed bug — with **a human gate at every tracker write**.
> **Marketplace name:** shironigun · **Source:** shironigun/claude-marketplace (this repo)
> When you install a plugin you refer to it as ** @shironigun** (the @ uses the marketplace's
> registered name, not the GitHub path).
---
Quick start
New skills/agents load at the start of a session. If you installed mid-session, run /reload-plugins or
start a new session.
---
Install
A. Claude Code CLI (terminal)
Manage them:
**Scope:** add --scope project to an install to write the enable entry into the repo's committed
.claude/settings.json (so collaborators can install it too); --scope local keeps it to this repo for
just you. Default is --scope user.
**In a running session** the same operations are available as slash commands:
/plugin install … opens the plugin's details and asks you to pick a scope (user / project / local) before
it installs.
B. Claude desktop app (Code tab)
The desktop plugin browser installs **from marketplaces you've already added**, so add this marketplace once
from a terminal (step A above) — there is no documented GUI form for *adding* a marketplace. Then, in a
**local** session (not a cloud session):
1. Click the **+** button next to the prompt box → **Plugins**.
2. **Add plugin** → pick qa-engineering (or any plugin) from the list → choose a scope (your account /
this project / local-only).
3. Manage or remove later via **+** → **Plugins** → **Manage plugins**.
4. If new skills don't show up, type /reload-plugins in the prompt box, or start a new session.
> Plugins are not available in cloud or WSL sessions; use a native local session. (In the **VS Code**
> extension you can do everything from the prompt box: type /plugins → **Marketplaces** tab to add this
> marketplace, then the **Plugins** tab to install.)
C. From a local clone (offline / development)
A local-path marketplace is read in place (not copied). After you git pull, run /reload-plugins or start
a new session. Don't add both the GitHub copy and a local copy at once — both register as shironigun;
remove one first (claude plugin marketplace remove shironigun).
---
The plugins
| Plugin | Category | What it does |
|---|---|---|
| **qa-engineering** | testing | The whole QA loop in one orchestrator — story → cases → publish → automate → bug — human-gated; also teaches & reviews a framework. **Product-neutral.** |
| qa-toolkit | testing | Generic QA building blocks: author API/UI test cases, convert failures to bugs, push to your tracker. |
| api-testing | testing | API test-case authoring + Playwright/TypeScript script generation + bug triage. |
| ui-testing | testing | UI test-case authoring (ADO) + runnable Playwright UI script generation. |
| crm-bug-suite | bug-tracking | Files Bugs/Defects and ticket comments on a specific ADO project in a house style. |
| release-notes-suite | release-management | Two-stage release pipeline: harvest the engineering inventory → write audience-facing release notes. |
> Several plugins (api-testing, ui-testing, crm-bug-suite, release-notes-suite) are tailored to
> a specific product and Azure DevOps project; qa-toolkit and **qa-engineering** are product-neutral and
> work against whatever tracker/app you point them at. Install only what you need.