review-preflight — community review-preflight, personal-mcp-core, community, ide skills

v1.0.0

About this Skill

Perfect for Code Review Agents needing automated pre-review safety checks for lint, tests, and PR diff context. Run the Codex PR review preflight in a fixed order and report actionable results without pushing or taking destructive actions.

wakadorimk2 wakadorimk2
[0]
[0]
Updated: 3/5/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
47
Canonical Locale
en
Detected Body Locale
en

Perfect for Code Review Agents needing automated pre-review safety checks for lint, tests, and PR diff context. Run the Codex PR review preflight in a fixed order and report actionable results without pushing or taking destructive actions.

Core Value

Empowers agents to run a minimal pre-review safety pass, checking lint, tests, and PR diff context, providing a consistent review process with tools like Codex CLI, and enabling them to identify obvious risky changes through a fixed order of checks.

Ideal Agent Persona

Perfect for Code Review Agents needing automated pre-review safety checks for lint, tests, and PR diff context.

Capabilities Granted for review-preflight

Automating code review preflight checks for PRs
Validating lint and test results before in-depth review
Identifying high-risk changes in PR diff context

! Prerequisites & Limits

  • Requires PR number and base branch as optional inputs
  • Default base branch set to 'cu' if not provided
  • Limited to running a fixed order of checks

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is review-preflight?

Perfect for Code Review Agents needing automated pre-review safety checks for lint, tests, and PR diff context. Run the Codex PR review preflight in a fixed order and report actionable results without pushing or taking destructive actions.

How do I install review-preflight?

Run the command: npx killer-skills add wakadorimk2/personal-mcp-core. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for review-preflight?

Key use cases include: Automating code review preflight checks for PRs, Validating lint and test results before in-depth review, Identifying high-risk changes in PR diff context.

Which IDEs are compatible with review-preflight?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for review-preflight?

Requires PR number and base branch as optional inputs. Default base branch set to 'cu' if not provided. Limited to running a fixed order of checks.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add wakadorimk2/personal-mcp-core. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use review-preflight immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

review-preflight

Install review-preflight, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

review-preflight

This is the canonical execution contract for running the review preflight with Codex CLI. The human-facing intent lives in docs/skills/review-preflight.md.

Goal

Run a minimal pre-review safety pass before deeper review work starts. Check lint, tests, PR diff context, and obvious risky changes in a fixed order so the result can be pasted into a PR comment.

Inputs

  • PR number (optional)
  • Base branch (optional, default: current branch upstream or main)
  • Expected commands: ruff check ., pytest, gh pr diff <PR> when PR number is available

If the PR number is missing, skip gh pr diff and use local git diff against the chosen base branch. If the base branch is missing, prefer the current branch upstream; otherwise use main.

Procedure

Run the checks in this order.

  1. Run ruff check .
  2. Run pytest
  3. Collect diff context
    • If PR number is provided: run gh pr diff <PR>
    • Otherwise: inspect local git diff against the chosen base branch
  4. Summarize the diff in 2 to 5 lines
  5. Flag obvious risks
    • destructive file operations
    • wide-scope refactors outside the stated review target
    • dependency, CI, or release-impacting changes
    • missing tests for behavior changes

Output Format

Return Markdown with the sections below in this order.

Summary

  • Overall status: / ⚠️ /
  • One-line summary

Checks

  • ruff: / ⚠️ /
  • pytest: / ⚠️ /
  • diff: / ⚠️ /

Diff Summary

  • 2 to 5 short lines

Risks

  • None if no obvious risk was found
  • Otherwise list each risk in one line

Fix Candidates

  • Minimal, local fixes only
  • None if no fix is needed before review

Next Action

  • One line stating whether review can proceed

Constraints

  • Do not push
  • Do not use external web search or fetch arbitrary remote content
  • Do not perform destructive operations
  • Do not change files unless explicitly asked in the current task
  • Keep recommendations inside the current review scope

Related Skills

Looking for an alternative to review-preflight or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer