{"owner":"apache","repo":"cassandra","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Agent Instructions for Apache Cassandra\n\n> These instructions apply to all AI-assisted contributions to `apache/cassandra`.\n\n## Apache Cassandra\nApache Cassandra is a NoSQL distributed database. This is the official Git repository.\n\n## Environment\n\n- Java 11 (default), 17, 21.\n- Python 3 for `cqlsh` and dtests.\n- Apache Ant >= 1.10 for all builds. Do NOT attempt to use Maven, Gradle, or any other build tool. Cassandra uses Ant exclusively.\n- Do NOT attempt to install dependencies, every dependency requires OSS community approval first.\n\n## Build\n\n```bash\n.build/sh/ai-build       # clean, build JAR, and run checkstyle (output is summarized)\n```\n\nDo NOT call `ant` directly — always use the `ai-*` wrapper scripts which handle log summarization and correct working directory.\n\n## Testing\n\n- Do NOT run the entire test suite. Run only the specific test(s) relevant to your change.\n\n    ```bash\n    # Run a single unit test class\n    .build/sh/ai-ci-test org.apache.cassandra.service.StorageServiceServerTest\n    ```\n\n- `ai-ci-test` does NOT support method-level filtering — it runs the entire test class.\n- When fixing a bug, first create a regression test that reproduces the failure, then implement the fix and verify.\n- Provide test(s) coverage for all new or modified code.\n\n## Linting and Code Checks\n\n`.build/sh/ai-build` includes checkstyle validation. There is no need to run checkstyle separately.\n\n## Code Style\nCassandra enforces style via Checkstyle (run via `.build/sh/ai-build`). The official style guide is at https://cassandra.apache.org/_/development/code_style.html. Always defer to it when in doubt.\n\nGeneral style conventions:\n- 4-space indentation, no tabs.\n- Match existing code style in the file you are editing.\n- All new files must include the Apache License 2.0 header.\n- Concise English documentation is required for complex classes and methods; trivial ones may not require them.\n\n## Git Workflow\n- Do NOT commit unless explicitly asked.\n- Commit messages format. For example:\n\n    ```\n    <One sentence description, usually Jira title or CHANGES.txt summary>\n\n    <Optional lengthier description>\n  \n    Assisted-by: AGENT_NAME:MODEL_VERSION\n    ```\n\n\n## Boundaries\n\n- 🚫 Never modify generated files in `src/gen-java/` — they are built from `src/antlr/` grammars.\n- 🚫 Never modify files in `lib/` — these are managed dependencies.\n- 🚫 Never commit secrets, credentials, or API keys.\n- 🚫 Never run the full test suite — it takes hours. Run targeted tests only.\n- 🚫 Never bypass Checkstyle violations without a suppression comment explaining why.\n- ⚠️ Ask before modifying the CQL grammar (`src/antlr/Cql.g`) — changes cascade widely.\n\n## Security\n\nSecurity model: [SECURITY.md](./SECURITY.md), which links to the project's\nsecurity model at\n[doc/modules/cassandra/pages/reference/security-model.adoc](./doc/modules/cassandra/pages/reference/security-model.adoc).\n\nAutomated agents (security scanners, code analyzers) that scan this\nrepository should consult that security model for the project's in-scope /\nout-of-scope declarations, trust boundaries, the security properties\nCassandra provides and disclaims, and how findings are triaged, before\nreporting issues.\n"},"files":{"AGENTS.md":"# Agent Instructions for Apache Cassandra\n\n> These instructions apply to all AI-assisted contributions to `apache/cassandra`.\n\n## Apache Cassandra\nApache Cassandra is a NoSQL distributed database. This is the official Git repository.\n\n## Environment\n\n- Java 11 (default), 17, 21.\n- Python 3 for `cqlsh` and dtests.\n- Apache Ant >= 1.10 for all builds. Do NOT attempt to use Maven, Gradle, or any other build tool. Cassandra uses Ant exclusively.\n- Do NOT attempt to install dependencies, every dependency requires OSS community approval first.\n\n## Build\n\n```bash\n.build/sh/ai-build       # clean, build JAR, and run checkstyle (output is summarized)\n```\n\nDo NOT call `ant` directly — always use the `ai-*` wrapper scripts which handle log summarization and correct working directory.\n\n## Testing\n\n- Do NOT run the entire test suite. Run only the specific test(s) relevant to your change.\n\n    ```bash\n    # Run a single unit test class\n    .build/sh/ai-ci-test org.apache.cassandra.service.StorageServiceServerTest\n    ```\n\n- `ai-ci-test` does NOT support method-level filtering — it runs the entire test class.\n- When fixing a bug, first create a regression test that reproduces the failure, then implement the fix and verify.\n- Provide test(s) coverage for all new or modified code.\n\n## Linting and Code Checks\n\n`.build/sh/ai-build` includes checkstyle validation. There is no need to run checkstyle separately.\n\n## Code Style\nCassandra enforces style via Checkstyle (run via `.build/sh/ai-build`). The official style guide is at https://cassandra.apache.org/_/development/code_style.html. Always defer to it when in doubt.\n\nGeneral style conventions:\n- 4-space indentation, no tabs.\n- Match existing code style in the file you are editing.\n- All new files must include the Apache License 2.0 header.\n- Concise English documentation is required for complex classes and methods; trivial ones may not require them.\n\n## Git Workflow\n- Do NOT commit unless explicitly asked.\n- Commit messages format. For example:\n\n    ```\n    <One sentence description, usually Jira title or CHANGES.txt summary>\n\n    <Optional lengthier description>\n  \n    Assisted-by: AGENT_NAME:MODEL_VERSION\n    ```\n\n\n## Boundaries\n\n- 🚫 Never modify generated files in `src/gen-java/` — they are built from `src/antlr/` grammars.\n- 🚫 Never modify files in `lib/` — these are managed dependencies.\n- 🚫 Never commit secrets, credentials, or API keys.\n- 🚫 Never run the full test suite — it takes hours. Run targeted tests only.\n- 🚫 Never bypass Checkstyle violations without a suppression comment explaining why.\n- ⚠️ Ask before modifying the CQL grammar (`src/antlr/Cql.g`) — changes cascade widely.\n\n## Security\n\nSecurity model: [SECURITY.md](./SECURITY.md), which links to the project's\nsecurity model at\n[doc/modules/cassandra/pages/reference/security-model.adoc](./doc/modules/cassandra/pages/reference/security-model.adoc).\n\nAutomated agents (security scanners, code analyzers) that scan this\nrepository should consult that security model for the project's in-scope /\nout-of-scope declarations, trust boundaries, the security properties\nCassandra provides and disclaims, and how findings are triaged, before\nreporting issues.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Agent Instructions for Apache Cassandra\n\n> These instructions apply to all AI-assisted contributions to `apache/cassandra`.\n\n## Apache Cassandra\nApache Cassandra is a NoSQL distributed database. This is the official Git repository.\n\n## Environment\n\n- Java 11 (default), 17, 21.\n- Python 3 for `cqlsh` and dtests.\n- Apache Ant >= 1.10 for all builds. Do NOT attempt to use Maven, Gradle, or any other build tool. Cassandra uses Ant exclusively.\n- Do NOT attempt to install dependencies, every dependency requires OSS community approval first.\n\n## Build\n\n```bash\n.build/sh/ai-build       # clean, build JAR, and run checkstyle (output is summarized)\n```\n\nDo NOT call `ant` directly — always use the `ai-*` wrapper scripts which handle log summarization and correct working directory.\n\n## Testing\n\n- Do NOT run the entire test suite. Run only the specific test(s) relevant to your change.\n\n    ```bash\n    # Run a single unit test class\n    .build/sh/ai-ci-test org.apache.cassandra.service.StorageServiceServerTest\n    ```\n\n- `ai-ci-test` does NOT support method-level filtering — it runs the entire test class.\n- When fixing a bug, first create a regression test that reproduces the failure, then implement the fix and verify.\n- Provide test(s) coverage for all new or modified code.\n\n## Linting and Code Checks\n\n`.build/sh/ai-build` includes checkstyle validation. There is no need to run checkstyle separately.\n\n## Code Style\nCassandra enforces style via Checkstyle (run via `.build/sh/ai-build`). The official style guide is at https://cassandra.apache.org/_/development/code_style.html. Always defer to it when in doubt.\n\nGeneral style conventions:\n- 4-space indentation, no tabs.\n- Match existing code style in the file you are editing.\n- All new files must include the Apache License 2.0 header.\n- Concise English documentation is required for complex classes and methods; trivial ones may not require them.\n\n## Git Workflow\n- Do NOT commit unless explicitly asked.\n- Commit messages format. For example:\n\n    ```\n    <One sentence description, usually Jira title or CHANGES.txt summary>\n\n    <Optional lengthier description>\n  \n    Assisted-by: AGENT_NAME:MODEL_VERSION\n    ```\n\n\n## Boundaries\n\n- 🚫 Never modify generated files in `src/gen-java/` — they are built from `src/antlr/` grammars.\n- 🚫 Never modify files in `lib/` — these are managed dependencies.\n- 🚫 Never commit secrets, credentials, or API keys.\n- 🚫 Never run the full test suite — it takes hours. Run targeted tests only.\n- 🚫 Never bypass Checkstyle violations without a suppression comment explaining why.\n- ⚠️ Ask before modifying the CQL grammar (`src/antlr/Cql.g`) — changes cascade widely.\n\n## Security\n\nSecurity model: [SECURITY.md](./SECURITY.md), which links to the project's\nsecurity model at\n[doc/modules/cassandra/pages/reference/security-model.adoc](./doc/modules/cassandra/pages/reference/security-model.adoc).\n\nAutomated agents (security scanners, code analyzers) that scan this\nrepository should consult that security model for the project's in-scope /\nout-of-scope declarations, trust boundaries, the security properties\nCassandra provides and disclaims, and how findings are triaged, before\nreporting issues.\n","category":"root","tokens":802}]}