preflight

Run automated pre-commit and pre-push verification checks on e22-plugins using mise and Bash scripts.

2|Updated May 19, 2026
One-click install
npx skills add https://github.com/element22llc/e22-plugins --skill preflight-element22llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preflight
Source: https://github.com/element22llc/e22-plugins/tree/main/.claude/skills/preflight
Command: npx skills add https://github.com/element22llc/e22-plugins --skill preflight-element22llc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the verification process of e22-plugins before a commit or push, streamlining the development workflow by providing a summary of the verification results and allowing quick re-run of failed checks.

Core Features & Use Cases

  • Automated Verification: Run predefined verification gates on e22-plugins to ensure code quality and adherence to standards.
  • Summary Reporting: Present a summary of each gate's pass/fail status with a single re-run command for any failure.
  • Repo-local Helper: Designed as a thin wrapper over existing mise tasks for streamlined usage.
  • Use Case: Before pushing code changes to a repository, run /preflight to ensure that all checks pass, preventing potential issues later on.

Quick Start

To run the preflight checks, simply use the command: /preflight

Frequently Asked Questions about preflight

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

FAQPage Schema
How do I automate pre-commit code verification checks for my repository?

Automate pre-commit code verification by running the `/preflight` command, which executes predefined verification gates on your codebase to ensure code quality and standard compliance before pushing changes.

What are pre-push verification checks and why do I need them?

Pre-push verification checks are automated quality gates that run before code is committed or pushed. They are needed to enforce code quality, verify standard compliance, and prevent potential issues from entering the repository.

Do I need mise installed to run pre-commit verification scripts?

Yes, you need mise installed. The verification process runs a suite of checks using `mise` and custom Bash scripts within the `scripts/` directory to execute its predefined verification gates.

How do I re-run a failed code quality check from my pre-commit summary?

To re-run a failed code quality check, use the single re-run command provided in the verification summary report, which presents the pass or fail status of each individual gate.

Can I use custom Bash scripts for CI/CD pre-commit checks?

Yes, you can use custom Bash scripts for CI/CD pre-commit checks. This Skill functions as a thin wrapper over existing `mise` tasks and custom scripts to execute verification gates.