luigidemasi opened a new issue, #56: URL: https://github.com/apache/camel-kit/issues/56
> Imported from [luigidemasi/camel-kit#95](https://github.com/luigidemasi/camel-kit/issues/95), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-06-23. > Closed by [luigidemasi/camel-kit#99](https://github.com/luigidemasi/camel-kit/pull/99), merged on 2026-06-23. --- ## Description After `camel-kit init`, the CLI prints next steps that are stale relative to the current skill architecture. Current output still suggests: - `/camel-design` - `/camel-verify` The current workflow routes users through `/camel-start`, and `/camel-verify` is mostly an internal verification skill invoked by `/camel-execute`. Relevant code: - `camel-kit-core/src/main/java/io/github/luigidemasi/camelkit/command/InitCommand.java` ## Steps to Reproduce 1. Run `camel-kit init <project>`. 2. Inspect the printed "Next steps" section. ## Expected Behavior The init summary should point users to the current supported entrypoint and workflow, for example: - open the project in the selected agent - run `/camel-start` for integration work - optionally use `/camel-migrate`, `/camel-knowledge`, or `/camel-debug` for direct workflows ## Actual Behavior The init summary still references older commands. ## Acceptance Criteria - [x] Update `InitCommand` next-step output to use `/camel-start` - [x] Remove `/camel-design` from user-facing next steps - [x] Avoid presenting `/camel-verify` as the primary standalone troubleshooting command if `/camel-debug` is now the preferred path - [x] Add or update tests that assert the generated next-step text uses current commands -- 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]
