Graph-Based Change Review
tirth8205/code-review-graph
Reviews a change set using a code knowledge graph for risk scores, blast radius and test gaps, and ends with a merge recommendation.
Checks a YugabyteDB backport revision on Phorge against the original diff it was ported from and flags differences, tracing unexplained code back to master.
Install YugabyteDB Backport Review
$ npx skills add yugabyte/yugabyte-db --skill review-backport -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yugabyte/yugabyte-db review-backport --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/yugabyte/yugabyte-db.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/review-backport .claude/skills/review-backport && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "review-backport" agent skill from https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/review-backport into .claude/skills/review-backport/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-backport", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/review-backportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add yugabyte/yugabyte-db --skill review-backport -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yugabyte/yugabyte-db review-backport --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yugabyte/yugabyte-db.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/review-backport .agents/skills/review-backport && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review-backport" agent skill from https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/review-backport into .agents/skills/review-backport/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-backport", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yugabyte/yugabyte-db --skill review-backport -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yugabyte/yugabyte-db review-backport --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yugabyte/yugabyte-db.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/review-backport .cursor/skills/review-backport && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "review-backport" agent skill from https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/review-backport into .cursor/skills/review-backport/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-backport", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/yugabyte/yugabyte-db.git --path .claude/skills/review-backport--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add yugabyte/yugabyte-db --skill review-backport -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yugabyte/yugabyte-db review-backport --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yugabyte/yugabyte-db.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/review-backport .gemini/skills/review-backport && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "review-backport" agent skill from https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/review-backport into .gemini/skills/review-backport/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-backport", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install yugabyte/yugabyte-db review-backportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add yugabyte/yugabyte-db --skill review-backport -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yugabyte/yugabyte-db.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/review-backport .github/skills/review-backport && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "review-backport" agent skill from https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/review-backport into .github/skills/review-backport/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-backport", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add yugabyte/yugabyte-db --skill review-backport -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yugabyte/yugabyte-db review-backport --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yugabyte/yugabyte-db.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/review-backport .opencode/skills/review-backport && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "review-backport" agent skill from https://github.com/yugabyte/yugabyte-db/tree/master/.claude/skills/review-backport into .opencode/skills/review-backport/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-backport", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
review-backport- GitHub stars
- 11k
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,249 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Checks a YugabyteDB backport revision on Phorge against the original diff it was ported from and flags differences, tracing unexplained code back to master.
- Works in 9 steps: Fetch the backport revision → Parse the summary for references → Fetch the original revision → …
- Verifying a YugabyteDB backport diff against its original commit
- SKILL.md covers Prerequisites, Workflow and Notes
- Reaches phorge.dev.yugabyte.com; needs PHABRICATOR_API_TOKEN
What it does
Given a Phorge revision ID such as D51405, the agent fetches the backport through the Phorge MCP server, confirms the title carries a BACKPORT tag with a version, and checks that the version matches the target branch listed in the diff metadata. It then reads the summary for the original commit hash and original revision, plus any other diffs the backport says it includes.
Next it fetches the original revision and compares the two, looking for changes the backport does not explain and following them back to their origin on master. The review policy itself (what counts as a backport, what to flag and the merge-conflicts note) lives in the repository's REVIEW.md; this skill only covers the mechanics of fetching and comparing. If the summary cannot be parsed, the agent asks you for the original diff ID.
When your agent uses it
- Verifying a YugabyteDB backport diff against its original commit
- Reviewing a Phorge revision whose title starts with a BACKPORT tag
- Checking that a backport targets the branch its version string names
- Finding the origin on master of code a backport adds without explanation
Example prompts
- “Review backport D51405 and tell me where it differs from the original diff.”
- “Does the version in this backport's title match the branch it targets?”
- “The backport also pulls in a second diff; check that its changes are accounted for.”
Requirements
- The Phorge MCP server (user-phorge) set up for your agent
- A Phorge Conduit API token
Workflow steps
9 steps, taken from the step headings in SKILL.md.
- Fetch the backport revision
- Parse the summary for references
- Fetch the original revision
- Get the latest diff ID for each revision
- Get raw diffs
- Fetch additional referenced diffs (if any)
- Compare and review
- Trace unexplained differences back to their origin on master
- Produce the review report
What it can do on your machine
Read from SKILL.md and the folder at commit cd6f789. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
phorge.dev.yugabyte.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
PHABRICATOR_API_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
YugabyteDB Backport Review loads about 2.5k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 1,249 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,249 words (~2,515 tokens).
“Review a YugabyteDB backport diff by comparing it to the original commit/diff and identifying any differences.”
- name
- review-backport
Files
Just SKILL.md in .claude/skills/review-backport of yugabyte/yugabyte-db.
Open the folder on GitHubat commit cd6f789
Compare with similar skills
YugabyteDB Backport Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| YugabyteDB Backport Review this skillyugabyte/yugabyte-db | 11k | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| Graph-Based Change Reviewtirth8205/code-review-graph | 32k | 1 repos | ~331 | Automated safety check: Pass | MIT | |
| Liveagent Code ReviewStack-Cairn/LiveAgent | 2.2k | — | ~2k | Automated safety check: Pass | MIT | |
| Code Review Graph Navigatorhandsontable/handsontable | 22k | — | ~939 | Automated safety check: Pass | Custom licence | |
| Code Reviewnteract/semiotic | 2.7k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| RoamCranot/roam-code | 517 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Liveagent Code Review
Stack-Cairn/LiveAgent
Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation.
Code Review Graph Navigator
handsontable/handsontable
Queries a pre-built, Tree-sitter-based code graph of the whole monorepo instead of grepping call chains, for exploring, debugging, refactoring or reviewing code.
Code Review
nteract/semiotic
Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence.
Roam
Cranot/roam-code
Codebase comprehension via roam-code CLI. An agent skill from Cranot/roam-code.
Batchy
s2-streamstore/claude-batch-toolkit
Send non-urgent tasks to Claude's Batch API at 50% off. An agent skill from s2-streamstore/claude-batch-toolkit.
More from yugabyte/yugabyte-db
YugabyteDB ASH Instrumentation
yugabyte/yugabyte-db
Procedure for adding or changing YugabyteDB Active Session History wait states in TServer and DocDB C++ code, including the macro to use for sync and async paths.
YugabyteDB Phorge Diff Creator
yugabyte/yugabyte-db
Creates a Phorge code review diff for the current branch with arc diff, while applying public-repo confidentiality rules since Phorge content later lands verbatim on the public GitHub repo.
YugabyteDB Issue Creator
yugabyte/yugabyte-db
Creates a GitHub issue or JIRA ticket for a YugabyteDB change or bug, after scrubbing customer data, secrets and unreleased details from anything public.
YBA Read-Only Query CLI
yugabyte/yugabyte-db
Runs read-only lookups - list, describe, get - against a live YugabyteDB Anywhere control plane using the yba CLI, with mutating commands explicitly off-limits.
Create Fork Pull Request
yugabyte/yugabyte-db
Pushes the current branch to your fork and opens a cross-repository GitHub pull request, with a strict check against leaking customer data into public text.
cargo-pgrx Commands and Tests
yugabyte/yugabyte-db
Helps choose and run cargo-pgrx commands and decide whether a Rust test is a plain test or a pg_test, so code never crosses the Postgres boundary the wrong way.
Related
Works with
Categories
Questions about YugabyteDB Backport Review
What does YugabyteDB Backport Review do?
Checks a YugabyteDB backport revision on Phorge against the original diff it was ported from and flags differences, tracing unexplained code back to master. Given a Phorge revision ID such as D51405, the agent fetches the backport through the Phorge MCP server, confirms the title carries a BACKPORT tag with a version, and checks that the version matches the target branch listed in the diff metadata. It then reads the summary for the original commit hash and original revision, plus any other diffs the backport says it includes.
When should I use YugabyteDB Backport Review?
YugabyteDB Backport Review fits situations like: verifying a YugabyteDB backport diff against its original commit; reviewing a Phorge revision whose title starts with a BACKPORT tag; checking that a backport targets the branch its version string names; finding the origin on master of code a backport adds without explanation.
How do I install YugabyteDB Backport Review in Claude Code?
Run `npx skills add yugabyte/yugabyte-db --skill review-backport -a claude-code`. Or copy the skill folder (.claude/skills/review-backport in yugabyte/yugabyte-db) into .claude/skills/review-backport in your project. Claude Code loads it when a task matches its description.
How do I install YugabyteDB Backport Review in Codex?
Run `npx skills add yugabyte/yugabyte-db --skill review-backport -a codex`. Or copy the skill folder (.claude/skills/review-backport in yugabyte/yugabyte-db) into .agents/skills/review-backport in your project. Codex loads it when a task matches its description.
Can I use YugabyteDB Backport Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add yugabyte/yugabyte-db --skill review-backport -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-backport, .gemini/skills/review-backport, .github/skills/review-backport and .opencode/skills/review-backport in your project.
What does YugabyteDB Backport Review need to run?
Going by SKILL.md and its folder, YugabyteDB Backport Review needs credentials named PHABRICATOR_API_TOKEN. Our summary lists: The Phorge MCP server (user-phorge) set up for your agent; A Phorge Conduit API token.
Does YugabyteDB Backport Review access the network?
SKILL.md names 1 domain. In commands or code: phorge.dev.yugabyte.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is YugabyteDB Backport Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does YugabyteDB Backport Review use?
YugabyteDB Backport Review has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does YugabyteDB Backport Review use?
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to YugabyteDB Backport Review?
Skills that share tags, products or a category with YugabyteDB Backport Review: Graph-Based Change Review (tirth8205/code-review-graph, 32k stars), Liveagent Code Review (Stack-Cairn/LiveAgent, 2.2k stars), Code Review Graph Navigator (handsontable/handsontable, 22k stars) and Code Review (nteract/semiotic, 2.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains YugabyteDB Backport Review?
yugabyte (a GitHub organization) maintains it in yugabyte/yugabyte-db, which has 10,586 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 11, 2026.
Source: yugabyte/yugabyte-db on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.