pre-landing-review

Audit code diffs against a checklist and issue a landing verdict.

310|45|Updated Feb 22, 2026

Search Tags:#checklist #code-review #gate #pull-request #diff-analysis #safety-audit #pre-landing

Ready to run

npx skills add https://github.com/Mathews-Tom/armory --skill pre-landing-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pre-landing-review
Source: https://github.com/Mathews-Tom/armory/tree/main/skills/pre-landing-review
Command: npx skills add https://github.com/Mathews-Tom/armory --skill pre-landing-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Gate-oriented safety audit for code changes before landing, using a structured checklist with two-pass severity triage and blocking/non-blocking classification.

Core Features & Use Cases

Two-pass CRITICAL and INFORMATIONAL safety triage to identify blocking vs informational issues.
Enforces a gating process on code changes, providing remediation guidance and a final landing verdict.
Integrates with diffs, checklist loading from references/checklist.md, and clear developer-facing outcomes.

Quick Start

Run a pre-landing review by supplying the branch diff and verifying the references/checklist.md.

Frequently Asked Questions about pre-landing-review

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

FAQPage Schema

How do I run a pre-landing safety audit on a pull request?▼

Run a pre-landing safety audit by supplying the branch diff and verifying the checklist. The process performs a two-pass triage to classify blocking or informational issues, yielding a final landing verdict with remediation guidance.

What is a two-pass safety triage for code review?▼

A two-pass safety triage evaluates diffs by first identifying critical blocking issues and then cataloging informational findings. This structured checklist approach enforces remediation before delivering a final merge verdict.

How does a checklist-based gate review identify blocking issues in a diff?▼

The gate review analyzes diffs against predefined criteria to identify blocking issues. It mandates remediation for critical findings and compiles explicit guidance for fixes or acknowledgments before allowing the merge.

Can I customize the safety checklist used for the pre-landing review?▼

You can customize the safety checklist by modifying the references file. The review loads its mandatory checklist from this file, allowing you to define the specific criteria used to gate code changes.

What is the best way to ensure a feature branch is safe to merge?▼

The best way to ensure a branch is safe to merge is performing a structured safety audit. This process analyzes diffs against a checklist, enforces blocking remediation for critical issues, and provides a final landing verdict.

What happens when critical blocking issues are found during a diff analysis?▼

When critical blocking issues are found during diff analysis, the safety audit enforces remediation. It prevents the merge and compiles explicit developer-facing guidance for required fixes or necessary acknowledgments.