HDDS-15316. Add AGENTS.md and CLAUDE.md#10302
Conversation
Generated-by: Claude Code w/ Opus 4.7
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- Add CLAUDE.md to RAT exclusions (rat.sh would otherwise fail). - Trim inline submodule enumeration; point at pom.xml for full lists. - Reorder build commands to recommend `install` over `verify` for iterative dev. - Consolidate code-conventions and PR-workflow into one section pointing at CONTRIBUTING.md. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Point at pom.xml for groupId/artifactId/version instead of inlining 2.2.0-SNAPSHOT, which will drift on each release. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
| Useful flags (composable): | ||
| - `-DskipShade` — skip building the shaded Ozone FS jar (saves time; omit this flag if you need to run filesystem integration tests, which require the shaded jar) | ||
| - `-DskipRecon` — skip Recon Web UI (~2 min faster) | ||
| - `-DskipDocs` — skip Hugo docs build | ||
| - `-Pdist` — build the binary tarball under `hadoop-ozone/dist/target/` |
There was a problem hiding this comment.
We can prompt the model to use these options when building locally.
There was a problem hiding this comment.
Do you mean we should remove this section? Or keep it here
There was a problem hiding this comment.
Agent shall know what commands to execute to validate the changes, optional commands could confuse the agent.
There was a problem hiding this comment.
Sorry what I meant is we keep it, but we can specify in the markdown that we should use these options when building locally.
…d hints - Rename CLAUDE.md -> AGENTS.md (cross-tool convention per agents.md); add CLAUDE.md as a symlink so existing Claude Code users still work. - Drop Claude-specific intro; rewrite tool-agnostic. - Add Tech stack line (Java 8 / JDK21 runtime, Maven, JUnit 5, Hadoop RPC + gRPC over Protobuf, RocksDB, Ratis). - Recommend `-DskipShade -DskipRecon -DskipDocs` for iterative builds. - Add `Generated-by: Claude Code (Opus 4.7)` attribution per ASF generative-tooling policy. - RAT: add AGENTS.md alongside CLAUDE.md in rat-exclusions. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Per ASF generative-tooling policy, contributors should attribute non-trivial AI-generated content as `Generated-by: TOOL (MODEL)`. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
| @@ -0,0 +1,80 @@ | |||
| # AGENTS.md | |||
There was a problem hiding this comment.
it would be nice to add skills and rules files for Cursor:
https://cursor.com/docs/skills & https://cursor.com/docs/rules
There was a problem hiding this comment.
Yes, but I think we can address this in the future. I would prefer if we develop our own Ozone-related skills (e.g. Cassandra bug hunting skills apache/cassandra#4794 or backporting skills for release process) instead of using the generic skills like https://github.com/obra/superpowers / https://github.com/mattpocock/skills / https://github.com/addyosmani/agent-skills
And for skills, let's standardize to something like https://agentskills.io instead of Cursor specific formats.
I think using the AGENTS.md using Claude Code /init is not advisable. See https://www.humanlayer.dev/blog/writing-a-good-claude-md for the reasoning. Since AGENTS.md will be loaded for each session, it is important we get this right (otherwise it might be a regression). I would prefer if the creator can try using the AGENTS.md for a while (to do bug fixes, creating small to large features) and update based on their findings and shortcomings. This would increase the community confidence in these AGENTS.md Personally, these are the things I would add:
PTAL of these links I found, we can research on the Harness engineering best practices |
Generated-by: Claude Code w/ Opus 4.7
What changes were proposed in this pull request?
Init CLAUDE.md for ozone.
This can be considered a subtask of HDDS-15158
This is generated using
/initcommand in Claude Code. Using Opus 4.7 xhigh.Added checkstyle CI workflow in addition to the originally generated content.
Pls feel free to suggest new lines to be added to this md, or we can revise later on.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-15316
How was this patch tested?