mcpField
P
pre-merge-gate

pre-merge-gate

github.com/heyeddi-comTesting & quality086 installsUpdated 1d ago
Repository

About pre-merge-gate

pre-merge-gate is a project skill that runs a set of checks and produces a PASS/FAIL/SKIP report before code is merged. It is intended for QA and agents verifying that required checks pass before approving or merging a PR.

Key features

  1. 01Runs configured project checks
  2. 02Produces PASS/FAIL/SKIP report
  3. 03Exits nonzero when a check fails
  4. 04Supports optional audit skips

Use cases

  1. 01Checking readiness before merging to main or dev
  2. 02Verifying fixes after review feedback
  3. 03Providing a QA gate report for a PR

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/heyeddi-com/heyeddi-skills --skill pre-merge-gate

After installing, type/pre-merge-gatein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

manifest.json
context/
ANTI_PATTERNS.md
EXAMPLES.md
PROSE_ANTI_SLOP.md
VOCABULARY.md
reference/
subagents.md
scripts/
_skill_cli.py
pre_merge_gate.py

Details

From the project README

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

  1. 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

  • setup audit (@heyeddi-setup verify_setup --check: incomplete prefs fail)
  • 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)
  • engineering audit (@engineering-excellence audit_engineering --check: errors fail; warns advisory)

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

  • duplicate UI scan (no-duplicate-ui)
  • prose audit (heyeddi-design verify_prose.py) — always-on for copy; skip only in emergency
  • contrast audit on product routes (visual-auditor; SKIP if Playwright missing)

Flags: --skip-duplicate-ui, --skip-prose-audit, --skip-engineering-audit, --skip-setup-audit, --skip-visual-audit. --skip-backend, --skip-engineering-audit, and --skip-setup-audit are 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:

  1. Run:

    python .agents/skills/heyeddi/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 → reference/next-skill-handoff.md.

Comments

Markdown supported