preflight-checks

Run project-specific linters, formatters, and type checkers on staged files.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/kirvin/copilot-cli-essentials --skill preflight-checks-kirvin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preflight-checks
Source: https://github.com/kirvin/copilot-cli-essentials/tree/main/plugins/cpe/skills/preflight-checks
Command: npx skills add https://github.com/kirvin/copilot-cli-essentials --skill preflight-checks-kirvin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the detection and execution of project-specific linters, formatters, and type checkers, preventing common code quality issues from being committed.

Core Features & Use Cases

  • Automated Tool Detection: Intelligently identifies and runs relevant code quality tools based on project configuration files (e.g., package.json, .eslintrc, pyproject.toml).
  • Staged/Modified File Scoping: Ensures checks are only performed on relevant, changed files, optimizing performance.
  • Auto-Fix Protocol: Attempts to automatically fix formatting and simple linting errors, then re-stages modified files.
  • Use Case: Before committing a code change, run this skill to automatically format your Python code with Black, lint your JavaScript with ESLint, and check TypeScript types, fixing any detected issues.

Quick Start

Run the preflight-checks skill to verify and fix code quality issues in your staged files.

Frequently Asked Questions about preflight-checks

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

FAQPage Schema
How do I run linters and type checkers on staged files before a commit?

To run linters and type checkers on staged files, this Skill scopes checks to modified files and auto-detects tools like ESLint, mypy, and Ruff from project configs. It executes the relevant checks and attempts to auto-fix common formatting and linting errors.

What's the best way to automatically format code and fix linting errors before a pull request?

Automatically formatting code and fixing linting errors before a pull request is handled by the auto-fix protocol. It runs detected formatters like Prettier, applies fixes to simple issues, and re-stages the modified files so they are ready for commit.

Does this pre-commit code quality check support Python projects using Ruff and mypy?

Yes, this pre-commit code quality check supports Python projects by auto-detecting Ruff and mypy from configuration files like pyproject.toml. It runs these tools on your staged or modified Python files to ensure quality and consistency.

Can I use this tool to check TypeScript types and lint JavaScript with ESLint?

You can use this tool to check TypeScript types and lint JavaScript by auto-detecting ESLint and TypeScript configurations from package.json. It executes these checkers on your changed files to prevent type and lint issues from being committed.

How does automated pre-commit tool detection work for mixed-language projects?

Automated pre-commit tool detection for mixed-language projects works by reading configuration files like package.json and pyproject.toml. It intelligently identifies and runs the relevant linters, formatters, and type checkers for each staged file's respective language.

Why should I scope pre-commit linting to modified files instead of the whole project?

Scoping pre-commit linting to modified files instead of the whole project optimizes performance by only running checks on changed code. This ensures fast feedback and targeted auto-fixing before commits without processing unaffected files.