Help us improve
Share bugs, ideas, or general feedback.
From metaswarm
Diagnoses metaswarm installation state, project configuration, and potential issues across Claude Code, Codex, and Gemini.
npx claudepluginhub dsifry/metaswarmHow this skill is triggered — by the user, by Claude, or both
Slash command
/metaswarm:statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate a diagnostic report of the metaswarm installation, project configuration, and potential issues across Claude Code, Codex, and Gemini. Useful for troubleshooting and verifying setup or migration.
Runs 11 categories of environment diagnostics to identify misconfigured providers, stale state, broken hooks, and other plugin issues before they surface in workflows.
Detects your project stack and interactively configures metaswarm, writes instruction files (AGENTS.md/CLAUDE.md/GEMINI.md), coverage thresholds, and command shims for pytest, vitest, jest, go, cargo.
Runs comprehensive diagnostics on Claude Code environment: plugins, settings, hooks, MCP servers. Identifies issues, supports --fix and --verbose.
Share bugs, ideas, or general feedback.
Generate a diagnostic report of the metaswarm installation, project configuration, and potential issues across Claude Code, Codex, and Gemini. Useful for troubleshooting and verifying setup or migration.
Run each check below and present results in a single formatted report. Detect the active platform first:
PLUGIN_ROOT or CODEX_HOME is present, .codex-plugin/plugin.json is the active manifest, or the user invoked $statusCLAUDE_PLUGIN_ROOT is present, .claude-plugin/plugin.json is the active manifest, or the user invoked $statusextensionPath is present, gemini-extension.json is the active manifest, or the user invoked $status.codex-plugin/plugin.json from the plugin root and report version.claude-plugin/plugin.json from the plugin root and report versiongemini-extension.json from the plugin root and report versionpackage.json at plugin root for versionPlugin version: UNKNOWN.metaswarm/project-profile.json exists in the working directorydistribution, metaswarm_version, language, framework, test_runnerProject setup: NOT CONFIGURED -- run $setupProject setup: NOT CONFIGURED -- run $setupProject setup: NOT CONFIGURED -- run $setupCodex
.codex-plugin/plugin.json exists in the plugin root~/.codex/config.toml for an enabled metaswarm@... plugin entry when accessible~/.codex/plugins/cache/ for .codex-plugin/plugin.json with "name": "metaswarm"localClaude Code
.claude-plugin/plugin.json exists in the plugin root~/.claude/plugins/cache/ for .claude-plugin/plugin.json with "name": "metaswarm"Gemini
gemini-extension.json exists in the plugin rootWhen checking a Claude project, check these files in .claude/commands/:
| Shim | Expected |
|---|---|
start-task.md | Routes to /metaswarm:start-task |
prime.md | Routes to /metaswarm:prime |
review-design.md | Routes to /metaswarm:review-design |
self-reflect.md | Routes to /metaswarm:self-reflect |
pr-shepherd.md | Routes to /metaswarm:pr-shepherd |
brainstorm.md | Routes to /metaswarm:brainstorm |
For each: report Present/Missing. If the file exists but does not contain "metaswarm" routing, flag as present (non-metaswarm content).
When checking a Codex project, report not applicable (Codex uses $skill-name invocation) instead of treating missing .claude/commands/ files as errors.
.claude/plugins/metaswarm/.claude-plugin/plugin.jsonDETECTED -- run $migrate~/.claude/plugins/cache/ and ~/.codex/plugins/cache/ for a directory containing .claude-plugin/plugin.json or .codex-plugin/plugin.json with "name": "beads"installed (standalone) -- metaswarm defers priming to BEADSnot separately installedbd CLIcommand -v bd && bd --version 2>/dev/null
not installed -- knowledge priming and self-reflect require bd. Core orchestration works without it.gtg CLIcommand -v gtg && gtg --help >/dev/null 2>&1
not installed -- pr-shepherd will fall back to manual gh checks..metaswarm/external-tools.yaml -- if absent: not configured (optional)command -v codex # Codex CLI
command -v gemini # Gemini CLI
Report per-tool: enabled (yes/no), status (available/not installed).
.coverage-thresholds.json -- if absent: not configurednode --version 2>/dev/null
not installed -- scripts/beads-*.ts require Node.js. Core orchestration works without it.## Metaswarm Status Report
| Component | Status |
|---|---|
| Active platform | Codex |
| Plugin version | 0.11.0 |
| Project setup | Configured (distribution: plugin) |
| Platform install | Codex plugin installed and enabled |
| Command shims | Not applicable (Codex uses $skill-name) |
| Legacy embedded plugin | Not detected |
| BEADS plugin | Not separately installed |
| bd CLI | Available (v0.5.2) |
| gtg CLI | Available |
| External tools | Codex: available, Gemini: not installed |
| Coverage thresholds | 100% (all categories) |
| Node.js | Available (v22.4.0) |
### Issues Found
- None
### Recommendations
- None
When issues are found:
### Issues Found
1. Legacy embedded plugin detected alongside marketplace plugin -- run `$migrate`
2. Codex plugin not installed from a marketplace -- install from `/plugins` after adding the marketplace
### Recommendations
1. Install `bd` CLI for knowledge priming and self-reflect
2. Install `gtg` for the fastest `$pr-shepherd` readiness checks
3. Configure external tools for cross-model review (`.metaswarm/external-tools.yaml`)
This skill is diagnostic-only and never fails fatally. If any individual check errors, report the failure for that check (for example, Plugin version: ERROR -- could not read plugin.json) and continue with remaining checks.