PR Deep Verification
QwenLM/qwen-code
Runs a sandboxed, evidence-based check of one qwen-code pull request, proving its main change against the base build and writing a report with a machine-readable verdict.
Runs local checks and a repo-reviewer subagent over the whole branch diff before a pull request is opened, then records the approval in the PR description.
Install Pre-PR Review
$ npx skills add yuga-hashimoto/and-code --skill pre-pr-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yuga-hashimoto/and-code pre-pr-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/yuga-hashimoto/and-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/pre-pr-review .claude/skills/pre-pr-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 "pre-pr-review" agent skill from https://github.com/yuga-hashimoto/and-code/tree/main/.opencode/skills/pre-pr-review into .claude/skills/pre-pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-pr-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/yuga-hashimoto/and-code/tree/main/.opencode/skills/pre-pr-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 yuga-hashimoto/and-code --skill pre-pr-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yuga-hashimoto/and-code pre-pr-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yuga-hashimoto/and-code.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/pre-pr-review .agents/skills/pre-pr-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 "pre-pr-review" agent skill from https://github.com/yuga-hashimoto/and-code/tree/main/.opencode/skills/pre-pr-review into .agents/skills/pre-pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-pr-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 yuga-hashimoto/and-code --skill pre-pr-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yuga-hashimoto/and-code pre-pr-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yuga-hashimoto/and-code.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/pre-pr-review .cursor/skills/pre-pr-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 "pre-pr-review" agent skill from https://github.com/yuga-hashimoto/and-code/tree/main/.opencode/skills/pre-pr-review into .cursor/skills/pre-pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-pr-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/yuga-hashimoto/and-code.git --path .opencode/skills/pre-pr-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 yuga-hashimoto/and-code --skill pre-pr-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yuga-hashimoto/and-code pre-pr-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yuga-hashimoto/and-code.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/pre-pr-review .gemini/skills/pre-pr-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 "pre-pr-review" agent skill from https://github.com/yuga-hashimoto/and-code/tree/main/.opencode/skills/pre-pr-review into .gemini/skills/pre-pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-pr-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 yuga-hashimoto/and-code pre-pr-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 yuga-hashimoto/and-code --skill pre-pr-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yuga-hashimoto/and-code.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/pre-pr-review .github/skills/pre-pr-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 "pre-pr-review" agent skill from https://github.com/yuga-hashimoto/and-code/tree/main/.opencode/skills/pre-pr-review into .github/skills/pre-pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-pr-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 yuga-hashimoto/and-code --skill pre-pr-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 yuga-hashimoto/and-code pre-pr-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yuga-hashimoto/and-code.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/pre-pr-review .opencode/skills/pre-pr-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 "pre-pr-review" agent skill from https://github.com/yuga-hashimoto/and-code/tree/main/.opencode/skills/pre-pr-review into .opencode/skills/pre-pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pre-pr-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
pre-pr-review- GitHub stars
- 127
- Token cost
- ~710 tokens
- SKILL.md length
- 322 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Runs local checks and a repo-reviewer subagent over the whole branch diff before a pull request is opened, then records the approval in the PR description.
- Works in 5 steps: Sync and scope the diff → Run the local gates first (cheap… → Invoke the reviewer with the task tool,… → …
- About to open a pull request in this repository
- SKILL.md covers Workflow and Rules
- Calls git
What it does
Written for one Android repository, the skill makes an approved review a precondition for creating a pull request. It starts by fetching origin main and listing the branch diff, and stops if the branch has nothing ahead. Then it runs the cheap local gates first, detekt and spotlessCheck through Gradle, plus a translation key-parity check when string resources changed. Nothing in CI enforces the review, so the habit depends on the author.
The repo-reviewer subagent then reviews the full diff itself. A REQUEST_CHANGES verdict means fixing every blocker and reviewing again until the verdict is APPROVE, and non-blocking suggestions can be applied when they are cheap and safe. The reviewer's report goes into the PR description verbatim and must be redone after material later pushes. If the subagent is unavailable you say so in the PR, and trivial bot PRs such as translation syncs are exempt.
When your agent uses it
- About to open a pull request in this repository
- Re-checking a branch after reviewer feedback
- Adding the reviewer's verdict to a PR description
Example prompts
- “I am ready to open a PR for the settings screen changes. Run the pre-PR review first.”
- “The reviewer asked for changes on this branch; fix the blockers and run the review again.”
- “Update the pre-PR review block in the PR description after my latest push.”
Requirements
- Git with an origin/main branch
- A repo-reviewer subagent defined in the repository
- The Gradle tasks detekt and spotlessCheck
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Sync and scope the diff
- Run the local gates first (cheap failures should never reach the reviewer)
- Invoke the reviewer with the task tool, subagent type repo-reviewer. Prompt it with
- Handle the verdict
- Record the verdict in the PR description. The PR body should carry the reviewer's report
What it can do on your machine
Read from SKILL.md and the folder at commit f6593e1. 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Pre-PR Review loads about 710 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 322 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 yuga-hashimoto/and-code at commit f6593e1, republished under its MIT licence (© yuga-hashimoto). 322 words, ~710 tokens.
Download SKILL.mdSave it as
.claude/skills/pre-pr-review/SKILL.md (or your agent's skills folder).- name
- pre-pr-review
- description
- Review pass before opening a pull request in this repository. Runs local CI gates and the repo-reviewer subagent on the full branch diff, iterates until the reviewer approves, and records the verdict in the PR description. Use whenever you are about to create a PR.
- license
- MIT
Pre-PR review
This repository expects an approved review BEFORE any pull request is created. The reviewer is
the repo-reviewer subagent, which carries the repository's architecture map and hard rules.
Nothing in CI enforces this: the check that used to fail a PR whose description carried no
approved report is gone, so the review is a convention the author keeps, not a gate that keeps
them.
Workflow
Sync and scope the diff
bash git fetch origin main git diff --stat origin/main...HEADIf the branch has no commits ahead of
origin/main, stop: there is nothing to review.Run the local gates first (cheap failures should never reach the reviewer):
bash ./gradlew detekt spotlessCheckIf
app/src/main/res/values*/strings.xmlchanged, also run the key-parity check from.github/workflows/i18n-check.yml(every source key must exist in every locale file). A full Gradle build may be impossible on-device (x86_64 aapt2 on an arm64 device); that is expected — CI compiles. Fix everything that can run locally.Invoke the reviewer with the task tool, subagent type
repo-reviewer. Prompt it with:このブランチ（<branch name>、base: origin/main）のPR前レビューをお願いします。 変更概要: <one or two sentences describing the change and why>The subagent reviews
git diff origin/main...HEADitself; do not paste the whole diff into the prompt.Handle the verdict
REQUEST_CHANGES: fix every ブロッカー, then re-run from step 3. Repeat untilAPPROVE. Never open the PR while a ブロッカー is outstanding.APPROVE: proceed. Consider 提案（非ブロッキング） items; apply the cheap, safe ones.
Record the verdict in the PR description. The PR body should carry the reviewer's report verbatim inside the marker block below, so a reader can see the review actually happened:
markdown <!-- pre-pr-review: approved --> ## Pre-PR review <paste the reviewer's final report here>If a later push changes the branch materially, re-run this skill and update the block (
pre-pr-review: approvedmust stay truthful for the HEAD commit).
Show full SKILL.md (58 more words)Show less
Rules
- Do not skip, summarize away, or forge the reviewer report; the block must be the subagent's actual output for the current HEAD. Nothing checks this now, which is exactly why it matters.
- If the
repo-reviewersubagent is unavailable, say so in the PR — do not open it silently. - Trivial bot PRs (e.g. Weblate translation sync) are exempt.
© yuga-hashimoto, MIT. 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 .opencode/skills/pre-pr-review of yuga-hashimoto/and-code.
Open the folder on GitHubat commit f6593e1
Compare with similar skills
Pre-PR 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 |
|---|---|---|---|---|---|---|
| Pre-PR Review this skillyuga-hashimoto/and-code | 127 | — | ~710 | Automated safety check: Pass | MIT | |
| PR Deep VerificationQwenLM/qwen-code | 28k | — | ~23k | Automated safety check: Pass | Apache-2.0 | |
| Open Code Review CLIalibaba/open-code-review | 46k | — | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Code Reviewflutter/flutter | 180k | — | ~1.4k | Automated safety check: Pass | BSD-3-Clause | |
| PR Review State Fetchprisma/orm | 48k | — | ~767 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Open Code Review CLI
alibaba/open-code-review
Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Code Review
flutter/flutter
Performs a comprehensive, multi-step code review of pull requests or local code changes, using iterative refinement (generation, critique, synthesis) to ensure high-quality, actionable feedback.
- Official
PR Review State Fetch
prisma/orm
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
Knowledge Graph PR Review
tirth8205/code-review-graph
Reviews a pull request or branch diff with a code knowledge graph and produces a structured review that includes blast-radius analysis.
Related
Categories
Questions about Pre-PR Review
What does Pre-PR Review do?
Runs local checks and a repo-reviewer subagent over the whole branch diff before a pull request is opened, then records the approval in the PR description. Written for one Android repository, the skill makes an approved review a precondition for creating a pull request. It starts by fetching origin main and listing the branch diff, and stops if the branch has nothing ahead.
When should I use Pre-PR Review?
Pre-PR Review fits situations like: about to open a pull request in this repository; re-checking a branch after reviewer feedback; adding the reviewer's verdict to a PR description.
How do I install Pre-PR Review in Claude Code?
Run `npx skills add yuga-hashimoto/and-code --skill pre-pr-review -a claude-code`. Or copy the skill folder (.opencode/skills/pre-pr-review in yuga-hashimoto/and-code) into .claude/skills/pre-pr-review in your project. Claude Code loads it when a task matches its description.
How do I install Pre-PR Review in Codex?
Run `npx skills add yuga-hashimoto/and-code --skill pre-pr-review -a codex`. Or copy the skill folder (.opencode/skills/pre-pr-review in yuga-hashimoto/and-code) into .agents/skills/pre-pr-review in your project. Codex loads it when a task matches its description.
Can I use Pre-PR 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 yuga-hashimoto/and-code --skill pre-pr-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/pre-pr-review, .gemini/skills/pre-pr-review, .github/skills/pre-pr-review and .opencode/skills/pre-pr-review in your project.
What does Pre-PR Review need to run?
Going by SKILL.md and its folder, Pre-PR Review needs the command-line tools its instructions call (git). Our summary lists: Git with an origin/main branch; A repo-reviewer subagent defined in the repository; The Gradle tasks detekt and spotlessCheck.
Does Pre-PR Review access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Pre-PR 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 Pre-PR Review use?
Pre-PR Review is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Pre-PR Review use?
About 710 tokens (SKILL.md is roughly 2.8k 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 Pre-PR Review?
Skills that share tags, products or a category with Pre-PR Review: PR Deep Verification (QwenLM/qwen-code, 28k stars), Open Code Review CLI (alibaba/open-code-review, 46k stars), Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars) and Code Review (flutter/flutter, 180k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pre-PR Review?
yuga-hashimoto (a GitHub user) maintains it in yuga-hashimoto/and-code, which has 127 GitHub stars. The repository was last updated on October 8, 2026.
Source: yuga-hashimoto/and-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.