omk-flow-pr-review

Inspect pull request diffs and generate merge recommendations with risk classification.

130|14|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-flow-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omk-flow-pr-review
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/kimi/omk-flow-pr-review
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-flow-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid merging risky or untested pull requests by turning a diff into an evidence-informed review outcome.

Core Features & Use Cases

  • Diff-to-risk review: Inspects the current git status and maps changed files to features and risk areas to focus the review.
  • Comprehensive correctness and safety checks: Reviews correctness, security, types, tests, and potential regressions across the modified surface.
  • Merge recommendation with blocking clarity: Identifies whether there are blocking issues and produces either a precise blocking list or a pass review with remaining risks.

Quick Start

Ask the AI to run the omk-flow-pr-review on your current PR to classify risk, analyze test gaps, and generate a merge recommendation.

Frequently Asked Questions about omk-flow-pr-review

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

FAQPage Schema
How do I review a pull request for merge risks and security issues?

Test gap analysis identifies missing test coverage by mapping changed files to feature risk areas before merge. It evaluates the modified surface to ensure tests adequately cover correctness and potential regression scenarios.

Can I get an automated merge recommendation from a git diff?

A blocking issue in code review is a correctness, security, or regression risk found in the modified surface. The review emits blocking issues with exact file locations and suggested fixes to prevent unsafe merges.

What is test gap analysis in the context of code review?

Test gap analysis identifies missing test coverage by mapping changed files to feature risk areas before merge. It evaluates the modified surface to ensure tests adequately cover correctness and potential regression scenarios.

How do I detect potential regressions before merging a code change?

Yes, you can get an automated merge recommendation by transforming a pull request diff into an evidence-informed review. It emits a precise blocking list with suggested fixes or a pass review covering remaining risks.

When do I need an evidence-gated code review for my pull request?

A blocking issue in code review is a correctness, security, or regression risk found in the modified surface. The review emits blocking issues with exact file locations and suggested fixes to prevent unsafe merges.