factory-pr-review

Automate pre-push quality gates and structured pull request reviews for GitHub, GitLab, or Azure DevOps.

1|Updated Apr 8, 2026

Search Tags:#code review #pull request #openapi #breaking changes #governance #traceability #push gate

One-click install

npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-pr-review

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: factory-pr-review
Source: https://github.com/e2its/myrmion-AI-factory/tree/main/.claude/skills/factory-pr-review
Command: npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires oasdiff, @asyncapi/cli, gh, glab, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Pull requests frequently reach the merge stage with broken API contracts, missing documentation, architectural drift, or secrets in the diff, causing expensive review cycles and production incidents. This skill intercepts issues locally before push and produces structured, severity-weighted reviews for open PRs, reducing review fatigue and preventing broken code from reaching the remote.

Core Features & Use Cases

Pre-push quality gate: Automatically runs before git push to block breaking changes, secret leaks, and governance violations without waiting for CI.
Six-axis review engine: Audits code correctness, code-to-documentation sync, OpenAPI/AsyncAPI contract changes, Architecture Decision Records, CHANGELOG/traceability, and cyclomatic complexity.
Assistive PR reviewer: Generates structured JSON and Markdown reviews with clear severity buckets (blocker, important, nit, question, praise) for GitHub, GitLab, or Azure DevOps pull requests.
Framework-aware hard blocks: Enforces project-specific governance rules including branch naming, protected paths, manifest coherence, and incremental persistence policies.

Quick Start

Ask Claude to review a specific pull request URL or let the automatic push hook run the preflight gate before you push your branch.

Frequently Asked Questions about factory-pr-review

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

FAQPage Schema

How do I automate pre-push pull request reviews to catch breaking API contract changes?▼

Automated pre-push pull request review uses git hooks to intercept pushes and run quality gates for breaking API contract changes, governance violations, and secret leaks. This prevents broken code from reaching the remote repository before merge cycles begin.

How does a six-axis code review engine evaluate OpenAPI and AsyncAPI contract changes?▼

A six-axis code review engine evaluates OpenAPI and AsyncAPI contract changes by auditing code correctness, documentation sync, contract validity, architecture decision records, traceability, and cyclomatic complexity. It uses oasdiff and asyncapi-cli to detect breaking schema modifications.

Can I use automated PR review gates with GitHub, GitLab, or Azure DevOps repositories?▼

Yes, automated PR review gates support GitHub, GitLab, and Azure DevOps repositories. The review engine integrates with platform CLIs like gh and glab to generate structured Markdown and JSON severity reports for pull requests across these hosting services.

Do I need oasdiff and asyncapi-cli installed to validate API contract changes locally?▼

You need oasdiff and asyncapi-cli optionally installed to validate API contract changes locally. The pre-push gate requires git, while these dependencies enable deeper contract validation for OpenAPI and AsyncAPI schema drift detection before merging.

What is the best way to enforce governance rules like branch naming and protected paths before a git push?▼

The best way to enforce governance rules like branch naming and protected paths before a git push is using framework-aware hard blocks within a pre-push hook. This intercepts violations locally, applying manifest coherence and incremental persistence policies without waiting for CI.

Why does my pull request merge with missing documentation and architectural drift despite passing CI?▼

Pull requests merge with missing documentation and architectural drift when CI lacks local pre-push interception. A structured pre-push quality gate catches documentation sync issues, ADR violations, and complexity drift before code reaches the remote, reducing review fatigue.