How do I install the Pre Merge Gate skill?

Run npx skillmds@latest add heyeddi-com/pre-merge-gate-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pre Merge Gate safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pre Merge Gate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pre Merge Gate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pre Merge Gate?

HeyEddi-com (@heyeddi-com) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pre Merge Gate by heyeddi-com — Agent Skill

Name: Pre Merge Gate
Author: HeyEddi-com

File contents

Pre-merge Gate

Subagents (default)

Run gate via Task shell subagent: pre_merge_gate.py. Main chat triages FAIL lines and re-delegates fixes. See reference/subagents.md.

When to use

QA wants a single green/red report before approving a PR
Before merging to main / dev
After addressing review feedback: confirm all gates pass

Hard stop

The script exits 1 if any check is FAIL. Do not treat a markdown BLOCKED report with exit 0 as merge-ready — that bug is fixed. Agents must not merge (or say merge-ready) unless the process exits 0.

Instructions

Run python .agents/skills/pre-merge-gate/scripts/pre_merge_gate.py --project-root <root>.
Read the markdown report: each check shows PASS/FAIL/SKIP.
Fix failing checks and re-run until exit code is 0.

Eval / harness turns: When the eval harness captures Playwright proof separately, run with --skip-visual-audit so the gate does not invoke contrast audit (no Playwright in agent turn).

Checks

Required when the tree exists

npm test + production build (package.json)
vue-tsc --noEmit when node_modules is present (FAIL if frontend exists but toolchain missing)
backend pytest (backend/tests, prefers backend/.venv)
ruff F821 on backend/app (undefined names / dropped imports)

Optional (SKIP allowed if skill/tool missing; FAIL still hard-stops)

duplicate UI scan (no-duplicate-ui)
prose audit (heyeddi-design verify_prose.py)
contrast audit on product routes (visual-auditor; SKIP if Playwright missing)

Flags: --skip-duplicate-ui, --skip-prose-audit, --skip-visual-audit. --skip-backend is emergency-only and must not be used for merge sign-off.

When the task is complete: suggest next skills

When you have finished the user's request for this skill (not after every tool call or subagent phase), suggest what to run next:

Run:

python .agents/skills/heyeddi-orchestrator/scripts/suggest_next_skill.py --current-skill pre-merge-gate --project-root .

Add --route /path if you worked a specific route.

Include the script's ### Next step block in your final reply. The user copies the Prompt line into chat (e.g. @heyeddi-design craft /settings).

Pass --mode shape (or craft, audit, etc.) when you know which sub-command just finished.

See @heyeddi-orchestrator → reference/next-skill-handoff.md.

---name: pre-merge-gate-2description: Runs pre-merge checks (backend + frontend + optional UI audit). Any FAIL exits 1 (hard stop). Use when QA approves a PR or before merge to main.---# Pre-merge Gate## Subagents (default)Run gate via **Task** `shell` subagent: `pre_merge_gate.py`. Main chat triages FAIL lines and re-delegates fixes. See `reference/subagents.md`.## When to use- QA wants a single green/red report before approving a PR- Before merging to `main` / `dev`- After addressing review feedback: confirm all gates pass## Hard stopThe script **exits 1** if any check is `FAIL`. Do not treat a markdown `BLOCKED` report with exit 0 as merge-ready — that bug is fixed. Agents must not merge (or say merge-ready) unless the process exits 0.## Instructions1. Run `python .agents/skills/pre-merge-gate/scripts/pre_merge_gate.py --project-root <root>`.2. Read the markdown report: each check shows PASS/FAIL/SKIP.3. Fix failing checks and re-run until exit code is 0.**Eval / harness turns:** When the eval harness captures Playwright proof separately, run with `--skip-visual-audit` so the gate does not invoke contrast audit (no Playwright in agent turn).## Checks**Required when the tree exists**- npm test + production build (`package.json`)- `vue-tsc --noEmit` when `node_modules` is present (FAIL if frontend exists but toolchain missing)- `backend` pytest (`backend/tests`, prefers `backend/.venv`)- ruff **F821** on `backend/app` (undefined names / dropped imports)**Optional (SKIP allowed if skill/tool missing; FAIL still hard-stops)**- duplicate UI scan (`no-duplicate-ui`)- prose audit (`heyeddi-design` `verify_prose.py`)- contrast audit on product routes (`visual-auditor`; SKIP if Playwright missing)Flags: `--skip-duplicate-ui`, `--skip-prose-audit`, `--skip-visual-audit`. `--skip-backend` is emergency-only and must not be used for merge sign-off.## When the task is complete: suggest next skillsWhen you have **finished the user's request** for this skill (not after every tool call or subagent phase), suggest what to run next:1. Run: ```bash python .agents/skills/heyeddi-orchestrator/scripts/suggest_next_skill.py --current-skill pre-merge-gate --project-root . ``` Add `--route /path` if you worked a specific route.2. Include the script's **`### Next step`** block in your **final** reply. The user copies the **Prompt** line into chat (e.g. `@heyeddi-design craft /settings`).Pass `--mode shape` (or `craft`, `audit`, etc.) when you know which sub-command just finished.See `@heyeddi-orchestrator` → `reference/next-skill-handoff.md`.

Frequently asked questions

Pre Merge Gate