pre-landing-review

Audit the current Git branch diff against origin/main for structural issues.

Updated May 11, 2026
One-click install
npx skills add https://github.com/jason660519/Project-Manager --skill pre-landing-review-jason660519
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-landing-review
Source: https://github.com/jason660519/Project-Manager/tree/main/.agents/skills/pre-landing-review
Command: npx skills add https://github.com/jason660519/Project-Manager --skill pre-landing-review-jason660519

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing diff review to analyze the current branch against the base branch for structural issues tests often miss, including contract drift, capability gaps, schemaVersion misses, ADR violations, IPC injection risks, Anthropic key leakage, LLM output trust boundaries, enum/discriminated-union completeness, and dead code.

Core Features & Use Cases

  • Diff audit: compares the active branch against origin/main to surface structural issues before a PR or push.
  • Quality gates: detects contract drift, ADR violations, IPC injection risks, and potential key leakage.
  • Actionable output: produces a critique plus a Fix-First action list to guide fixes before merging.
  • Use Case: when preparing a PR or merge, run this skill to verify compliance with project standards and safety concerns.

Quick Start

Run this skill on your current branch diff prior to pushing or opening a PR to ensure code quality and safety.

Frequently Asked Questions about pre-landing-review

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

FAQPage Schema
How do I check a Git branch diff for contract drift and security risks before opening a PR?

A pre-landing diff review audits your branch against origin/main to catch ADR violations, enum incompleteness, and data leakage that automated tests often miss before merging.

What structural issues should I look for in a pre-landing diff review?

A pre-landing diff review audits your branch against origin/main to catch ADR violations, enum incompleteness, and data leakage that automated tests often miss before merging.

How do I audit my Git diff for IPC injection risks and LLM output trust boundaries?

Performing a pre-landing diff review evaluates your Git state to detect IPC injection risks, LLM output trust boundary gaps, and Anthropic key leakage, generating a Fix-First action list to resolve them.

Does pre-landing code review work for feature branches in a standard PR flow?

Yes, pre-landing diff review applies directly to feature branches in a PR workflow, computing the diff against the base branch to verify compliance with project safety standards prior to pushing.

What is the best way to fix schemaVersion misses and dead code found in a branch diff?

The best way is to use a pre-landing diff review, which identifies schemaVersion misses and dead code, then produces an actionable Fix-First steps list to guide your corrections before merging.