yihua opened a new pull request, #20448:
URL: https://github.com/apache/hudi/pull/20448

   ### Describe the issue this Pull Request addresses
   
   closes #20447, part of #20446
   
   Coding agents working on Hudi keep rediscovering the same project-specific 
traps: which JDK and profiles each branch needs, tests that pass without 
reproducing the bug, and PR checks that reject the title, template, or a 
co-author trailer.
   
   ### Summary and Changelog
   
   Adds 11 Claude Code skills under `.claude/skills/` that load automatically 
in an `apache/hudi` checkout. `/start-dev` drives a change from intake to a 
draft PR by routing through the others: `build-hudi`, `author-changes`, 
`develop-changes`, `review-pr` (with the committer rubric and invariant 
checklist distilled from the public review history), `pr-correctness-review`, 
`port-fixes` (`master` and `branch-0.x`), `prove-performance` (with its 
benchmark helper scripts), `create-pr`, `quiet-build`, and `manage-agents`. 
`.gitignore` now tracks `.claude/skills/` while still ignoring the rest of 
`.claude/` and `CLAUDE.md`.
   
   These complement `hudi-ai-operator`, which is for operating Hudi tables 
rather than developing Hudi. #18338 is a separate, earlier draft with a 
different set of skills.
   
   ### Impact
   
   None on Hudi itself. Contributors using Claude Code get the skills when 
working in the repo.
   
   ### Risk Level
   
   none
   
   ### Documentation Update
   
   none; `.claude/skills/README.md` lists the skills.
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Enough context is provided in the sections above
   - [ ] Adequate tests were added if applicable
   


-- 
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]

Reply via email to