{"owner":"scylladb","repo":"seastar","hasSkills":true,"totalSkillsCount":1,"totalTokensCount":883,"categories":["claude-rule"],"hasMcp":false,"mcpConfig":null,"found":[".claude/CLAUDE.md"],"skills":{".claude/CLAUDE.md":"# Seastar Project Instructions\n\n## Building\n\nThe project uses CMake with ninja as the build system. Build directories are located in `build/<mode>`.\n\n### Build Commands\n\n**Build specific target:**\n```bash\nninja -C build/<mode> <target>\n```\n\nWhere `<mode>` is typically:\n- `dev` - development build\n- `debug` - debug build\n- `release` - release build\n- `sanitize` - sanitizer build (ASan/UBSan)\n\n**List available targets:**\n```bash\nninja -C build/<mode> -t targets\n```\n\n**List all targets (including test targets):**\n```bash\nninja -C build/<mode> -t targets all\n```\n\n### Common Build Examples\n\n```bash\n# Build ioinfo tool in dev mode\nninja -C build/dev apps/io_tester/ioinfo\n\n# Build io_tester in dev mode\nninja -C build/dev apps/io_tester/io_tester\n\n# Build all in release mode\nninja -C build/release\n\n# List all available targets\nninja -C build/dev -t targets all\n```\n\n### Important Notes\n\n- **Check for existing build directories first** - if `build/<mode>` exists, use it directly; otherwise run `./configure.py --mode=<mode>` to create it\n- **Always use `ninja -C build/<mode>`** from the repository root\n- **Do NOT use** plain `ninja` from the root directory - it will fail with \"Execute Ninja in a build directory\"\n- The working directory during builds should typically be the repository root\n- After code changes to specific components, rebuild only that target for faster iteration\n\n## Testing\n\nThe project uses CTest for running tests. Test executables are built in `build/<mode>/tests/unit/` and `build/<mode>/tests/perf/`.\n\n### Test Runners\n\n**`./test.py`** (preferred) - Python wrapper with useful options:\n```bash\n./test.py --mode dev --name <pattern>  # Run specific test in dev mode\n./test.py --mode dev --fast            # Run only fast tests\n./test.py --mode dev -v                # Verbose output\n```\n\nOptions:\n- `--mode <mode>` - Run for specific build mode (otherwise runs ALL modes)\n- `--name <pattern>` - Filter tests by name\n- `--fast` - Run only fast tests\n- `--timeout <secs>` - Set timeout (default 300s)\n- `--smp <n>` / `-c <n>` - Number of threads for multi-core tests (default 2)\n- `--verbose` / `-v` - Verbose output\n- `--offline` - Disable tests that access the internet\n\n**`ninja -C build/<mode> test`** - Basic ctest invocation for a single mode. Less flexible, no `--output-on-failure` by default.\n\n### Running Specific Tests\n\n```bash\n# Using test.py (preferred)\n./test.py --mode dev --name circular_buffer\n\n# Using ctest directly\nctest --test-dir build/dev -R circular_buffer --output-on-failure\n\n# Run test executable directly\n./build/dev/tests/unit/circular_buffer_test\n```\n\n**List all available tests:**\n```bash\nctest --test-dir build/dev -N\n```\n\n### Test Types\n\n- **Unit tests**: Located in `tests/unit/`, use Boost.Test framework\n- **Performance tests**: Located in `tests/perf/`, benchmark various components\n\n### Important Notes\n\n- **When iterating on code changes**, choose an appropriate test that covers the modified code and run only that test\n- **Running all tests is slow** - only run the full test suite when explicitly requested\n- Most unit tests use Boost.Test and accept standard Boost.Test command line options\n- Some tests (like allocator tests) may run for the default duration (5 seconds) unless interrupted\n\n## Style\n\nMinimum C++ version is C++20. Use C++20 API where possible.\n\nFollow existing style.\n\nComment all public methods carefully following the style of the same source file (e.g., doxygen if existing comments use that style).\n"},"files":{".claude/CLAUDE.md":"# Seastar Project Instructions\n\n## Building\n\nThe project uses CMake with ninja as the build system. Build directories are located in `build/<mode>`.\n\n### Build Commands\n\n**Build specific target:**\n```bash\nninja -C build/<mode> <target>\n```\n\nWhere `<mode>` is typically:\n- `dev` - development build\n- `debug` - debug build\n- `release` - release build\n- `sanitize` - sanitizer build (ASan/UBSan)\n\n**List available targets:**\n```bash\nninja -C build/<mode> -t targets\n```\n\n**List all targets (including test targets):**\n```bash\nninja -C build/<mode> -t targets all\n```\n\n### Common Build Examples\n\n```bash\n# Build ioinfo tool in dev mode\nninja -C build/dev apps/io_tester/ioinfo\n\n# Build io_tester in dev mode\nninja -C build/dev apps/io_tester/io_tester\n\n# Build all in release mode\nninja -C build/release\n\n# List all available targets\nninja -C build/dev -t targets all\n```\n\n### Important Notes\n\n- **Check for existing build directories first** - if `build/<mode>` exists, use it directly; otherwise run `./configure.py --mode=<mode>` to create it\n- **Always use `ninja -C build/<mode>`** from the repository root\n- **Do NOT use** plain `ninja` from the root directory - it will fail with \"Execute Ninja in a build directory\"\n- The working directory during builds should typically be the repository root\n- After code changes to specific components, rebuild only that target for faster iteration\n\n## Testing\n\nThe project uses CTest for running tests. Test executables are built in `build/<mode>/tests/unit/` and `build/<mode>/tests/perf/`.\n\n### Test Runners\n\n**`./test.py`** (preferred) - Python wrapper with useful options:\n```bash\n./test.py --mode dev --name <pattern>  # Run specific test in dev mode\n./test.py --mode dev --fast            # Run only fast tests\n./test.py --mode dev -v                # Verbose output\n```\n\nOptions:\n- `--mode <mode>` - Run for specific build mode (otherwise runs ALL modes)\n- `--name <pattern>` - Filter tests by name\n- `--fast` - Run only fast tests\n- `--timeout <secs>` - Set timeout (default 300s)\n- `--smp <n>` / `-c <n>` - Number of threads for multi-core tests (default 2)\n- `--verbose` / `-v` - Verbose output\n- `--offline` - Disable tests that access the internet\n\n**`ninja -C build/<mode> test`** - Basic ctest invocation for a single mode. Less flexible, no `--output-on-failure` by default.\n\n### Running Specific Tests\n\n```bash\n# Using test.py (preferred)\n./test.py --mode dev --name circular_buffer\n\n# Using ctest directly\nctest --test-dir build/dev -R circular_buffer --output-on-failure\n\n# Run test executable directly\n./build/dev/tests/unit/circular_buffer_test\n```\n\n**List all available tests:**\n```bash\nctest --test-dir build/dev -N\n```\n\n### Test Types\n\n- **Unit tests**: Located in `tests/unit/`, use Boost.Test framework\n- **Performance tests**: Located in `tests/perf/`, benchmark various components\n\n### Important Notes\n\n- **When iterating on code changes**, choose an appropriate test that covers the modified code and run only that test\n- **Running all tests is slow** - only run the full test suite when explicitly requested\n- Most unit tests use Boost.Test and accept standard Boost.Test command line options\n- Some tests (like allocator tests) may run for the default duration (5 seconds) unless interrupted\n\n## Style\n\nMinimum C++ version is C++20. Use C++20 API where possible.\n\nFollow existing style.\n\nComment all public methods carefully following the style of the same source file (e.g., doxygen if existing comments use that style).\n"},"items":[{"name":"CLAUDE.md","path":".claude/CLAUDE.md","rawUrl":"https://raw.githubusercontent.com/scylladb/seastar/HEAD/.claude/CLAUDE.md","title":".claude - Claude Agent Guidelines & System Prompt","category":"claude-rule","format":"markdown","content":"# Seastar Project Instructions\n\n## Building\n\nThe project uses CMake with ninja as the build system. Build directories are located in `build/<mode>`.\n\n### Build Commands\n\n**Build specific target:**\n```bash\nninja -C build/<mode> <target>\n```\n\nWhere `<mode>` is typically:\n- `dev` - development build\n- `debug` - debug build\n- `release` - release build\n- `sanitize` - sanitizer build (ASan/UBSan)\n\n**List available targets:**\n```bash\nninja -C build/<mode> -t targets\n```\n\n**List all targets (including test targets):**\n```bash\nninja -C build/<mode> -t targets all\n```\n\n### Common Build Examples\n\n```bash\n# Build ioinfo tool in dev mode\nninja -C build/dev apps/io_tester/ioinfo\n\n# Build io_tester in dev mode\nninja -C build/dev apps/io_tester/io_tester\n\n# Build all in release mode\nninja -C build/release\n\n# List all available targets\nninja -C build/dev -t targets all\n```\n\n### Important Notes\n\n- **Check for existing build directories first** - if `build/<mode>` exists, use it directly; otherwise run `./configure.py --mode=<mode>` to create it\n- **Always use `ninja -C build/<mode>`** from the repository root\n- **Do NOT use** plain `ninja` from the root directory - it will fail with \"Execute Ninja in a build directory\"\n- The working directory during builds should typically be the repository root\n- After code changes to specific components, rebuild only that target for faster iteration\n\n## Testing\n\nThe project uses CTest for running tests. Test executables are built in `build/<mode>/tests/unit/` and `build/<mode>/tests/perf/`.\n\n### Test Runners\n\n**`./test.py`** (preferred) - Python wrapper with useful options:\n```bash\n./test.py --mode dev --name <pattern>  # Run specific test in dev mode\n./test.py --mode dev --fast            # Run only fast tests\n./test.py --mode dev -v                # Verbose output\n```\n\nOptions:\n- `--mode <mode>` - Run for specific build mode (otherwise runs ALL modes)\n- `--name <pattern>` - Filter tests by name\n- `--fast` - Run only fast tests\n- `--timeout <secs>` - Set timeout (default 300s)\n- `--smp <n>` / `-c <n>` - Number of threads for multi-core tests (default 2)\n- `--verbose` / `-v` - Verbose output\n- `--offline` - Disable tests that access the internet\n\n**`ninja -C build/<mode> test`** - Basic ctest invocation for a single mode. Less flexible, no `--output-on-failure` by default.\n\n### Running Specific Tests\n\n```bash\n# Using test.py (preferred)\n./test.py --mode dev --name circular_buffer\n\n# Using ctest directly\nctest --test-dir build/dev -R circular_buffer --output-on-failure\n\n# Run test executable directly\n./build/dev/tests/unit/circular_buffer_test\n```\n\n**List all available tests:**\n```bash\nctest --test-dir build/dev -N\n```\n\n### Test Types\n\n- **Unit tests**: Located in `tests/unit/`, use Boost.Test framework\n- **Performance tests**: Located in `tests/perf/`, benchmark various components\n\n### Important Notes\n\n- **When iterating on code changes**, choose an appropriate test that covers the modified code and run only that test\n- **Running all tests is slow** - only run the full test suite when explicitly requested\n- Most unit tests use Boost.Test and accept standard Boost.Test command line options\n- Some tests (like allocator tests) may run for the default duration (5 seconds) unless interrupted\n\n## Style\n\nMinimum C++ version is C++20. Use C++20 API where possible.\n\nFollow existing style.\n\nComment all public methods carefully following the style of the same source file (e.g., doxygen if existing comments use that style).\n","isInternal":false,"tokens":883,"sizeBytes":3494}],"systemPromptSnippet":"<yakaai_skills repo=\"scylladb/seastar\">\n<!-- File: .claude/CLAUDE.md (Tokens: ~883 | Category: claude-rule) -->\n# Seastar Project Instructions\n\n## Building\n\nThe project uses CMake with ninja as the build system. Build directories are located in `build/<mode>`.\n\n### Build Commands\n\n**Build specific target:**\n```bash\nninja -C build/<mode> <target>\n```\n\nWhere `<mode>` is typically:\n- `dev` - development build\n- `debug` - debug build\n- `release` - release build\n- `sanitize` - sanitizer build (ASan/UBSan)\n\n**List available targets:**\n```bash\nninja -C build/<mode> -t targets\n```\n\n**List all targets (including test targets):**\n```bash\nninja -C build/<mode> -t targets all\n```\n\n### Common Build Examples\n\n```bash\n# Build ioinfo tool in dev mode\nninja -C build/dev apps/io_tester/ioinfo\n\n# Build io_tester in dev mode\nninja -C build/dev apps/io_tester/io_tester\n\n# Build all in release mode\nninja -C build/release\n\n# List all available targets\nninja -C build/dev -t targets all\n```\n\n### Important Notes\n\n- **Check for existing build directories first** - if `build/<mode>` exists, use it directly; otherwise run `./configure.py --mode=<mode>` to create it\n- **Always use `ninja -C build/<mode>`** from the repository root\n- **Do NOT use** plain `ninja` from the root directory - it will fail with \"Execute Ninja in a build directory\"\n- The working directory during builds should typically be the repository root\n- After code changes to specific components, rebuild only that target for faster iteration\n\n## Testing\n\nThe project uses CTest for running tests. Test executables are built in `build/<mode>/tests/unit/` and `build/<mode>/tests/perf/`.\n\n### Test Runners\n\n**`./test.py`** (preferred) - Python wrapper with useful options:\n```bash\n./test.py --mode dev --name <pattern>  # Run specific test in dev mode\n./test.py --mode dev --fast            # Run only fast tests\n./test.py --mode dev -v                # Verbose output\n```\n\nOptions:\n- `--mode <mode>` - Run for specific build mode (otherwise runs ALL modes)\n- `--name <pattern>` - Filter tests by name\n- `--fast` - Run only fast tests\n- `--timeout <secs>` - Set timeout (default 300s)\n- `--smp <n>` / `-c <n>` - Number of threads for multi-core tests (default 2)\n- `--verbose` / `-v` - Verbose output\n- `--offline` - Disable tests that access the internet\n\n**`ninja -C build/<mode> test`** - Basic ctest invocation for a single mode. Less flexible, no `--output-on-failure` by default.\n\n### Running Specific Tests\n\n```bash\n# Using test.py (preferred)\n./test.py --mode dev --name circular_buffer\n\n# Using ctest directly\nctest --test-dir build/dev -R circular_buffer --output-on-failure\n\n# Run test executable directly\n./build/dev/tests/unit/circular_buffer_test\n```\n\n**List all available tests:**\n```bash\nctest --test-dir build/dev -N\n```\n\n### Test Types\n\n- **Unit tests**: Located in `tests/unit/`, use Boost.Test framework\n- **Performance tests**: Located in `tests/perf/`, benchmark various components\n\n### Important Notes\n\n- **When iterating on code changes**, choose an appropriate test that covers the modified code and run only that test\n- **Running all tests is slow** - only run the full test suite when explicitly requested\n- Most unit tests use Boost.Test and accept standard Boost.Test command line options\n- Some tests (like allocator tests) may run for the default duration (5 seconds) unless interrupted\n\n## Style\n\nMinimum C++ version is C++20. Use C++20 API where possible.\n\nFollow existing style.\n\nComment all public methods carefully following the style of the same source file (e.g., doxygen if existing comments use that style).\n</yakaai_skills>"}