From weave
Checks the installation and configuration status of the Weave Claude Code plugin, diagnosing missing components, stale daemon configs, and setup issues.
How this skill is triggered — by the user, by Claude, or both
Slash command
/weave:weave-statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Check the current installation and configuration status of the Weave Claude Code plugin.
Check the current installation and configuration status of the Weave Claude Code plugin.
Run:
weave-claude-code status
Each status line indicates one of four states:
✓ — component is present and correctly configured✗ — component is missing or misconfigured (action required)⚠ — component is working but has drifted from current settings (action recommended)- — component is absent but not an error (e.g., daemon not yet started)Common issues and fixes:
| Symptom | Fix |
|---|---|
✗ Configuration: not found | Run /weave:weave-install to complete installation |
✗ CLI: not found in PATH | Run npm install -g weave-claude-code in a terminal |
✗ Weave project: not configured | Run /weave:weave-config set weave_project ENTITY/PROJECT |
⚠ Daemon is running an older config | A setting changed since the daemon started, so the live daemon is using stale config. Run weave-claude-code restart to apply the new settings. |
- Daemon socket: not running | Normal if no Claude Code session is active; daemon starts automatically on next hook event |
- Log file: not created yet | Normal before first session; no action needed |
Summarize the status to the user. If all required items are ✓, confirm the plugin is ready and sessions will be traced automatically. If any ✗ items exist, provide the specific fix steps. If a ⚠ warning appears, surface it explicitly and run the recommended fix command.
npx claudepluginhub wandb/weave-claude-code --plugin weaveGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.