andygrove opened a new issue, #5592:
URL: https://github.com/apache/datafusion-comet/issues/5592
## What is the problem the feature request solves?
Comet's agent skills live under `.claude/skills/`. The skills themselves are
vendor-neutral
Markdown -- there is nothing Claude-specific in their content -- but the
directory name ties a
shared project asset to one LLM vendor.
Both `apache/datafusion` and `apache/datafusion-python` have already moved
to a vendor-neutral
layout:
| | `apache/datafusion` | `apache/datafusion-python` |
|---|---|---|
| Skills | `.ai/skills/<name>/SKILL.md` | `.ai/skills/<name>/SKILL.md` |
| `.claude/skills` | (absent) | symlink to `../.ai/skills` |
| `CLAUDE.md` | symlink to `AGENTS.md` | symlink to `AGENTS.md` |
## Describe the potential solution
Adopt the same layout as the sibling repos:
- Move `.claude/skills` to `.ai/skills`.
- Keep `.claude/skills` as a symlink to `../.ai/skills`, so agents that only
look in the
vendor-specific location still discover the skills with no contributor
setup.
- Add a `CLAUDE.md` symlink to the existing `AGENTS.md`, which is already
the vendor-neutral
agent guide but does not currently mention skills at all.
- Update the RAT excludes in `pom.xml`.
One migration note for contributors: `CLAUDE.md` is currently in
`.gitignore` so that personal
untracked instruction files can live at the repo root. Tracking a
`CLAUDE.md` symlink means
dropping that entry, and anyone holding a personal root `CLAUDE.md` will hit
a checkout conflict
on pull and will need to move or delete it. Both sibling repos accepted the
same tradeoff.
## Additional context
None.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
