{"owner":"chroma-core","repo":"chroma","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md","CLAUDE.md"],"skills":{"AGENTS.md":"# Chroma Codebase Guidelines for AI Agents\n\nSee [CLAUDE.md](./CLAUDE.md) for codebase conventions (commit message format, etc.).\n","CLAUDE.md":"# Chroma Codebase Guidelines\n\n## Commit Message Style\n\nUse the `[TYPE](scope): Description` format:\n\n```\n[ENH](rust-client): Add retry middleware\n[BUG](rust-client): Fix connection timeout on retry\n[TST](gc): Add MCMR hard delete integration test\n[DOC](api): Update embeddings endpoint docs\n[CHORE](deps): Bump reqwest to 0.13\n```\n\nCommon types: `ENH` (feature/enhancement), `BUG` (fix), `TST` (test), `DOC`\n(docs), `CHORE` (maintenance/refactor), `BLD` (build system changes).\n\nScope is optional but encouraged — use the component name (e.g.\n`rust-client`, `gc`, `dashboard-api`).\n\n### 50/72 Rule\n\n- **Subject line: ≤ 50 characters.** Keeps it readable in `git log --oneline`,\n  GitHub PR lists, and rebase tooling.\n- **Blank line** between subject and body (required — many tools use this to\n  split them).\n- **Body lines: wrap at 72 characters.** Leaves room for indentation in\n  80-column terminals and email patch workflows.\n- **Imperative mood** in the subject: \"Add login command\", not \"Added\" or\n  \"Adds\". Matches Git's own generated messages.\n- **Body explains what and why**, not how — the diff shows how.\n\nWith the `[TYPE](scope):` prefix, aim to keep the whole subject under 50 chars.\nIf the scope makes that tight, drop it — the type alone is fine.\n\n## Tilt-Backed Tests\n\nTests named `test_k8s_integration` depend on a local Tilt-managed Kubernetes\nenvironment and should not be run blindly.\n\nBefore running these tests, ensure Tilt is already running and the local\nservices are ready. In this repo, the key readiness signals are:\n\n- frontend healthcheck responds on `http://localhost:8000/api/v2/healthcheck`\n- Spanner emulator is reachable on `localhost:9010`\n- required Kubernetes pods in the `chroma` namespace are `Ready`\n\nIf a task requires running `test_k8s_integration` tests and Tilt is not\nclearly ready yet, do one of these before running the tests:\n\n- verify an existing Tilt environment is ready and then run the tests\n- start or restart Tilt, wait for readiness, and only then run the tests\n\nDo not interpret early connection failures from these tests as product bugs\nuntil the Tilt dependency has been checked.\n"},"files":{"AGENTS.md":"# Chroma Codebase Guidelines for AI Agents\n\nSee [CLAUDE.md](./CLAUDE.md) for codebase conventions (commit message format, etc.).\n","CLAUDE.md":"# Chroma Codebase Guidelines\n\n## Commit Message Style\n\nUse the `[TYPE](scope): Description` format:\n\n```\n[ENH](rust-client): Add retry middleware\n[BUG](rust-client): Fix connection timeout on retry\n[TST](gc): Add MCMR hard delete integration test\n[DOC](api): Update embeddings endpoint docs\n[CHORE](deps): Bump reqwest to 0.13\n```\n\nCommon types: `ENH` (feature/enhancement), `BUG` (fix), `TST` (test), `DOC`\n(docs), `CHORE` (maintenance/refactor), `BLD` (build system changes).\n\nScope is optional but encouraged — use the component name (e.g.\n`rust-client`, `gc`, `dashboard-api`).\n\n### 50/72 Rule\n\n- **Subject line: ≤ 50 characters.** Keeps it readable in `git log --oneline`,\n  GitHub PR lists, and rebase tooling.\n- **Blank line** between subject and body (required — many tools use this to\n  split them).\n- **Body lines: wrap at 72 characters.** Leaves room for indentation in\n  80-column terminals and email patch workflows.\n- **Imperative mood** in the subject: \"Add login command\", not \"Added\" or\n  \"Adds\". Matches Git's own generated messages.\n- **Body explains what and why**, not how — the diff shows how.\n\nWith the `[TYPE](scope):` prefix, aim to keep the whole subject under 50 chars.\nIf the scope makes that tight, drop it — the type alone is fine.\n\n## Tilt-Backed Tests\n\nTests named `test_k8s_integration` depend on a local Tilt-managed Kubernetes\nenvironment and should not be run blindly.\n\nBefore running these tests, ensure Tilt is already running and the local\nservices are ready. In this repo, the key readiness signals are:\n\n- frontend healthcheck responds on `http://localhost:8000/api/v2/healthcheck`\n- Spanner emulator is reachable on `localhost:9010`\n- required Kubernetes pods in the `chroma` namespace are `Ready`\n\nIf a task requires running `test_k8s_integration` tests and Tilt is not\nclearly ready yet, do one of these before running the tests:\n\n- verify an existing Tilt environment is ready and then run the tests\n- start or restart Tilt, wait for readiness, and only then run the tests\n\nDo not interpret early connection failures from these tests as product bugs\nuntil the Tilt dependency has been checked.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Chroma Codebase Guidelines for AI Agents\n\nSee [CLAUDE.md](./CLAUDE.md) for codebase conventions (commit message format, etc.).\n","category":"root","tokens":33},{"name":"CLAUDE.md","path":"CLAUDE.md","title":"CLAUDE.md","content":"# Chroma Codebase Guidelines\n\n## Commit Message Style\n\nUse the `[TYPE](scope): Description` format:\n\n```\n[ENH](rust-client): Add retry middleware\n[BUG](rust-client): Fix connection timeout on retry\n[TST](gc): Add MCMR hard delete integration test\n[DOC](api): Update embeddings endpoint docs\n[CHORE](deps): Bump reqwest to 0.13\n```\n\nCommon types: `ENH` (feature/enhancement), `BUG` (fix), `TST` (test), `DOC`\n(docs), `CHORE` (maintenance/refactor), `BLD` (build system changes).\n\nScope is optional but encouraged — use the component name (e.g.\n`rust-client`, `gc`, `dashboard-api`).\n\n### 50/72 Rule\n\n- **Subject line: ≤ 50 characters.** Keeps it readable in `git log --oneline`,\n  GitHub PR lists, and rebase tooling.\n- **Blank line** between subject and body (required — many tools use this to\n  split them).\n- **Body lines: wrap at 72 characters.** Leaves room for indentation in\n  80-column terminals and email patch workflows.\n- **Imperative mood** in the subject: \"Add login command\", not \"Added\" or\n  \"Adds\". Matches Git's own generated messages.\n- **Body explains what and why**, not how — the diff shows how.\n\nWith the `[TYPE](scope):` prefix, aim to keep the whole subject under 50 chars.\nIf the scope makes that tight, drop it — the type alone is fine.\n\n## Tilt-Backed Tests\n\nTests named `test_k8s_integration` depend on a local Tilt-managed Kubernetes\nenvironment and should not be run blindly.\n\nBefore running these tests, ensure Tilt is already running and the local\nservices are ready. In this repo, the key readiness signals are:\n\n- frontend healthcheck responds on `http://localhost:8000/api/v2/healthcheck`\n- Spanner emulator is reachable on `localhost:9010`\n- required Kubernetes pods in the `chroma` namespace are `Ready`\n\nIf a task requires running `test_k8s_integration` tests and Tilt is not\nclearly ready yet, do one of these before running the tests:\n\n- verify an existing Tilt environment is ready and then run the tests\n- start or restart Tilt, wait for readiness, and only then run the tests\n\nDo not interpret early connection failures from these tests as product bugs\nuntil the Tilt dependency has been checked.\n","category":"root","tokens":535}]}