yugabyte/yugabyte-db

cargo-pgrx

Choose and run cargo-pgrx commands, pgrx tests, pg_test coverage, and pg_sys boundary checks.

pg-code-style-guide

The code style guide for YugabyteDB's PostgreSQL fork: required conventions for ANY change under src/postgres -- follow upstream PostgreSQL's rules, explicit and implicit, while isolating and marking the YB delta so that the diff/merge tooling (git, Phorge,…

create-diff

Create a YugabyteDB Phorge diff for the current branch's changes. Use when the user wants to publish their changes for review.

create-pr

Create a Pull Request for the current branch's changes. Use when the user wants to publish a branch for review as a GitHub PR.

yba-query-cli

Query a running YugabyteDB Anywhere (YBA) control plane using the `yba` CLI (managed/yba-cli) — list/describe universes, tasks, backups, providers, alerts, users, storage/EAR/EIT configs, xClusters, RBAC, runtime config, telemetry providers, and more. Use…

review-backport

Review YugabyteDB backport diffs by comparing them against their original commits/diffs. Use when the user provides a Phorge backport diff ID (e.g. D51405) and wants to verify the backport is correct, or when reviewing backport revisions.

create-issue

Create a GitHub issue (or JIRA ticket) tracking a YugabyteDB change or bug. Use when the user needs a tracker reference and doesn't have one yet — e.g. before opening a PR/diff, or to file a standalone bug/feature request.

ash-instrumentation

Instrument YugabyteDB ASH (Active Session History) wait states: add a new WaitStateCode, choose the right macro for synchronous vs asynchronous/callback code paths, register background trackers, plumb ASH metadata through RPCs, and test with…