Node Pre-push

SkillDev tools

Run the Node pull-request gates before pushing TypeScript changes, and triage verified flakes without speculative test changes.

Use Node Pre-push in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Node Pre-push and connect your AI. About a minute.

Then ask your AI: use the Node Pre-push skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.

No other account needed.

Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

Node Pre-pushStart free

The instructions your AI receives, as published by kaeawc/auto-mobile in skills/node-prepush/SKILL.md and read by Ahel’s review.

Use this workflow before pushing a Node or TypeScript change.

Run bash scripts/prepush-node.sh. During a short local feedback loop, use bash scripts/prepush-node.sh --changed; it still runs format, typecheck, and lint in full because their baseline and boundary gates are global.
Treat a non-zero bun run lint exit as a failure. Error-level oxlint rules such as eqeqeq are direct gates; the warning ratchet cannot excuse them.
The first gate fetches origin/main and requires the current HEAD to contain it. Rebase or merge main, then re-run the gate before requesting a merge.
For a suspected Node CI flake, inspect the exact failed job log and rerun only after evidence supports it. This week's verified loaded-runner 100ms timing overages use the timing gate's isolated recheck; do not alter tests when that recheck is clean. Treat a matching cross-platform failure as shared state or stale base until proven otherwise.

Advanced