GitHub Review Iteration
prisma/orm
Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.
Review the current code changes (branch diff vs main, a commit range, or a PR) for seq-db.
Install Code Review
$ npx skills add ozontech/seq-db --skill code-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ozontech/seq-db code-review --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/ozontech/seq-db.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/code-review .claude/skills/code-review && 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 "code-review" agent skill from https://github.com/ozontech/seq-db/tree/main/.claude/skills/code-review into .claude/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", 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/ozontech/seq-db/tree/main/.claude/skills/code-reviewType 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 ozontech/seq-db --skill code-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ozontech/seq-db code-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ozontech/seq-db.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/code-review .agents/skills/code-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-review" agent skill from https://github.com/ozontech/seq-db/tree/main/.claude/skills/code-review into .agents/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", 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 ozontech/seq-db --skill code-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ozontech/seq-db code-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ozontech/seq-db.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/code-review .cursor/skills/code-review && 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 "code-review" agent skill from https://github.com/ozontech/seq-db/tree/main/.claude/skills/code-review into .cursor/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", 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/ozontech/seq-db.git --path .claude/skills/code-review--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 ozontech/seq-db --skill code-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ozontech/seq-db code-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ozontech/seq-db.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/code-review .gemini/skills/code-review && 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 "code-review" agent skill from https://github.com/ozontech/seq-db/tree/main/.claude/skills/code-review into .gemini/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", 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 ozontech/seq-db code-reviewInstalls 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 ozontech/seq-db --skill code-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ozontech/seq-db.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/code-review .github/skills/code-review && 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 "code-review" agent skill from https://github.com/ozontech/seq-db/tree/main/.claude/skills/code-review into .github/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", 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 ozontech/seq-db --skill code-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ozontech/seq-db code-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ozontech/seq-db.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/code-review .opencode/skills/code-review && 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 "code-review" agent skill from https://github.com/ozontech/seq-db/tree/main/.claude/skills/code-review into .opencode/skills/code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-review", 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
code-review- GitHub stars
- 133
- Token cost
- ~411 tokens
- SKILL.md length
- 191 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Review the current code changes (branch diff vs main, a commit range, or a PR) for seq-db.
- Works in 4 steps: Determine scope from the user's request → Spawn the code-reviewer subagent (Agent… → Relay the findings. Present the… → …
- The user asks to review changes
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A diff before opening a PR
What it does
Code Review is an agent skill from ozontech/seq-db. Review the current code changes (branch diff vs main, a commit range, or a PR) for seq-db. Delegates to the code-reviewer subagent so the review's file reading and test runs stay out of the main context, then relays ranked findings. Use when the user asks to review changes, a branch, or a diff before opening a PR.
Its SKILL.md is about 410 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Code review and Subagents. The repository describes itself as: seq-db is a scalable and high-performance database designed for storing and querying logs efficiently. The licence is Apache-2.0.
When your agent uses it
- The user asks to review changes
- A diff before opening a PR
Example prompts
- “/code-review”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Determine scope from the user's request
- Spawn the code-reviewer subagent (Agent tool, `subagent_type
- Relay the findings. Present the subagent's verdict and findings to the
- Do not fix anything unless asked. Reviewing and editing are separate
What it can do on your machine
Read from SKILL.md and the folder at commit 70af159. 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.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Code Review loads about 411 tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 191 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
The full file from ozontech/seq-db at commit 70af159, republished under its Apache-2.0 licence (© ozontech). 191 words, ~411 tokens.
Download SKILL.mdSave it as
.claude/skills/code-review/SKILL.md (or your agent's skills folder).- name
- code-review
- description
- Review the current code changes (branch diff vs main, a commit range, or a PR) for seq-db. Delegates to the code-reviewer subagent so the review's file reading and test runs stay out of the main context, then relays ranked findings. Use when the user asks to review changes, a branch, or a diff before opening a PR.
Review changes
Delegate the review to a subagent so the diff reading, context gathering, and any test/lint runs stay out of this conversation's context. You orchestrate and relay; you do not read the whole diff yourself.
Steps
- Determine scope from the user's request:
- No argument → current branch vs
mainplus uncommitted changes. - A commit/range, path(s), or PR number → pass that through verbatim.
- No argument → current branch vs
- Spawn the
code-reviewersubagent (Agent tool,subagent_type: "code-reviewer"). Give it the scope and any focus the user asked for (e.g. "concentrate on the sealing path"). One agent is enough; only fan out into several code-reviewer agents if the diff spans clearly independent subsystems and the user asked for a thorough pass. - Relay the findings. Present the subagent's verdict and findings to the
user, ranked most-severe first. If code-review reporting via
ReportFindingsis available, call it once with the verified findings for structured rendering; otherwise present them as a concise markdown list. Do not pad the output — a clean review is a valid result. - Do not fix anything unless asked. Reviewing and editing are separate steps. After presenting findings, offer to fix specific ones on request.
© ozontech, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/code-review of ozontech/seq-db.
Open the folder on GitHubat commit 70af159
Compare with similar skills
Code 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 |
|---|---|---|---|---|---|---|
| Code Review this skillozontech/seq-db | 133 | — | ~411 | Automated safety check: Pass | Apache-2.0 | |
| GitHub Review Iterationprisma/orm | 48k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Cherry Studio PR ReviewCherryHQ/cherry-studio | 52k | — | ~3.9k | Automated safety check: Pass | AGPL-3.0 | |
| PR Reviewjaemk/self_update | 961 | — | ~1.5k | Automated safety check: Notes | MIT | |
| PR Reviewjaemk/cached | 2.1k | — | ~2.5k | Automated safety check: Notes | MIT | |
| Cursor Composer Task DelegateChachamaru127/claude-code-harness | 3.2k | — | ~4.4k | Automated safety check: Notes | MIT |
Similar skills
- Official
Cherry Studio PR Review
CherryHQ/cherry-studio
Reviews Cherry Studio branches, pull requests, commits, files and docs against the project's own architecture, naming, API-boundary and UI rules, report-only by default.
PR Review
jaemk/self_update
Targeted, read-only review of a PR or checked-out branch. An agent skill from jaemk/self_update.
PR Review
jaemk/cached
Targeted, read-only review of a PR or checked-out branch. An agent skill from jaemk/cached.
Cursor Composer Task Delegate
Chachamaru127/claude-code-harness
Hands one implementation task to Cursor Composer in an isolated git worktree, then reviews its diff and cherry-picks the result into the main branch.
Pull Request Code Review Orchestrator
openinterpreter/openinterpreter
Run a final code review on a pull request
More from ozontech/seq-db
Perf Loop
ozontech/seq-db
Autonomous performance-optimization loop for seq-db driven by seqbazooka.
Code Navigation
ozontech/seq-db
How to navigate and explore Go code in this repo. An agent skill from ozontech/seq-db.
Perf Architect
ozontech/seq-db
Design-level performance review for seq-db — proposes data-structure, algorithmic, memory-layout, and architectural alternatives for a hot path, each with reasoning and a validation plan.
Perf Analyze
ozontech/seq-db
One-shot profile analysis for seq-db — turns pprof profiles (and optional metrics/report) into a ranked list of concrete, profile-grounded optimization opportunities for the code.
Related
Categories
Questions about Code Review
What does Code Review do?
Review the current code changes (branch diff vs main, a commit range, or a PR) for seq-db. Code Review is an agent skill from ozontech/seq-db. Review the current code changes (branch diff vs main, a commit range, or a PR) for seq-db.
When should I use Code Review?
Code Review fits situations like: the user asks to review changes; A diff before opening a PR.
How do I install Code Review in Claude Code?
Run `npx skills add ozontech/seq-db --skill code-review -a claude-code`. Or copy the skill folder (.claude/skills/code-review in ozontech/seq-db) into .claude/skills/code-review in your project. Claude Code loads it when a task matches its description.
How do I install Code Review in Codex?
Run `npx skills add ozontech/seq-db --skill code-review -a codex`. Or copy the skill folder (.claude/skills/code-review in ozontech/seq-db) into .agents/skills/code-review in your project. Codex loads it when a task matches its description.
Can I use Code 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 ozontech/seq-db --skill code-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-review, .gemini/skills/code-review, .github/skills/code-review and .opencode/skills/code-review in your project.
What does Code Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Code Review is instructions for the agent only.
Does Code Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Code 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 Code Review use?
Code Review is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Code Review use?
About 411 tokens (SKILL.md is roughly 1.6k 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 Code Review?
Skills that share tags, products or a category with Code Review: GitHub Review Iteration (prisma/orm, 48k stars), Cherry Studio PR Review (CherryHQ/cherry-studio, 52k stars), PR Review (jaemk/self_update, 961 stars) and PR Review (jaemk/cached, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Code Review?
ozontech (a GitHub organization) maintains it in ozontech/seq-db, which has 133 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 6, 2026.
Source: ozontech/seq-db on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.