Stats
Actions
Tags
From trabuco
Validate a Trabuco project's structural health. Runs the Trabuco doctor + interprets findings. Use when a project isn't building correctly, after a manual edit, or before committing significant changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/trabuco:doctorThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **Target project**: if no argument, assume current working directory. If the argument is a path, use it. Call `mcp__trabuco__get_project_info` first to confirm it's a Trabuco project.
Target project: if no argument, assume current working directory. If the argument is a path, use it. Call mcp__trabuco__get_project_info first to confirm it's a Trabuco project.
Run doctor: call mcp__trabuco__run_doctor. Capture the structured output — it includes per-module checks, dependency conflicts, missing artifacts, etc.
Interpret: don't dump the raw output. Group findings:
Fix proposals: for each critical, offer a concrete fix. If it's something Trabuco itself would regenerate correctly, suggest trabuco add or regenerating the affected artifacts. If it's user code (broken entity, missing import), point at the file.
Docker check (if relevant): if the project uses Testcontainers and mcp__trabuco__check_docker reports it's not running, that's a critical finding for testing — flag it even if run_doctor didn't.
npx claudepluginhub arianlopezc/trabuco --plugin trabucoGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.