skills.rest
razorpay
razorpayOFFICIAL
Explore all skills by this author →
Website𝕏@razorpayGitHub

pre-ship-check

Scan branch diffs across six layers and emit a canonical Markdown report.

2|2|Updated May 13, 2026
Search Tags:#design system#pr review#test coverage#CI guardrails#diff scanning#prompt craft#risk redaction
One-click install
npx skills add https://github.com/razorpay/ai-playbook --skill pre-ship-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-ship-check
Source: https://github.com/razorpay/ai-playbook/tree/main/skills/pre-ship-check
Command: npx skills add https://github.com/razorpay/ai-playbook --skill pre-ship-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of inconsistent, reviewer-mood-driven PR review by enforcing a structured six-layer pre-merge contract on every change.

Core Features & Use Cases

  • Six-layer diff review: Scans a branch’s diff for redlines, design-system drift, missing tests, PR craft issues, prompt-craft trace quality, and behavior preservation.
  • Deterministic, actionable reporting: Emits a canonical Markdown report that’s reviewer-readable quickly and machine-parseable for downstream tooling.
  • Green Belt boss-fight readiness: Provides the required pre-flight discipline for Green Belt submissions by making the review standard runnable.

Quick Start

Use the command run pre-ship-check on this branch to generate a structured report for your branch’s diff against the base branch.

Frequently Asked Questions about pre-ship-check

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

FAQPage Schema
How do I run a structured pre-merge PR review on my branch diff?▼

A six-layer diff review scans branch changes for redlines, design-system drift, missing tests, PR craft issues, prompt-craft trace quality, and behavior preservation. It replaces reviewer-mood-driven checks with a deterministic pre-merge contract on every change.

Does CI guardrail scanning check for missing test coverage and design system drift?▼

Yes, CI guardrail scanning checks for missing test coverage and design system drift. The review scans six defined layers with strict RED-blocking rules to catch these policy and quality issues before opening or merging a PR.

What is the best way to generate a deterministic and machine-parseable PR review report?▼

The best way to generate a deterministic PR review report is to run the pre-ship scan on your branch diff. It emits a canonical Markdown report matching output-shape.md, making it quickly reviewer-readable and machine-parseable for downstream tooling.

Can I use diff scanning to enforce Green Belt boss-fight readiness for code and UI changes?▼

Yes, you can use diff scanning to enforce Green Belt boss-fight readiness. The review provides the required pre-flight discipline for Green Belt submissions by making the review standard runnable across code and UI changes with sponsor and maintainer review gating.

Related Skills

Explore More Software Engineering Skills→
kage1020kage1020

diff-report

Analyze branch changes and generate a five-section Markdown diff report.

Community
Intermediate
FlatbreadLabsFlatbreadLabs
64

mergify-merge-protections

Control GitHub PR merge timing and dependencies with Mergify protection rules.

Official
Intermediate
ysyecustysyecust
40

verification-loop

Automate end-to-end project verification across builds, type checks, linting, tests, and security scans.

Community
Intermediate
FrekiManagarmFrekiManagarm

github-code-review

Coordinate multi-agent GitHub pull request reviews across security, performance, style, and architecture.

Community
Advanced