메뉴
Install a Claude Code plugin and register it in settings.json so the full team can replicate the install. Use this whenever adding a new plugin to the project — it keeps settings.json in sync with what is actually installed.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
| name | add-plugin |
| description | Install a Claude Code plugin and register it in settings.json so the full team can replicate the install. Use this whenever adding a new plugin to the project — it keeps settings.json in sync with what is actually installed. |
| argument-hint | <name@marketplace> [--repo <owner/repo>] |
| user-invocable | true |
| allowed-tools | Read, Edit, Bash |
Role: implementation. This skill installs a Claude Code plugin and
adds it to .claude/settings.json so the project's plugin set is
reproducible.
You have been invoked with the /add-plugin skill.
name@marketplace
format encodes both; never ask the user to repeat information
already in the argument.Arguments: $ARGUMENTS
Required: plugin identifier ($0) in name@marketplace format —
e.g. skill-creator@claude-plugins-official or refactoring@refactoring.
Optional:
--repo <owner/repo>: GitHub repository to register as the
marketplace source before installing (e.g. elifiner/refactoring).
Required for plugins not on an official marketplace.Extract:
NAME — the part before @ in $0MARKETPLACE — the part after @ in $0REPO — value of --repo, or empty string if not providedRead .claude/settings.json. If enabledPlugins already contains
"<NAME>@<MARKETPLACE>": true, report:
<NAME>@<MARKETPLACE> is already registered in settings.json. Nothing to do.
and stop.
If REPO is non-empty, run:
claude plugin marketplace add <REPO>
If this fails, report the error and stop.
Run:
claude plugin install <NAME>@<MARKETPLACE>
If this fails, report the error and stop — do not update settings.json for a plugin that did not install successfully.
Add to the enabledPlugins object in .claude/settings.json:
"<NAME>@<MARKETPLACE>": true
If a --repo was provided, also add to extraKnownMarketplaces:
"<MARKETPLACE>": {
"source": {
"source": "github",
"repo": "<REPO>"
}
}
Installed: <NAME>@<MARKETPLACE>
Repo: <REPO or "official marketplace">
settings.json: updated
Validate test suite quality by running a real mutation testing tool and triaging surviving mutants. Use after writing tests to verify assertions catch behavioral changes, when evaluating test coverage quality, or as a CI quality gate on critical modules. The AI value here is triage — classifying survivors, writing fix tests — not generating or estimating mutations.
General-purpose analyze-then-improve test workflow for any JS/TS, Go, Java, or C# codebase. A 4-phase orchestrator: analyze with /test-health, optionally derive Gherkin with /gherkin-derive, triage into work items, implement each Story with /build + /coverage-delta + the mutation-kill agent, and validate with /quality-targets-converge. Local-first, BDD optional, Go-aware. Use when the user says "upgrade our tests", "improve test quality", or runs /test-upgrade. Lighter and general-purpose where /test-modernize is a brownfield legacy rescue.
Frontend component architecture review — dispatch the component-architecture-review agent over the frontend component files to catch reusable components that should be extracted, duplicated UI patterns, prop drilling, component-granularity problems, and inconsistent component APIs as a frontend evolves. Use when the user says "review the frontend architecture", "are my components reusable", "is this UI duplicated", "should this be a shared component", "check for prop drilling", or before extracting a component library. Advisory — it recommends, it does not edit.
Run eval fixtures against review agents and grade results. Use this after adding or modifying a review agent, to validate detection accuracy, or when the user says "run the evals", "test the agents", "check for regressions", or "how accurate is the agent".
Run all enabled review agents against target files. Use this whenever the user asks for a code review, wants feedback on their code, says "review my code", "check this before I PR", "what's wrong with this", "run the agents", or has just finished implementing a feature. Use proactively before commits and pull requests.
Charter-driven exploratory testing of a running feature or endpoint. Dispatches the QA Engineer in "Chaos Specialist" mode to probe with structured heuristics (Goldilocks, Happy-Path Divergence, Telemetry Deepening, Invariant Probing, CRUD Sweep), run adversarial expansion, and auto-triage critical defects into an incremental report. Use when the user says "explore this endpoint", "poke at this feature", or wants hands-off exploratory testing of a live target.