luigidemasi opened a new issue, #55: URL: https://github.com/apache/camel-kit/issues/55
> Imported from [luigidemasi/camel-kit#94](https://github.com/luigidemasi/camel-kit/issues/94), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-06-23. > Closed by commit [27f1d96](https://github.com/luigidemasi/camel-kit/commit/27f1d9655fca7a05bb81bbf8d9abe55fe41ffeb0). --- ## Description Camel-Kit generates a fairly rich agent workspace: command stubs, skills, MCP configs, `.camel-kit/config.properties`, graph files, templates, and docs. When something is misconfigured, users currently have to infer the problem from failed agent behavior or failed MCP calls. A diagnostic command would make setup issues easier to detect and fix. ## Proposed Solution Add a `camel-kit doctor` command that validates the generated workspace and reports actionable findings. Suggested checks: - `.camel-kit/config.properties` exists and contains expected keys - generated command directory exists for the selected agent - skill directories and `SKILL.md` files exist - only intended skills are user-invocable - MCP config exists for the selected agent - generated MCP tool allowlists match implemented server tools - `.camel-kit/project-graph.json` exists or graph generation can run - command prefix in config matches the installed invocation style - Java/Maven/JBang prerequisites are available where required - common stale-resource references are absent from active generated files ## Expected Behavior Users and contributors can run one command to verify whether a project was initialized correctly. ## Acceptance Criteria - [ ] Add `camel-kit doctor` Picocli command - [ ] Print PASS/WARN/FAIL findings with actionable remediation text - [ ] Support JSON output for automation - [ ] Cover generated workspace, MCP config, skills, config properties, graph, and prerequisites - [ ] Add unit tests for healthy and intentionally broken workspaces -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
