Preflight
Run the e22-plugins verification gates and report a per-gate pass/fail summary, with the single re-run command for any failure. Repo-local dev helper; a thin wrapper over the existing mise tasks — no new validation.From its SKILL.md
npx -y skills add element22llc/e22-plugins --skill preflightAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, as published. Nobody here has run it
/preflight — verify before commit / push
A thin convenience wrapper over the existing mise tasks. It adds no
validation logic; it just runs the gates and summarizes them. See
AUTHORING.md → "What I touched → what to run".
Steps
-
Pick the depth:
- Default / before push or PR →
mise run ci(full: lint, plugin-check, actions, fixtures, test, shell, hooktests, version-scan). --fastor before a local commit →mise run check(lint, plugin-check, actions only).
- Default / before push or PR →
-
Run it and capture output.
-
Report a per-gate summary — one line per gate with ✅/❌. For any failure, give the single command to reproduce just that gate:
Failed gate Re-run lint uv run ruff check . && uv run ruff format --check .plugin-check uv run python scripts/check_plugin.py(thencheck_standards.py,check_changelog.py)fixtures uv run python scripts/check_fixtures.pytest uv run pytestshell shellcheck plugins/steer/hooks/*.sh plugins/steer/hooks/lib/*.sh ...hooktests sh plugins/steer/hooks/tests/run.shactions actionlintversion-scan sh plugins/steer/scripts/scan-version-pins.sh . -
If everything passed, say so plainly and state which gate level ran (
checkvsci). Do not claimci-level confidence after only runningcheck.