Pre-Landing PR Review

VerifiedCaution

Analyzes diff against main for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.

Sby Skills Guide Bot
DevelopmentIntermediate
7/23/2026
Claude Code
#code-review#git-diff#pull-request#sql-safety#llm-security

Recommended for

Automated summary

Reviews the current branch's diff against main through a structured checklist (SQL safety, LLM output trust boundary, conditional side effects, dead code, test gaps) as a pre-landing gate.

Strengths

  • Two-pass analysis — critical (SQL/data safety, LLM trust boundary) then informational — so risk is clearly prioritized
  • Re-fetches origin/main before diffing to avoid false positives from a stale local main
  • Asks for confirmation on every critical issue via AskUserQuestion, including a false-positive option
  • Read-only by default: only edits files when the user explicitly picks 'Fix it now'

Limitations

  • Hard dependency on .claude/skills/review/checklist.md existing; the workflow halts without it
  • Runs no tests or linters — it targets structural issues that tests don't catch
  • Only diffs against main and assumes the remote is named origin
When to use it

Right before opening or merging a pull request, to catch structural and safety problems CI won't surface.

When not to use it

For in-depth functional code review, refactoring, or debugging — it only covers the checklist and changes nothing without approval.

Security analysis

Caution
Quality score86/100

The skill is legitimate and mostly read-only, with explicit user confirmation required before edits. However, it uses Bash/git network operations and has write-capable tools, so it warrants caution rather than being considered risk-free.

Findings
  • •Uses Bash to run git fetch/diff, which performs network access to the configured origin remote.
  • •Declares Edit and Write permissions and may modify files when the user explicitly selects 'Fix it now'.
  • •Reads and trusts `.claude/skills/review/checklist.md`; if that file is compromised, it could influence review behavior, though the skill stops if it is unreadable.
How this analysis is made

Examples

Review before landing
Review my current branch against main before I open the PR — check for SQL safety and LLM trust boundary problems.
Explicit slash command
/review
Sanity check uncommitted work
I've got a mix of committed and uncommitted changes on this branch; run a pre-landing review against origin/main and tell me if anything critical is there.

name: review version: 1.0.0 description: | Pre-landing PR review. Analyzes diff against main for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. allowed-tools:

  • Bash
  • Read
  • Edit
  • Write
  • Grep
  • Glob
  • AskUserQuestion

Pre-Landing PR Review

You are running the /review workflow. Analyze the current branch's diff against main for structural issues that tests don't catch.


Step 1: Check branch

  1. Run git branch --show-current to get the current branch.
  2. If on main, output: "Nothing to review — you're on main or have no changes against main." and stop.
  3. Run git fetch origin main --quiet && git diff origin/main --stat to check if there's a diff. If no diff, output the same message and stop.

Step 2: Read the checklist

Read .claude/skills/review/checklist.md.

If the file cannot be read, STOP and report the error. Do not proceed without the checklist.


Step 3: Get the diff

Fetch the latest main to avoid false positives from a stale local main:

git fetch origin main --quiet

Run git diff origin/main to get the full diff. This includes both committed and uncommitted changes against the latest main.


Step 4: Two-pass review

Apply the checklist against the diff in two passes:

  1. Pass 1 (CRITICAL): SQL & Data Safety, LLM Output Trust Boundary
  2. Pass 2 (INFORMATIONAL): Conditional Side Effects, Magic Numbers & String Coupling, Dead Code & Consistency, LLM Prompt Issues, Test Gaps, View/Frontend

Follow the output format specified in the checklist. Respect the suppressions — do NOT flag items listed in the "DO NOT flag" section.


Step 5: Output findings

Always output ALL findings — both critical and informational. The user must see every issue.

  • If CRITICAL issues found: output all findings, then for EACH critical issue use a separate AskUserQuestion with the problem, your recommended fix, and options (A: Fix it now, B: Acknowledge, C: False positive — skip). After all critical questions are answered, output a summary of what the user chose for each issue. If the user chose A (fix) on any issue, apply the recommended fixes. If only B/C were chosen, no action needed.
  • If only non-critical issues found: output findings. No further action needed.
  • If no issues found: output Pre-Landing Review: No issues found.

Important Rules

  • Read the FULL diff before commenting. Do not flag issues already addressed in the diff.
  • Read-only by default. Only modify files if the user explicitly chooses "Fix it now" on a critical issue. Never commit, push, or create PRs.
  • Be terse. One line problem, one line fix. No preamble.
  • Only flag real problems. Skip anything that's fine.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/pre-landing-pr-review-mrx3xxt0/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/pre-landing-pr-review-mrx3xxt0' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pre-landing-pr-review-mrx3xxt0/download' --output '.skill-downloads/pre-landing-pr-review-mrx3xxt0/SKILL.md.part' && mv '.skill-downloads/pre-landing-pr-review-mrx3xxt0/SKILL.md.part' '.skill-downloads/pre-landing-pr-review-mrx3xxt0/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/pre-landing-pr-review-mrx3xxt0/SKILL.md' && test -s '.skill-downloads/pre-landing-pr-review-mrx3xxt0/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/review' && cp -R '.skill-downloads/pre-landing-pr-review-mrx3xxt0' '.claude/skills/review'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/pre-landing-pr-review-mrx3xxt0'

openskills read 'pre-landing-pr-review-mrx3xxt0'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/pre-landing-pr-review-mrx3xxt0/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills