preflight

Scan git-changed files for common issues and report them with file:line references.

Updated Sep 12, 2021
One-click install
npx skills add https://github.com/cerico/macfair --skill preflight-cerico
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: preflight
Source: https://github.com/cerico/macfair/tree/main/files/claude/skills/preflight
Command: npx skills add https://github.com/cerico/macfair --skill preflight-cerico

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a quick pre-PR check to catch common issues before you push changes, reducing back-and-forth and rework.

Core Features & Use Cases

  • Change-set validation: Detects common problems in files changed in a PR.
  • Issue reporting: Reports file:line references for quick fixes.
  • Workflow integration: Easily integrated into CI or local git workflows.

Quick Start

Run the preflight to catch issues before pushing a PR. Use:

  • Run git diff main --name-only to get the list of changed files.
  • For each changed file, run the checks described in this Skill.
  • Report issues with file:line references.

Frequently Asked Questions about preflight

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

FAQPage Schema
How do I catch code quality issues before creating a pull request?▼

Code quality pre-PR checks automate scanning changed files for common issues, reporting errors with file and line references to reduce rework and review back-and-forth.

How does a preflight scan identify which files to check in a git diff?▼

The preflight scan identifies changed files using the git diff command, then applies static checks only to those modified files to validate the change-set and group results for readability.

Can I integrate static checks into my existing CI workflow?▼

Yes, static checks integrate into existing CI workflows. The preflight process applies to any Git-based workflow and easily integrates into CI pipelines or local git workflows.

What is the best way to report pull request issues for quick fixes?▼

The best way to report pull request issues is by grouping results for readability and providing exact file:line references, allowing developers to catch errors quickly before merging.

Does preflight code review require any external dependencies?▼

Preflight code review requires no external dependencies. It relies on standard Git-based workflow commands like git diff to identify changed files and validate change-sets.