productionos-review

Analyze code diffs to surface high-risk issues before merging.

8|Updated Mar 17, 2026

Search Tags:#quality-assurance #code-review #security-review #diff-analysis #llm-safety #dependency-risk #pre-landing

Ready to run

npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill productionos-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: productionos-review
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/codex-skills/productionos-review
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill productionos-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing review of code changes to surface high-risk issues before merging, focusing on correctness, security, and test coverage.

Core Features & Use Cases

Deterministic pre-landing review: Analyzes diffs for risk signals before release.
Risk buckets coverage: Checks SQL safety, LLM trust boundaries, conditional side effects, missing tests, dependency risks, and security issues.
Evidence-first findings: Produces prioritized findings with file references and concrete remediation guidance.

Quick Start

Invoke the productionos-review workflow on a pull request diff to generate a findings report.

Frequently Asked Questions about productionos-review

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

FAQPage Schema

How do I review code diffs for security risks before merging a pull request?▼

Pre-landing risk review analyzes code diffs across branches to surface high-risk issues before merging. It checks SQL safety, trust boundaries, side effects, test coverage, and dependency risks to produce a prioritized findings list with severities and concrete remediation guidance.

What is pre-landing code review and when do I need it for risky pull requests?▼

Pre-landing code review is a deterministic process that evaluates pull request diffs for correctness and security risks before release. You need it when merging risky PRs that involve SQL changes, LLM trust boundaries, or new dependencies.

How do I analyze SQL safety and LLM trust boundaries in a pull request diff?▼

You can analyze SQL safety and LLM trust boundaries by running a pre-landing risk review on the changed files. The review assesses trust boundaries, conditional side effects, and dependency risks to generate an evidence-first findings report.

Does pre-landing risk review work with Codex-safe workflows?▼

Yes, pre-landing risk review integrates with Codex-safe workflows to provide deterministic review ordering. It operates on diffs, branches, and changed files across repositories to output prioritized findings with file references and remediation guidance.

Can I check for missing tests and dependency risks in a code diff before landing?▼

Yes, pre-landing risk review checks code diffs for missing tests and dependency risks alongside SQL safety and security issues. It produces a prioritized findings list with severities and evidence to support deterministic pre-landing review decisions.

What are the limitations of automated diff analysis for security review?▼

Automated diff analysis for security review focuses on risk signals within the provided diff, branches, and changed files. It surfaces high-risk issues like side effects and trust boundaries but requires a pre-landing review workflow to ensure comprehensive coverage before merging.