{"owner":"pgdogdev","repo":"pgdog","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md","CLAUDE.md"],"skills":{"AGENTS.md":"\nRead `CLAUDE.md` and `.claude/skills/rust/SKILL.md`.\n\n## Tool usage\n\nPrefer the dedicated Read, Grep, and Glob tools for file searching and reading. Bash is permitted as a fallback when dedicated tools can't accomplish the task, but excessive Bash tool calls for search/read operations will be denied.\n\n\n## Running tests\n\nUnit and integration tests use `cargo-nextest`:\n\n```sh\ncargo nextest run --profile dev\n```\n\nIf a single test fails, run it directly by name to isolate the failure.\n\nIntegration tests live under `integration/<lang>/`. The harness is multi-language;\n`integration/run.sh` only dispatches the `python`, `ruby`, `java`, and `sql` suites.\nOther suites (`go`, `rust`, `dry_run`, `pgbench`, `toxi`, `two_pc`, `plugins`,\n`schema_sync`, `complex`, `mirror`, `load_balancer`, `copy_data`, ...) must be run\ndirectly via their own `run.sh`. All suites require a running Postgres instance\nconfigured by `bash integration/setup.sh`.\n\n```sh\nbash integration/run.sh          # python + ruby + java + sql\n```\n\nOr a specific suite:\n\n```sh\nbash integration/go/run.sh\n```\n\nAlways run `cargo fmt` before submitting changes. Run `cargo clippy` where practical.","CLAUDE.md":"# About the project\n\nPgDog is a connection pooler, load balancer and database sharder for PostgreSQL. It's written in async Rust. It implements the PostgreSQL network protocol: applications connect to PgDog, PgDog connects to Postgres, and neither know there is a proxy in between.\n\n## Workflow\n\nLoad the `/rust` skill. Don't follow C/C++/Go norms.\n\n\n## Running tests\n\nUnit tests:\n\n```sh\ncargo nextest run --profile dev\n```\n\nIf a test fails, run it directly by name. Integration tests require Postgres configured via `bash integration/setup.sh` first.\n\nThe integration harness is multi-language: each suite lives in `integration/<lang>/`.\n`integration/run.sh` only dispatches the `python`, `ruby`, `java`, and `sql` suites.\nOther suites (`go`, `elixir`, `rust`, `dry_run`, `pgbench`, `toxi`, `two_pc`,\n`plugins`, `schema_sync`, `complex`, `mirror`, `load_balancer`, `copy_data`, ...)\nmust be run directly via their own `run.sh`.\n\n```sh\nbash integration/run.sh           # python + ruby + java + sql\nbash integration/go/run.sh        # Go suite\nbash integration/elixir/run.sh    # Elixir/Postgrex suite\n```\n\nFormat before committing: `cargo fmt`. Run `cargo clippy` where practical."},"files":{"AGENTS.md":"\nRead `CLAUDE.md` and `.claude/skills/rust/SKILL.md`.\n\n## Tool usage\n\nPrefer the dedicated Read, Grep, and Glob tools for file searching and reading. Bash is permitted as a fallback when dedicated tools can't accomplish the task, but excessive Bash tool calls for search/read operations will be denied.\n\n\n## Running tests\n\nUnit and integration tests use `cargo-nextest`:\n\n```sh\ncargo nextest run --profile dev\n```\n\nIf a single test fails, run it directly by name to isolate the failure.\n\nIntegration tests live under `integration/<lang>/`. The harness is multi-language;\n`integration/run.sh` only dispatches the `python`, `ruby`, `java`, and `sql` suites.\nOther suites (`go`, `rust`, `dry_run`, `pgbench`, `toxi`, `two_pc`, `plugins`,\n`schema_sync`, `complex`, `mirror`, `load_balancer`, `copy_data`, ...) must be run\ndirectly via their own `run.sh`. All suites require a running Postgres instance\nconfigured by `bash integration/setup.sh`.\n\n```sh\nbash integration/run.sh          # python + ruby + java + sql\n```\n\nOr a specific suite:\n\n```sh\nbash integration/go/run.sh\n```\n\nAlways run `cargo fmt` before submitting changes. Run `cargo clippy` where practical.","CLAUDE.md":"# About the project\n\nPgDog is a connection pooler, load balancer and database sharder for PostgreSQL. It's written in async Rust. It implements the PostgreSQL network protocol: applications connect to PgDog, PgDog connects to Postgres, and neither know there is a proxy in between.\n\n## Workflow\n\nLoad the `/rust` skill. Don't follow C/C++/Go norms.\n\n\n## Running tests\n\nUnit tests:\n\n```sh\ncargo nextest run --profile dev\n```\n\nIf a test fails, run it directly by name. Integration tests require Postgres configured via `bash integration/setup.sh` first.\n\nThe integration harness is multi-language: each suite lives in `integration/<lang>/`.\n`integration/run.sh` only dispatches the `python`, `ruby`, `java`, and `sql` suites.\nOther suites (`go`, `elixir`, `rust`, `dry_run`, `pgbench`, `toxi`, `two_pc`,\n`plugins`, `schema_sync`, `complex`, `mirror`, `load_balancer`, `copy_data`, ...)\nmust be run directly via their own `run.sh`.\n\n```sh\nbash integration/run.sh           # python + ruby + java + sql\nbash integration/go/run.sh        # Go suite\nbash integration/elixir/run.sh    # Elixir/Postgrex suite\n```\n\nFormat before committing: `cargo fmt`. Run `cargo clippy` where practical."},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"\nRead `CLAUDE.md` and `.claude/skills/rust/SKILL.md`.\n\n## Tool usage\n\nPrefer the dedicated Read, Grep, and Glob tools for file searching and reading. Bash is permitted as a fallback when dedicated tools can't accomplish the task, but excessive Bash tool calls for search/read operations will be denied.\n\n\n## Running tests\n\nUnit and integration tests use `cargo-nextest`:\n\n```sh\ncargo nextest run --profile dev\n```\n\nIf a single test fails, run it directly by name to isolate the failure.\n\nIntegration tests live under `integration/<lang>/`. The harness is multi-language;\n`integration/run.sh` only dispatches the `python`, `ruby`, `java`, and `sql` suites.\nOther suites (`go`, `rust`, `dry_run`, `pgbench`, `toxi`, `two_pc`, `plugins`,\n`schema_sync`, `complex`, `mirror`, `load_balancer`, `copy_data`, ...) must be run\ndirectly via their own `run.sh`. All suites require a running Postgres instance\nconfigured by `bash integration/setup.sh`.\n\n```sh\nbash integration/run.sh          # python + ruby + java + sql\n```\n\nOr a specific suite:\n\n```sh\nbash integration/go/run.sh\n```\n\nAlways run `cargo fmt` before submitting changes. Run `cargo clippy` where practical.","category":"root","tokens":290},{"name":"CLAUDE.md","path":"CLAUDE.md","title":"CLAUDE.md","content":"# About the project\n\nPgDog is a connection pooler, load balancer and database sharder for PostgreSQL. It's written in async Rust. It implements the PostgreSQL network protocol: applications connect to PgDog, PgDog connects to Postgres, and neither know there is a proxy in between.\n\n## Workflow\n\nLoad the `/rust` skill. Don't follow C/C++/Go norms.\n\n\n## Running tests\n\nUnit tests:\n\n```sh\ncargo nextest run --profile dev\n```\n\nIf a test fails, run it directly by name. Integration tests require Postgres configured via `bash integration/setup.sh` first.\n\nThe integration harness is multi-language: each suite lives in `integration/<lang>/`.\n`integration/run.sh` only dispatches the `python`, `ruby`, `java`, and `sql` suites.\nOther suites (`go`, `elixir`, `rust`, `dry_run`, `pgbench`, `toxi`, `two_pc`,\n`plugins`, `schema_sync`, `complex`, `mirror`, `load_balancer`, `copy_data`, ...)\nmust be run directly via their own `run.sh`.\n\n```sh\nbash integration/run.sh           # python + ruby + java + sql\nbash integration/go/run.sh        # Go suite\nbash integration/elixir/run.sh    # Elixir/Postgrex suite\n```\n\nFormat before committing: `cargo fmt`. Run `cargo clippy` where practical.","category":"root","tokens":296}]}