Menu
Report the installed version of the dev-team plugin.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Build a xunit.v2 Stryker shim so Stryker.NET produces a valid mutation score for a xunit.v3 test project. Stryker.NET cannot observe mutant kills through xunit.v3 (it runs on the Microsoft Testing Platform), so a normal run reports a false near-zero score with almost every mutant reported Survived. Use this BEFORE running Stryker whenever the target .NET test project references xunit.v3 — including when mutation is enabled via /test-improve or /mutation-testing, or you are about to run dotnet-stryker — and as a rescue when a run already reported ~0% or everything Survived or the user says the score looks suspiciously low. When Stryker and xunit.v3 both appear, build the shim first.
List the main dev-team workflows, with an option to show every user-invocable slash command.
Audit code-review agents, skills, and hooks for structural compliance. Use this when adding or modifying any agent, skill, or hook file, or for a periodic health check of the toolkit. Trigger phrases: "audit the agents", "check compliance", "validate the skills", "are the agents correct", or any time agent/skill files change.
Orchestrate a bounded round of automated issue processing: reclaim orphaned in-progress issues, discover eligible `autoship:ready` issues, and invoke `/ship` sequentially for each — stopping at cost or count caps and surfacing blocked items without halting the round. Requires `--max-issues` and `--max-cost-usd`. Use when you want a self-contained automated delivery round driven from the issue tracker.
Flag production files that churn repeatedly while their paired test files do not change — the "Red Queen" co-evolution gap. Uses git log --stat to compute per-file change frequency over a configurable window, applies language-aware pairing heuristics (Python, JS/TS, Go, Java, C#), and produces a ranked table of stale-coverage pairs. Feeds test-health and test-improve as prioritization input, not a standalone gate. Use when you want to find high-churn files whose tests have gone stale, or before running /test-improve to identify the highest- leverage targets first.
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.
Basé sur la classification professionnelle SOC
| name | version |
| description | Report the installed version of the dev-team plugin. |
| user-invocable | true |
| allowed-tools | Bash |
Role: worker. This command reports the installed plugin version. It is a purely mechanical lookup — no reasoning, no file-by-file searching.
You have been invoked with the /version command.
Arguments: none.
Run the resolver and report its output verbatim:
sh "$CLAUDE_PLUGIN_ROOT/hooks/py.sh" "$CLAUDE_PLUGIN_ROOT/hooks/lib/plugin_version.py"
Invoking through hooks/py.sh (not python3 directly) is what lets this work
on Windows, where Python 3 is often installed as python/py and no
python3 is on PATH. The shim resolves a real interpreter or exits 2.
The script reads ~/.claude/plugins/installed_plugins.json (Claude Code's
install record) and resolves the version deterministically: a project-scoped
install for the current directory wins; otherwise it falls back to the
user-scoped install. It prints a single line, e.g.:
dev-team@bfinster v6.7.0 (scope: user)
dev-team is not installed (no record in installed_plugins.json).python3, or the install record is
missing); surface the script's stderr message verbatim.Do not add commentary beyond the single result line.