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.
Multi-agent SlangPy code review using predefined specialist sub-agents.
Install Slangpy Code Review
$ npx skills add shader-slang/slangpy --skill slangpy-code-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install shader-slang/slangpy slangpy-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/shader-slang/slangpy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/slangpy-code-review .claude/skills/slangpy-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 "slangpy-code-review" agent skill from https://github.com/shader-slang/slangpy/tree/main/.agents/skills/slangpy-code-review into .claude/skills/slangpy-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slangpy-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/shader-slang/slangpy/tree/main/.agents/skills/slangpy-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 shader-slang/slangpy --skill slangpy-code-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install shader-slang/slangpy slangpy-code-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shader-slang/slangpy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/slangpy-code-review .agents/skills/slangpy-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 "slangpy-code-review" agent skill from https://github.com/shader-slang/slangpy/tree/main/.agents/skills/slangpy-code-review into .agents/skills/slangpy-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slangpy-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 shader-slang/slangpy --skill slangpy-code-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install shader-slang/slangpy slangpy-code-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shader-slang/slangpy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/slangpy-code-review .cursor/skills/slangpy-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 "slangpy-code-review" agent skill from https://github.com/shader-slang/slangpy/tree/main/.agents/skills/slangpy-code-review into .cursor/skills/slangpy-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slangpy-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/shader-slang/slangpy.git --path .agents/skills/slangpy-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 shader-slang/slangpy --skill slangpy-code-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install shader-slang/slangpy slangpy-code-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shader-slang/slangpy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/slangpy-code-review .gemini/skills/slangpy-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 "slangpy-code-review" agent skill from https://github.com/shader-slang/slangpy/tree/main/.agents/skills/slangpy-code-review into .gemini/skills/slangpy-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slangpy-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 shader-slang/slangpy slangpy-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 shader-slang/slangpy --skill slangpy-code-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/shader-slang/slangpy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/slangpy-code-review .github/skills/slangpy-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 "slangpy-code-review" agent skill from https://github.com/shader-slang/slangpy/tree/main/.agents/skills/slangpy-code-review into .github/skills/slangpy-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slangpy-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 shader-slang/slangpy --skill slangpy-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 shader-slang/slangpy slangpy-code-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/shader-slang/slangpy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/slangpy-code-review .opencode/skills/slangpy-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 "slangpy-code-review" agent skill from https://github.com/shader-slang/slangpy/tree/main/.agents/skills/slangpy-code-review into .opencode/skills/slangpy-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "slangpy-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
slangpy-code-review- GitHub stars
- 154
- Token cost
- ~777 tokens
- SKILL.md length
- 253 words
- Files
- 2
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Multi-agent SlangPy code review using predefined specialist sub-agents.
- Works in 5 steps: Establish review scope, defaulting to a… → Inspect enough local context to create a… → Run all predefined reviewers in… → …
- The user explicitly asks for sub-agents
- SKILL.md covers Predefined Reviewers, Workflow, Reviewer Prompt Template and Final Output
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Slangpy Code Review is an agent skill from shader-slang/slangpy. Multi-agent SlangPy code review using predefined specialist sub-agents. Use when the user explicitly asks for sub-agents, parallel review, specialist reviewers, or a deeper delegated code review of local diffs, branches, PRs, MRs, or specific SlangPy files.
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development, covering Code review and Subagents. The repository describes itself as: Making it easier to work with slang in python.
When your agent uses it
- The user explicitly asks for sub-agents
- Parallel review
- Specialist reviewers
- A deeper delegated code review of local diffs
Example prompts
- “/slangpy-code-review”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Establish review scope, defaulting to a comparison against origin/main when the user does not specify one. Common scopes include
- Inspect enough local context to create a useful reviewer packet
- Run all predefined reviewers in parallel, giving them the same scope and context. Each reviewer should return findings in the specified…
- Collate results
- Report in code-review style
What it can do on your machine
Read from SKILL.md and the folder at commit ce68ef8. 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 markdown).
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
Slangpy Code Review loads about 777 tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 253 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 253 words (~777 tokens).
“Use this skill to run a coordinated multi-agent review. The parent agent is the review captain: it defines the review scope, dispatches specialist reviewers, deduplicates findings, and presents a concise final review.”
- name
- slangpy-code-review
Files
SKILL.md and 1 other file in .agents/skills/slangpy-code-review of shader-slang/slangpy.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit ce68ef8
Compare with similar skills
Slangpy 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 |
|---|---|---|---|---|---|---|
| Slangpy Code Review this skillshader-slang/slangpy | 154 | — | ~777 | Automated safety check: Pass | Custom licence | |
| 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 | |
| Cursor Composer Task DelegateChachamaru127/claude-code-harness | 3.2k | — | ~4.4k | Automated safety check: Notes | MIT | |
| Local PR Reviewwindmill-labs/windmill | 18k | — | ~995 | Automated safety check: Pass | Custom licence |
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.
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.
Local PR Review
windmill-labs/windmill
Runs the same code review locally that GitHub's auto-review actions run on a PR, delegating to a fresh-context subagent so the review isn't biased by the main session's own reasoning.
Auto Devflow
HuangPuStar/FenixAgent
A skill your agent uses when starting an issue, bugfix, feature, or refactor that should be driven by multiple coordinated subagents: explore → plan → code → review, with the main agent acting as…
More from shader-slang/slangpy
Review Plan
shader-slang/slangpy
Review a plan using sub agents and provide feedback on how to improve it.
Related
Categories
Questions about Slangpy Code Review
What does Slangpy Code Review do?
Multi-agent SlangPy code review using predefined specialist sub-agents. Slangpy Code Review is an agent skill from shader-slang/slangpy. Multi-agent SlangPy code review using predefined specialist sub-agents.
When should I use Slangpy Code Review?
Slangpy Code Review fits situations like: the user explicitly asks for sub-agents; parallel review; specialist reviewers; A deeper delegated code review of local diffs.
How do I install Slangpy Code Review in Claude Code?
Run `npx skills add shader-slang/slangpy --skill slangpy-code-review -a claude-code`. Or copy the skill folder (.agents/skills/slangpy-code-review in shader-slang/slangpy) into .claude/skills/slangpy-code-review in your project. Claude Code loads it when a task matches its description.
How do I install Slangpy Code Review in Codex?
Run `npx skills add shader-slang/slangpy --skill slangpy-code-review -a codex`. Or copy the skill folder (.agents/skills/slangpy-code-review in shader-slang/slangpy) into .agents/skills/slangpy-code-review in your project. Codex loads it when a task matches its description.
Can I use Slangpy 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 shader-slang/slangpy --skill slangpy-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/slangpy-code-review, .gemini/skills/slangpy-code-review, .github/skills/slangpy-code-review and .opencode/skills/slangpy-code-review in your project.
What does Slangpy Code Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Slangpy Code Review is instructions for the agent only.
Does Slangpy 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 Slangpy 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 Slangpy Code Review use?
Slangpy Code 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 Slangpy Code Review use?
About 777 tokens (SKILL.md is roughly 3.1k 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 Slangpy Code Review?
Skills that share tags, products or a category with Slangpy 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 Cursor Composer Task Delegate (Chachamaru127/claude-code-harness, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Slangpy Code Review?
shader-slang (a GitHub organization) maintains it in shader-slang/slangpy, which has 154 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 8, 2026.
Source: shader-slang/slangpy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.