luigidemasi opened a new issue, #61: URL: https://github.com/apache/camel-kit/issues/61
> Imported from [luigidemasi/camel-kit#105](https://github.com/luigidemasi/camel-kit/issues/105), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-06-25. > Closed by [luigidemasi/camel-kit#112](https://github.com/luigidemasi/camel-kit/pull/112), merged on 2026-06-25. --- ## Description Much of Camel-Kit's runtime behavior lives in Markdown skills, guide files, dispatch templates, trait files, and generated instruction templates. These assets are effectively source code. The current tests catch some stale contract tokens and frontmatter drift, but they do not fully validate the structure of shipped assets. Relevant files: - `camel-kit-core/src/main/resources/skills/` - `camel-kit-core/src/main/resources/templates/` - `camel-kit-core/src/main/resources/workflow/camel-kit-workflow.yaml` - `camel-kit-core/src/test/java/io/github/luigidemasi/camelkit/generator/ResourceConsistencyTest.java` - `camel-kit-core/src/test/java/io/github/luigidemasi/camelkit/workflow/WorkflowManifestTest.java` ## Expected Behavior Tests should validate that shipped skill/template assets are structurally coherent. Recommended checks: - every skill in the workflow manifest has a corresponding `skills/<name>/SKILL.md` - every guide listed in a `SKILL.md` guide table exists - every shared guide reference points to an existing file - every dispatch template expected by a supported agent exists - every trait file targets an existing skill or guide - every generated command stub points to an existing copied skill - MCP config templates render valid JSON for every supported agent - agent-specific command templates do not drift from manifest command names ## Additional Context This should be implemented as targeted tests, not as another broad recursive content scan. Avoid scanning ignored or historical documents. A good place to add this is a new test class such as `ShippedAssetStructureTest`, keeping stale token checks in `ResourceConsistencyTest`. ## Acceptance Criteria - Add structural tests for skill guide references, trait targets, dispatch templates, and MCP config rendering. - Tests fail with precise file paths and missing reference names. - Tests do not scan historical or ignored local docs. - Existing resource consistency tests continue to pass. - Documentation is updated if the tested asset contract changes. ## Validation Run: `./mvnw -pl camel-kit-core -Dtest='ResourceConsistencyTest,WorkflowManifestTest,*Asset*Test' test -Dformat.skip=true` -- 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]
