بنقرة واحدة
camel-debug
Ad-hoc troubleshooting for broken Camel routes outside of a pipeline run.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Ad-hoc troubleshooting for broken Camel routes outside of a pipeline run.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Design and plan Camel integrations through collaborative dialogue.
Internal reference skill — loaded by camel-brainstorm during flow design. Contains guides for component selection, EIP catalog, data formats, integration patterns, and design spec assembly. NOT user-invocable.
Execute an approved implementation plan with two-stage review.
Internal reference skill — loaded by camel-execute during implementation tasks. Contains guides for YAML generation, component loading, properties, Docker Compose, DataMapper, and route validation. NOT user-invocable.
Migrate an existing integration from another product to Apache Camel
Break a design spec into implementation tasks with wave analysis.
| name | camel-debug |
| description | Ad-hoc troubleshooting for broken Camel routes outside of a pipeline run. |
| user_invocable | false |
Diagnose and fix a broken Camel route using a structured STOP → PRESERVE → DIAGNOSE → FIX → GUARD workflow.
Announce: "Let me debug this using the camel-debug skill."
camel-verify handles this (dispatched by camel-execute)/camel-validate/camel-brainstorm/camel-plan or /camel-executeViolating the letter of these rules is violating the spirit of these rules.
.camel-kit/config.properties must exist (for runtime and version detection)| Guide | When to Load | Purpose |
|---|---|---|
guides/debug-workflow.md | Always | Full debugging workflow — STOP, PRESERVE, DIAGNOSE, FIX, GUARD |
camel-verify/guides/error-taxonomy.md | Always (reference) | Error classification tables — patterns, categories, fix actions |
Load these shared guides at workflow start:
shared/iron-laws.md — Iron Law 1 (MCP verification) applies during diagnosisshared/mcp-setup.md — MCP tool configuration for catalog queriesDiagnosis steps (Step 3 in the workflow) MUST run as subagents to keep diagnostic output out of the main context. Only the classification result and fix recommendation flow back to the main conversation.
| Subagent | Purpose | Input | Output |
|---|---|---|---|
| Route analyzer | Inspect route YAML for structural issues | Route file paths, error message | Structural findings list |
| MCP verifier | Verify components/endpoints against catalog | Component names from routes | Verification results (exists/missing/wrong options) |
| Log analyzer | Parse and classify error output | Raw log/stack trace text | Classified error with taxonomy match |