{"owner":"cockroachdb","repo":"pebble","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["CLAUDE.md"],"skills":{"CLAUDE.md":"# CLAUDE.md\n\nThis file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.\n\n## Pebble Development Environment\n\nPebble is a LevelDB/RocksDB inspired key-value store focused on\nperformance and internal usage by CockroachDB.\n\n## Testing\n```bash\ngo test -tags invariants .\ngo test -tags invariants ./...\n```\n\n## Regenerating test files\n```bash\ngo test -tags invariants ./<package> --rewrite\n```\n\n## Linting\n```bash\ngo test -tags invariants ./internal/lint\"\n```\n\n## When generating PRs and commit records\n\n- Follow the format:\n  - Separate the subject from the body with a blank line.\n  - Use the body of the commit record to explain what existed before your change, what you changed, and why.\n  - Prefix the subject line with the package in which the bulk of the changes occur.\n  - For multi-commit PRs, summarize each commit in the PR record.\n  - Do not include a test plan unless explicitly asked by the user.\n  - Use markdown format for the body; in particular, enclose any identifiers with backquotes.\n\n## Interaction Style\n\n* Be direct and honest.\n* Skip unnecessary acknowledgments.\n* Correct me when I'm wrong and explain why.\n* Suggest better alternatives if my ideas can be improved.\n* Focus on accuracy and efficiency.\n* Challenge my assumptions when needed.\n* Prioritize quality information and directness.\n"},"files":{"CLAUDE.md":"# CLAUDE.md\n\nThis file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.\n\n## Pebble Development Environment\n\nPebble is a LevelDB/RocksDB inspired key-value store focused on\nperformance and internal usage by CockroachDB.\n\n## Testing\n```bash\ngo test -tags invariants .\ngo test -tags invariants ./...\n```\n\n## Regenerating test files\n```bash\ngo test -tags invariants ./<package> --rewrite\n```\n\n## Linting\n```bash\ngo test -tags invariants ./internal/lint\"\n```\n\n## When generating PRs and commit records\n\n- Follow the format:\n  - Separate the subject from the body with a blank line.\n  - Use the body of the commit record to explain what existed before your change, what you changed, and why.\n  - Prefix the subject line with the package in which the bulk of the changes occur.\n  - For multi-commit PRs, summarize each commit in the PR record.\n  - Do not include a test plan unless explicitly asked by the user.\n  - Use markdown format for the body; in particular, enclose any identifiers with backquotes.\n\n## Interaction Style\n\n* Be direct and honest.\n* Skip unnecessary acknowledgments.\n* Correct me when I'm wrong and explain why.\n* Suggest better alternatives if my ideas can be improved.\n* Focus on accuracy and efficiency.\n* Challenge my assumptions when needed.\n* Prioritize quality information and directness.\n"},"items":[{"name":"CLAUDE.md","path":"CLAUDE.md","title":"CLAUDE.md","content":"# CLAUDE.md\n\nThis file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.\n\n## Pebble Development Environment\n\nPebble is a LevelDB/RocksDB inspired key-value store focused on\nperformance and internal usage by CockroachDB.\n\n## Testing\n```bash\ngo test -tags invariants .\ngo test -tags invariants ./...\n```\n\n## Regenerating test files\n```bash\ngo test -tags invariants ./<package> --rewrite\n```\n\n## Linting\n```bash\ngo test -tags invariants ./internal/lint\"\n```\n\n## When generating PRs and commit records\n\n- Follow the format:\n  - Separate the subject from the body with a blank line.\n  - Use the body of the commit record to explain what existed before your change, what you changed, and why.\n  - Prefix the subject line with the package in which the bulk of the changes occur.\n  - For multi-commit PRs, summarize each commit in the PR record.\n  - Do not include a test plan unless explicitly asked by the user.\n  - Use markdown format for the body; in particular, enclose any identifiers with backquotes.\n\n## Interaction Style\n\n* Be direct and honest.\n* Skip unnecessary acknowledgments.\n* Correct me when I'm wrong and explain why.\n* Suggest better alternatives if my ideas can be improved.\n* Focus on accuracy and efficiency.\n* Challenge my assumptions when needed.\n* Prioritize quality information and directness.\n","category":"root","tokens":339}]}