skills.rest
Xza85hrf
Xza85hrfCOMMUNITY
Explore all skills by this author →
GitHub

pre-landing-review

Automate pre-landing PR reviews with CRITICAL and INFORMATIONAL checks.

Updated Feb 9, 2026
Search Tags:#security#quality#risk-management#code-review#pr-review#pre-landing
One-click install
npx skills add https://github.com/Xza85hrf/claude-code-agent-kit --skill pre-landing-review-xza85hrf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-landing-review
Source: https://github.com/Xza85hrf/claude-code-agent-kit/tree/main/.claude/skills/quality/pre-landing-review
Command: npx skills add https://github.com/Xza85hrf/claude-code-agent-kit --skill pre-landing-review-xza85hrf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that code submissions to main are safe by identifying critical blockers and informational findings before merging, reducing risk and speeding up reviews.

Core Features & Use Cases

  • Two-pass review framework: CRITICAL blockers block /ship and INFORMATIONAL advisories to guide improvements.
  • Safety and quality checks: data safety, concurrency, authentication, and prompt risk evaluation to prevent unsafe changes.
  • Structured output: produces a standardized review report suitable for PR bodies.

Quick Start

Run the pre-landing-review skill on your feature branch to generate a structured review before opening a PR.

Frequently Asked Questions about pre-landing-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a two-pass PR review and how does it work for pre-landing checks?▼

Pre-landing PR review identifies critical blockers and informational findings before merging to main. It evaluates feature branch diffs for data safety, concurrency, authentication, and prompt risks to ensure code submissions are safe and reduce merge risks.

How do I automate code review for data safety and concurrency risks before merging?▼

Run the pre-landing review on your feature branch to generate a structured review report before opening a PR. The two-pass workflow checks for critical blockers and informational advisories, outputting a standardized report suitable for PR bodies.

Does pre-landing review work on feature branch diffs against the main branch?▼

Pre-landing review is designed for feature branch diffs against main. It requires no external dependencies or components, making it suitable for any software engineering workflow needing automated risk management and quality checks before landing code.

What is the difference between CRITICAL blockers and INFORMATIONAL advisories in code review?▼

Pre-landing review distinguishes CRITICAL blockers, which block the /ship operation, from INFORMATIONAL advisories that guide improvements. This two-pass framework ensures critical data safety and auth risks are caught before merging, while non-blocking issues are documented.

When do I need an automated pre-landing review for prompt risks and authentication?▼

Pre-landing review focuses on critical blockers blocking the ship operation. For non-blocking issues, it generates INFORMATIONAL advisories to guide improvements, meaning the merge is not halted but the risks are documented in the standardized PR report.

Related Skills

Explore More Software Engineering Skills→
lmanchulmanchu
5

review

Analyze pull request diffs against the main branch for critical issues.

Community
Advanced
rkz91rkz91
264

gsd-ship

Push a feature branch, create a pull request with an auto-generated body, and track merge status.

Community
Advanced
magicpro97magicpro97
8

merge-when-green

Automatically merge GitHub pull requests after all required CI checks pass.

Community
Intermediate
wangfeivwangfeiv

review

Analyze code diffs against mainline branches for SQL safety, concurrency, and trust boundaries.

Community
Intermediate