AnKiT-GaRG2 opened a new pull request, #130:
URL: https://github.com/apache/camel-kit/pull/130
_AI-generated by Claude Sonnet 5.5 on behalf of @AnKiT-GaRG2._
Fixes #112
## Problem
Law 2 of the generated `AGENTS.md` (shared template) names
`shared/context-authority.md`, which does not exist from the project root. The
file is installed under the agent's skills directory, for example
`.opencode/skills/shared/context-authority.md`,
`.claude/skills/shared/context-authority.md` and
`.bob/skills/shared/context-authority.md`. An agent following Law 2 therefore
hits a file-not-found error.
## Change
- `AgentsMdGenerator` passes the skills directory, relative to the project
root, to the template as `SKILLS_DIR`. This is the same way `COMMAND_PREFIX` is
rendered.
- `templates/shared/agents-md.md` Law 2 now reads ``Under
`{SKILLS_DIR}/shared/context-authority.md` ``.
-
`DefaultGeneratorTest.agentsMdNamesContextAuthorityByAPathFromTheProjectRoot`
generates the project for every agent and asserts that each
`…/shared/context-authority.md` path named in `AGENTS.md` exists from the
project root.
This covers the first checkbox of the issue's proposal and a narrower form
of the second (only the context-authority path, not every path in `AGENTS.md`).
## Not changed
Other templates also name `shared/context-authority.md` without the skills
directory: `bob2/rules/iron-laws.md` and the dispatch and trait files such as
`dispatch/claude.md` and `traits/claude/camel-validate.append.md`. They are not
part of the generated `AGENTS.md`, so I left them for a follow-up rather than
widen this change. Happy to include them here if you prefer.
## Verification
- `./mvnw -pl camel-kit-core -am test`: 1283 tests, 0 failures, 1 skipped,
build success.
- The new test fails without the template change (`bob2: AGENTS.md names
shared/context-authority.md, which does not exist from the project root`) and
passes with it.
--
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]
