pre-mortem

Analyze GitHub PR diffs for reliability, security, quality, and observability issues.

31|4|Updated Aug 24, 2021
One-click install
npx skills add https://github.com/razorpay/trino-gateway --skill pre-mortem-razorpay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-mortem
Source: https://github.com/razorpay/trino-gateway/tree/main/.agents/skills/pre-mortem
Command: npx skills add https://github.com/razorpay/trino-gateway --skill pre-mortem-razorpay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, bash, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The Pre-Mortem Skill helps engineering teams identify reliability, security, quality, and observability risks in pull requests before merging by validating code patterns and runtime risk signals across infrastructure, domain logic, and software quality patterns.

Core Features & Use Cases

  • Automated PR reliability checks across infrastructure (databases, queues, caches), domain constraints, and observability patterns.
  • Multi-agent analysis with dedicated checks for Infrastructure, Service Integrations, Domain Quality, Observability, and Performance.
  • Generates a prioritized findings list, with recommended fixes or PR comments, deduplicated across agents.

Quick Start

Provide a PR diff or open a PR in your repository and run the pre-mortem skill to surface issues before merge.

Frequently Asked Questions about pre-mortem

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

FAQPage Schema
How do I automate reliability and observability checks on a GitHub PR before merging?

To automate PR reliability checks before merge, analyze the GitHub PR diff to surface security, quality, infrastructure, and observability issues. This multi-agent process scans domain and performance patterns, prioritizes risks, deduplicates findings, and suggests actionable fixes.

What is pre-mortem PR analysis and when do I need it for infrastructure changes?

Pre-mortem PR analysis identifies runtime risks across infrastructure like databases, queues, and caches before code is merged. You need it to validate software quality patterns, domain constraints, and observability signals early, preventing reliability issues from reaching production.

How do I run a multi-agent PR analysis to surface security and performance issues?

Run a multi-agent PR analysis by loading repository context and scanning the PR diff. Dedicated agents check infrastructure, service integrations, domain quality, observability, and performance, aggregating findings into a prioritized, deduplicated list of recommended fixes or PR comments.

Do I need Python3 and bash to run automated PR reliability checks?

Yes, you need Python3 and bash installed in your environment to run these automated PR reliability checks. These dependencies execute the scripts that load repository context, scan diffs, and aggregate findings from the specialized analysis agents.

What's the best way to review pull requests for domain logic and service integration risks?

The best way to review pull requests for domain logic and service integration risks is using an automated multi-agent scanner. It validates domain constraints and service integrations directly from the PR diff, generating a prioritized findings list with actionable fixes before merge.

Why does my PR review miss observability and infrastructure pattern issues?

Your PR review likely misses observability and infrastructure pattern issues because manual checks lack comprehensive runtime risk validation. Automating the pre-merge analysis with dedicated scanning agents surfaces these specific infrastructure, domain, and observability defects reliably.