agentsclimarketplace
Sign in

Pre merge gate

Skill HeyEddi-com/skills/skills/pre-merge-gate

Runs pre-merge checks (tests, build, types, optional UI audit) and returns a markdown pass/fail report. Use when QA approves a PR or before merge to main.From its SKILL.md

Install
npx -y skills add HeyEddi-com/skills --skill pre-merge-gate

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 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

2.1 KB, 485 tokens by cl100k_base, as published. Nobody here has run it

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 frontend-heavy changes
  • After addressing review feedback: confirm all gates pass

Instructions

  1. Run python 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 all required checks pass.

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

Checks

  • npm test (if script exists)
  • verify build
  • vue-tsc (if available)
  • duplicate UI scan (no-duplicate-ui when installed)
  • prose audit on Vue/locale copy (heyeddi-design verify_prose.py when installed)
  • visual audit on product routes (visual-auditor when installed; skips if Playwright missing)

Use --skip-duplicate-ui, --skip-prose-audit, or --skip-visual-audit to omit optional UI gates.

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

What ships with it: 8 files

14.2 KB alongside SKILL.md, 2 of them executable

context/

reference/

scripts/

Gives 0 of the 12 instructions most docs writing skills give in 485 tokens

Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07

  • Announce the skill at startin 54 of 1637, across 26 files
  • Convert legacy doc files before editingin 45 of 1637, across 7 files
  • Predict questions readers might askin 42 of 1637, across 4 files
  • Generate clarifying questions for initial contextin 42 of 1637, across 3 files
  • Create document scaffold with placeholder textin 42 of 1637, across 3 files
  • Brainstorm content options for each sectionin 42 of 1637, across 3 files
  • Test the document with a fresh context-less instancein 42 of 1637, across 3 files
  • Include exact file paths in every taskin 42 of 1637, across 15 files
  • Ask interview questions one at a timein 42 of 1637, across 27 files
  • Apply surgical edits during refinementin 41 of 1637, across 2 files
  • Offer structured workflow or freeformin 40 of 1637, across 1 file
  • Ask for document meta-contextin 40 of 1637, across 2 files

Said here and by no other author read

  • run the pre-merge gate script
  • read the markdown report
  • pass required checks before merge
  • use the shell subagent to run the gate
  • skip visual audit during eval turns
  • suggest next skills when the task is complete

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,452. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.